From a4cf76cfd1f77878179100dc314ca298451e4048 Mon Sep 17 00:00:00 2001 From: Dave Peticolas Date: Sat, 2 Sep 2000 00:44:37 +0000 Subject: [PATCH] Fix some sgml warnings. git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@2750 57a11ea4-9604-0410-9ed3-97b8803252fd --- doc/sgml/C/xacc-doubleentry.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/sgml/C/xacc-doubleentry.sgml b/doc/sgml/C/xacc-doubleentry.sgml index b7c7072b1d..d4b50302dd 100644 --- a/doc/sgml/C/xacc-doubleentry.sgml +++ b/doc/sgml/C/xacc-doubleentry.sgml @@ -36,7 +36,7 @@ In the course of maintaining large, complex sets of accounts with many transactions, it is very easy to make errors that may go undetected for a long time, and be appallingly difficult to track down, even when - double-entry bookkepping is used. + double-entry bookkeeping is used. @@ -49,7 +49,8 @@ accounting; if you add something in to one account, you have to subtract it from somewhere else. When this is done regularly and consistently, this results in the - magical identity of accounting: + identity of accounting: + Total of Debits = Total of Credits. @@ -86,11 +87,10 @@ somewhat more accurate to call it multiple-entry bookkeeping. Unfortunately, there's 700 years of history of use of the term, which sufficiently discourages changing it. (And you - thought parts of Unix were criufty and old!) + thought parts of Unix were crufty and old!) - Insider knowledge: Bank statements are frequently written up from the bank's perspective, which is