Merge PR #1425 into maint

libgnucash/backend/xml/gnc-account-xml-v2.cpp

@@ -323,7 +323,7 @@ deprecated_account_security_handler (xmlNodePtr node, gpointer act_pdata)
     PWARN ("Account %s: Obsolete xml tag 'act:security' will not be preserved.",
            xaccAccountGetName (pdata->account));
     /* If the account has both a commodity and a security element, and
-       the commodity is a currecny, then the commodity is probably
+       the commodity is a currency, then the commodity is probably
        wrong. In that case we want to replace it with the
        security. jralls 2010-11-02 */
     if (!orig || gnc_commodity_is_currency (orig))

libgnucash/core-utils/gnc-filepath-utils.cpp

@@ -1,5 +1,5 @@
 /********************************************************************\
- * gnc-filepath-utils.c -- file path resolutin utilitie             *
+ * gnc-filepath-utils.c -- file path resolution utility             *
  *                                                                  *
  * This program is free software; you can redistribute it and/or    *
  * modify it under the terms of the GNU General Public License as   *

libgnucash/doc/constraints.txt

@@ -71,7 +71,7 @@ returned.
 
 Simple/ad-hoc lazy evaluation works well when data dependencies are 
 simple, but it breaks down when there are too many/circular
-relationships.  It becomes all too easy to get trapped in inifite
+relationships.  It becomes all too easy to get trapped in inifinite
 loops of corrections.   The goal of moving to a formal constraint
 system is to introduce specific, well-defined sync points where 
 constraint checking can be done, without incuring circular

libgnucash/doc/engine.txt

@@ -25,7 +25,7 @@ If it seems to be an independent concept, it can still be placed
 in the KVP tree of the book, which gives it a 'top-level' existence.
 
 If the concept is used only infrequently, then it probably belongs 
-in a KVP tree.  If the concept has performance-critical requriements,
+in a KVP tree.  If the concept has performance-critical requirements,
 then it is better to implement it as a C struct, and similarly
 design an appropriate SQL table around it, so that the database
 can be queried efficiently and rapidly.

libgnucash/engine/qofbook.h

@@ -87,7 +87,7 @@ struct _QofBook
     /* Boolean indicates that the session is dirty -- that is, it has
      * not yet been written out to disk after the last time the
      * backend ran commit_edit(). This is distinct from the inherited
-     * QofInstance::dirty, which indicates that some persisitent
+     * QofInstance::dirty, which indicates that some persistent
      * property of the book object itself has been edited and not
      * committed. Some backends write data out as part of
      * commit_edit() and so don't use this flag.

libgnucash/engine/test/test-numeric.cpp

@@ -243,7 +243,7 @@ check_equality_operator (void)
         check_unary_op (gnc_numeric_equal,
                         val, mval, mval, "expected %s = %s");
 
-        /* Certain modulo's should be very cleary un-equal; this
+        /* Certain modulo's should be very clearly un-equal; this
          * helps stop funky modulo-64 aliasing in compares that
          * might creep in. */
         mval.denom >>= 1;