Fix typos for gnuchash/ doc/ bindings/ and misc.

Typos found via `codespell -q 3 -D ~/Projects/codespell/codespell_lib/data/dictionary.txt -S *.po,./po,*.min.js,./ChangeLog*,./NEWS,./doc/README*,./AUTHORS,./libgnucash/tax/us/txf-de*,./data/accounts -L ans,cas,dragable,gae,iff,iif,mut,nd,numer,startd,stoll`

doc/projects.html

@@ -248,7 +248,7 @@
 
     <h2>A Web Browser for Financial Data</h2>
 
-    <p>More and more finacial data is moving onto the web.  
+    <p>More and more financial data is moving onto the web.  
     People shop on-line. They pay bills on-line.  There are
     even some promising e-wallet systems (such as 
     <a href="https://www.webfunds.org">WebFunds</a>).  For GnuCash
@@ -338,7 +338,7 @@
     <dl>
     <dt><b>E-Wallet</b></dt>
     <dd>An e-wallet, just like a real wallet, stores cash.  You
-        can use that cash to pay freinds or businesses.  Just
+        can use that cash to pay friends or businesses.  Just
 	like a real wallet, an e-wallet should not charge you 
 	monthly fees.  It should provide you with some measure
 	of anonymity and privacy.  An e-wallet should also do 
@@ -428,7 +428,7 @@
       <li>Basic Audit features.  There's a problem with blindly
           allowing on-line data (prices, transactions) to enter
 	  GnuCash.  It may not be clear where it came from,
-	  and even if the source is beleived to be 'reputable',
+	  and even if the source is believed to be 'reputable',
 	  there still may be factual errors in the data.  Thus,
 	  there must be a way of audting newly-arrived (or even old)
 	  on-line data, and mark it as 'reconciled', i.e. 
@@ -1215,7 +1215,7 @@
             do you own jewelry? appraised value? etc.)
             In particular, show how appreciation
             and depreciation should be treated.
-            See the section <a href="#arrangments">Arrangements</a> for
+            See the section <a href="#arrangements">Arrangements</a> for
             a discussion of the customization issues.
             </p>
           </li>
@@ -1272,7 +1272,7 @@
             menu. It would be nice to be able to examine different
             account types (Asset, Liability, Income, Expense,
             Payables, Receivables, Inventory) by selecting a tab
-            folder. This is maybe a bs. request that shoudn't 
+            folder. This is maybe a bs. request that shouldn't 
 	    be implemented.</p>
           </li>
 
@@ -1417,7 +1417,7 @@
             <p><b>Print Register Window</b>. Output register window to
                printer.
                <b>Status:</b> Done: there is a register report which
-	       is printable, there is botton on register. Done in 1.6.0
+	       is printable, there is a button on register. Done in 1.6.0
             </p>
           </li>
           <li>
@@ -1536,7 +1536,7 @@
         complex tasks, such as new user setup, account creation, 
         QIF import, budget prep, obscure functional corners.
 	<p>
-	Wizards are great, but lets not thow away the denser GUI's.
+	Wizards are great, but lets not throw away the denser GUI's.
 	For 8-hour-a-day users, the wizards can be irritating. 
 	A single, dense screen can be more efficient and nicer.
 	So when adding wizards, don't dump GUI's !! (instead,
@@ -1583,7 +1583,7 @@
         <p></p>
 
 
-      <dt><a name="arrangements"><b>Arrangments</b></a></dt>
+      <dt><a name="arrangements"><b>Arrangements</b></a></dt>
 
       <dd>
         An "application arrangement" is the defining look-n-feel of an application.
@@ -1622,9 +1622,9 @@
         their own preferred arrangement.   It can also simplify the code base: 
         instead of having two products, a home-user application, and a small-business 
         application, each with a different code base and #defines and what not, instead,
-        we have one code base, and different arrangments for each.
-        However, most importantly, the arrangments should be easy to share between users.
-        They should be such that users are encouraged to trade and use arrangments,
+        we have one code base, and different arrangements for each.
+        However, most importantly, the arrangements should be easy to share between users.
+        They should be such that users are encouraged to trade and use arrangements,
         and to create new ones that suit their needs.
         </p>
         <p>
@@ -1638,7 +1638,7 @@
 	Not started. Individually, all these cusomizable things exist
 	here and there in gnucash, but they cannot be shared between
 	users: a gnucash user cannot mail her favorite 'arrangement'
-	to her freind.
+	to her friend.
 	</p>
 
 
@@ -1767,7 +1767,7 @@
         dates, ISP contract expiration date :-). These may or may
         not be associated with transactions. Memo's should be
         possible. Pop-ups should happen when dates get close.
-        Technology: best bet is the Ximian Evolution Calander
+        Technology: best bet is the Ximian Evolution Calendar
 	component.</p>
 
         <p><b>Design Notes:</b> Most alerts &amp; data storage
@@ -2365,7 +2365,7 @@ next due date mm/dd/yy
 &gt;&gt;  - Export retrieved account data to CBB, Xfinans and QIF files
 &gt;&gt;
 &gt;&gt; With a simple click to an icon on my desktop, ZKA4BTX logs into
-&gt;&gt; T-Online, gets all my account datas from several banks, and writes
+&gt;&gt; T-Online, gets all my account data from several banks, and writes
 &gt;&gt; (adds) it to my CBB, Xfinans or GnuCash (QIF) files.
 &gt;&gt;
 &gt;&gt; Another very important thing is that I can do all my transfers