Fix some simple typos

hledger-lib/Hledger/Read/Common.hs

@@ -1020,7 +1020,7 @@ emptyorcommentlinep = do
 -- Several journal items may be followed by comments, which begin with
 -- semicolons and extend to the end of the line. Such comments may span
 -- multiple lines, but comment lines below the journal item must be
--- preceeded by leading whitespace.
+-- preceded by leading whitespace.
 --
 -- This parser combinator accepts a parser that consumes all input up
 -- until the next newline. This parser should extract the "content" from
@@ -1077,7 +1077,7 @@ followingcommentp =
 -- The first line of a transaction may be followed by comments, which
 -- begin with semicolons and extend to the end of the line. Transaction
 -- comments may span multiple lines, but comment lines below the
--- transaction must be preceeded by leading whitespace.
+-- transaction must be preceded by leading whitespace.
 --
 -- 2000/1/1 ; a transaction comment starting on the same line ...
 --   ; extending to the next line
@@ -1131,7 +1131,7 @@ commenttagsp = do
 --
 -- Postings may be followed by comments, which begin with semicolons and
 -- extend to the end of the line. Posting comments may span multiple
--- lines, but comment lines below the posting must be preceeded by
+-- lines, but comment lines below the posting must be preceded by
 -- leading whitespace.
 --
 -- 2000/1/1

hledger-web/static/js/excanvas.js

@@ -50,7 +50,7 @@ if (!document.createElement('canvas').getContext) {
   var Z2 = Z / 2;
 
   /**
-   * This funtion is assigned to the <canvas> elements as element.getContext().
+   * This function is assigned to the <canvas> elements as element.getContext().
    * @this {HTMLElement}
    * @return {CanvasRenderingContext2D_}
    */

hledger/CHANGES.md

@@ -445,7 +445,7 @@ User-visible changes in the hledger command line tool and library.
 
     It seems the simple and really only way to do this reliably is to require
     an explicit decimal point character. Most folks probably do this already.
-    Unfortunately, it makes another potential incompatiblity with ledger and
+    Unfortunately, it makes another potential incompatibility with ledger and
     beancount journals. But the error message will be clear and easy to
     work around.
 

hledger/hledger.1

@@ -829,7 +829,7 @@ tab(@);
 l.
 T{
 \f[C]-p \[dq]weekly from 2009/1/1 to 2009/4/1\[dq]\f[R] -- starts on
-2008/12/29, closest preceeding Monday
+2008/12/29, closest preceding Monday
 T}
 T{
 \f[C]-p \[dq]monthly in 2008/11/25\[dq]\f[R] -- starts on 2018/11/01
@@ -863,7 +863,7 @@ T{
 boundaries on 2008/01/01, 2008/03/01, ...
 T}
 T{
-\f[C]-p \[dq]every 2 weeks\[dq]\f[R] -- starts on closest preceeding
+\f[C]-p \[dq]every 2 weeks\[dq]\f[R] -- starts on closest preceding
 Monday
 T}
 T{

hledger/hledger.info

@@ -628,7 +628,7 @@ date.
 
    For example:
 
-'-p "weekly from 2009/1/1 to 2009/4/1"' - starts on 2008/12/29, closest preceeding Monday
+'-p "weekly from 2009/1/1 to 2009/4/1"' - starts on 2008/12/29, closest preceding Monday
 '-p "monthly in 2008/11/25"' - starts on 2018/11/01
 '-p "quarterly from 2009-05-05 to 2009-06-01"' - starts on 2009/04/01, ends on 2009/06/30, which are first and last days of Q2 2009
 '-p "yearly from 2009-12-29"' - starts on 2009/01/01, first day of 2009
@@ -643,7 +643,7 @@ end on the last one, as described above.
    Examples:
 
 '-p "bimonthly from 2008"' - periods will have boundaries on 2008/01/01, 2008/03/01, ...
-'-p "every 2 weeks"' - starts on closest preceeding Monday
+'-p "every 2 weeks"' - starts on closest preceding Monday
 '-p "every 5 month from 2009/03"' - periods will have boundaries on 2009/03/01, 2009/08/01, ...
 
    If you want intervals that start on arbitrary day of your choosing

hledger/hledger.txt

@@ -581,7 +581,7 @@ OPTIONS
        will  have  boundaries  on  2008/01/01,
        2008/03/01, ...
        -p "every 2 weeks" -- starts on closest
-       preceeding Monday
+       preceding Monday
        -p  "every 5 month from 2009/03" -- pe-
        riods   will   have    boundaries    on
        2009/03/01, 2009/08/01, ...

hledger/hledger_options.m4.md

@@ -339,7 +339,7 @@ associated period expression specifies different explicit start and end date.
 For example:
 
 ------------------------------------------
-`-p "weekly from 2009/1/1 to 2009/4/1"` -- starts on 2008/12/29, closest preceeding Monday
+`-p "weekly from 2009/1/1 to 2009/4/1"` -- starts on 2008/12/29, closest preceding Monday
 `-p "monthly in 2008/11/25"` -- starts on 2018/11/01                  
 `-p "quarterly from 2009-05-05 to 2009-06-01"` - starts on 2009/04/01, ends on 2009/06/30, which are first and last days of Q2 2009 
 `-p "yearly from 2009-12-29"` - starts on 2009/01/01, first day of 2009
@@ -358,7 +358,7 @@ Examples:
 
 ------------------------------------------
 `-p "bimonthly from 2008"` -- periods will have boundaries on 2008/01/01, 2008/03/01, ...
-`-p "every 2 weeks"`  -- starts on closest preceeding Monday
+`-p "every 2 weeks"`  -- starts on closest preceding Monday
 `-p "every 5 month from 2009/03"` -- periods will have boundaries on 2009/03/01, 2009/08/01, ...
 ------------------------------------------