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

--- a/discussion.roff	Thu Jul 12 01:07:44 2012 +0200
+++ b/discussion.roff	Thu Jul 12 01:18:02 2012 +0200
@@ -339,7 +339,7 @@
 was removed
 .Ci 14767c94b3827be7c867196467ed7aea5f6f49b0
 because its use case of writing to the user's terminal
-on receival of mail is obsolete.
+on reception of mail is obsolete.
 If users like to be informed of new mail, the shell's
 .Ev MAILPATH
 variable or graphical notifications are technically more appealing.
@@ -1713,7 +1713,7 @@
 .Fu fork()
 had been an expensive system call, because the process's image needed
 to be completely duplicated at once.
-This expensive work was especially unnecessary in the commonly occuring
+This expensive work was especially unnecessary in the commonly occurring
 case wherein the image is replaced by a call to
 .Fu exec()
 right after having forked the child process.
@@ -2813,7 +2813,7 @@
 .P
 Maintaining compatibility for its own sake is bad,
 because the code base collects more and more compatibility code.
-Sticking to the compatiblity code means remaining limited;
+Sticking to the compatibility code means remaining limited;
 whereas adjusting to the changes renders the compatibility unnecessary.
 Keeping unused alternatives in the code is a bad choice as they likely
 gather bugs, by not being well tested.
@@ -2927,7 +2927,7 @@
 (2) Any other whitespace should consist of spaces.
 These two rules ensure the integrity of the visual appearance.
 Although reformatting existing code should be avoided, I did it.
-I did not waste time arguing; I just reformated the code.
+I did not waste time arguing; I just reformatted the code.
 .Ci a485ed478abbd599d8c9aab48934e7a26733ecb1
 
 .U3 "Comments
@@ -3784,7 +3784,7 @@
 .Fn Mail
 in the home directory.
 .P
-The way MH data is splitted between profile and MH directory is a legacy.
+The way MH data is split between profile and MH directory is a legacy.
 It is only sensible in a situation where the profile is the only
 configuration file.
 Why else should the mail storage and the configuration files be intermixed?
@@ -3836,7 +3836,7 @@
 personal MH setup.
 In nmh, the environment variable
 .Ev MH
-could be used to specifiy a different profile.
+could be used to specify a different profile.
 To operate in the same MH setup with a separate context,
 the
 .Ev MHCONTEXT

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

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