1.1 --- a/discussion.roff	Thu Jul 12 01:07:44 2012 +0200
     1.2 +++ b/discussion.roff	Thu Jul 12 01:18:02 2012 +0200
     1.3 @@ -339,7 +339,7 @@
     1.4  was removed
     1.5  .Ci 14767c94b3827be7c867196467ed7aea5f6f49b0
     1.6  because its use case of writing to the user's terminal
     1.7 -on receival of mail is obsolete.
     1.8 +on reception of mail is obsolete.
     1.9  If users like to be informed of new mail, the shell's
    1.10  .Ev MAILPATH
    1.11  variable or graphical notifications are technically more appealing.
    1.12 @@ -1713,7 +1713,7 @@
    1.13  .Fu fork()
    1.14  had been an expensive system call, because the process's image needed
    1.15  to be completely duplicated at once.
    1.16 -This expensive work was especially unnecessary in the commonly occuring
    1.17 +This expensive work was especially unnecessary in the commonly occurring
    1.18  case wherein the image is replaced by a call to
    1.19  .Fu exec()
    1.20  right after having forked the child process.
    1.21 @@ -2813,7 +2813,7 @@
    1.22  .P
    1.23  Maintaining compatibility for its own sake is bad,
    1.24  because the code base collects more and more compatibility code.
    1.25 -Sticking to the compatiblity code means remaining limited;
    1.26 +Sticking to the compatibility code means remaining limited;
    1.27  whereas adjusting to the changes renders the compatibility unnecessary.
    1.28  Keeping unused alternatives in the code is a bad choice as they likely
    1.29  gather bugs, by not being well tested.
    1.30 @@ -2927,7 +2927,7 @@
    1.31  (2) Any other whitespace should consist of spaces.
    1.32  These two rules ensure the integrity of the visual appearance.
    1.33  Although reformatting existing code should be avoided, I did it.
    1.34 -I did not waste time arguing; I just reformated the code.
    1.35 +I did not waste time arguing; I just reformatted the code.
    1.36  .Ci a485ed478abbd599d8c9aab48934e7a26733ecb1
    1.37  
    1.38  .U3 "Comments
    1.39 @@ -3784,7 +3784,7 @@
    1.40  .Fn Mail
    1.41  in the home directory.
    1.42  .P
    1.43 -The way MH data is splitted between profile and MH directory is a legacy.
    1.44 +The way MH data is split between profile and MH directory is a legacy.
    1.45  It is only sensible in a situation where the profile is the only
    1.46  configuration file.
    1.47  Why else should the mail storage and the configuration files be intermixed?
    1.48 @@ -3836,7 +3836,7 @@
    1.49  personal MH setup.
    1.50  In nmh, the environment variable
    1.51  .Ev MH
    1.52 -could be used to specifiy a different profile.
    1.53 +could be used to specify a different profile.
    1.54  To operate in the same MH setup with a separate context,
    1.55  the
    1.56  .Ev MHCONTEXT