1.1 --- a/colophon.roff	Thu Jul 12 01:07:44 2012 +0200
     1.2 +++ b/colophon.roff	Thu Jul 12 01:18:02 2012 +0200
     1.3 @@ -3,8 +3,8 @@
     1.4  This document was typeset with the
     1.5  .I troff
     1.6  document preparation system on Unix.
     1.7 -After having typset my diploma thesis with LaTeX,
     1.8 -the choice for troff was similar to prefering MH over mutt.
     1.9 +After having typeset my diploma thesis with LaTeX,
    1.10 +the choice for troff was similar to preferring MH over mutt.
    1.11  .P
    1.12  I used the troff implementation of the Heirloom doctools,
    1.13  and built upon the

     2.1 --- a/discussion.roff	Thu Jul 12 01:07:44 2012 +0200
     2.2 +++ b/discussion.roff	Thu Jul 12 01:18:02 2012 +0200
     2.3 @@ -339,7 +339,7 @@
     2.4  was removed
     2.5  .Ci 14767c94b3827be7c867196467ed7aea5f6f49b0
     2.6  because its use case of writing to the user's terminal
     2.7 -on receival of mail is obsolete.
     2.8 +on reception of mail is obsolete.
     2.9  If users like to be informed of new mail, the shell's
    2.10  .Ev MAILPATH
    2.11  variable or graphical notifications are technically more appealing.
    2.12 @@ -1713,7 +1713,7 @@
    2.13  .Fu fork()
    2.14  had been an expensive system call, because the process's image needed
    2.15  to be completely duplicated at once.
    2.16 -This expensive work was especially unnecessary in the commonly occuring
    2.17 +This expensive work was especially unnecessary in the commonly occurring
    2.18  case wherein the image is replaced by a call to
    2.19  .Fu exec()
    2.20  right after having forked the child process.
    2.21 @@ -2813,7 +2813,7 @@
    2.22  .P
    2.23  Maintaining compatibility for its own sake is bad,
    2.24  because the code base collects more and more compatibility code.
    2.25 -Sticking to the compatiblity code means remaining limited;
    2.26 +Sticking to the compatibility code means remaining limited;
    2.27  whereas adjusting to the changes renders the compatibility unnecessary.
    2.28  Keeping unused alternatives in the code is a bad choice as they likely
    2.29  gather bugs, by not being well tested.
    2.30 @@ -2927,7 +2927,7 @@
    2.31  (2) Any other whitespace should consist of spaces.
    2.32  These two rules ensure the integrity of the visual appearance.
    2.33  Although reformatting existing code should be avoided, I did it.
    2.34 -I did not waste time arguing; I just reformated the code.
    2.35 +I did not waste time arguing; I just reformatted the code.
    2.36  .Ci a485ed478abbd599d8c9aab48934e7a26733ecb1
    2.37  
    2.38  .U3 "Comments
    2.39 @@ -3784,7 +3784,7 @@
    2.40  .Fn Mail
    2.41  in the home directory.
    2.42  .P
    2.43 -The way MH data is splitted between profile and MH directory is a legacy.
    2.44 +The way MH data is split between profile and MH directory is a legacy.
    2.45  It is only sensible in a situation where the profile is the only
    2.46  configuration file.
    2.47  Why else should the mail storage and the configuration files be intermixed?
    2.48 @@ -3836,7 +3836,7 @@
    2.49  personal MH setup.
    2.50  In nmh, the environment variable
    2.51  .Ev MH
    2.52 -could be used to specifiy a different profile.
    2.53 +could be used to specify a different profile.
    2.54  To operate in the same MH setup with a separate context,
    2.55  the
    2.56  .Ev MHCONTEXT

     3.1 --- a/preface.roff	Thu Jul 12 01:07:44 2012 +0200
     3.2 +++ b/preface.roff	Thu Jul 12 01:18:02 2012 +0200
     3.3 @@ -232,7 +232,7 @@
     3.4  Not every change is described because that would bore the reader.
     3.5  Instead, important changes and those standing for a set of similar
     3.6  changes are described and discussed.
     3.7 -Chapter 3 finishes up by summarizing the achivements and taking
     3.8 +Chapter 3 finishes up by summarizing the achievements and taking
     3.9  a look into the future of the mmh project.
    3.10  .P
    3.11  .I "Italic font
    3.12 @@ -240,7 +240,7 @@
    3.13  literature, and man pages.
    3.14  .CW "Constant width font
    3.15  is used to denote names of programs, files,
    3.16 -functions, command lines, code excrepts, program input and output.
    3.17 +functions, command lines, code excerpts, program input and output.
    3.18  .P
    3.19  References to man pages are printed as ``\c
    3.20  .Mp cat (1)''.
    3.21 @@ -250,7 +250,7 @@
    3.22  Internet technologies are specified by \fIRequests for Comments\fP (RFCs).
    3.23  Throughout the document, they are referenced similar to ``RFC\|821''.
    3.24  A list of relevant RFCs is located at the end of the document.
    3.25 -Literature is cited in backets, such as
    3.26 +Literature is cited in brackets, such as
    3.27  .[ ``[
    3.28  kernighan pike unix programming env
    3.29  .]]''.

     4.1 --- a/summary.roff	Thu Jul 12 01:07:44 2012 +0200
     4.2 +++ b/summary.roff	Thu Jul 12 01:18:02 2012 +0200
     4.3 @@ -93,7 +93,7 @@
     4.4  .\" a result of greater pureness.
     4.5  .P
     4.6  While I worked on mmh, nmh's community became very active as well.
     4.7 -Although we both worked on the same code base, there was no collaberation.
     4.8 +Although we both worked on the same code base, there was no collaboration.
     4.9  This, I must admit, was my failure because I kept my work hidden
    4.10  from the nmh community.
    4.11  The reasons are personal and community-related.