1.1 --- a/discussion.roff	Sun Jun 24 21:42:23 2012 +0200
     1.2 +++ b/discussion.roff	Sun Jun 24 21:59:29 2012 +0200
     1.3 @@ -70,7 +70,7 @@
     1.4  .], p. xviii]
     1.5  .QS
     1.6  Second, I limited myself to the routing function \(en
     1.7 -I wouldn't write user agents or delivery backends.
     1.8 +I wouldn't write user agents or delivery back-ends.
     1.9  This was a departure of the dominant through of the time,
    1.10  in which routing logic, local delivery, and often the network code
    1.11  were incorporated directly into the user agents.
    1.12 @@ -1018,7 +1018,7 @@
    1.13  to deal with the problem.
    1.14  Working on an experimental branch without an established user base,
    1.15  eased my work because I did not offend users when I removed existing
    1.16 -funtions.
    1.17 +functions.
    1.18  .P
    1.19  Rose and Romine counted 24 visible and 9 more hidden switches for
    1.20  .Pn send .
    1.21 @@ -1071,7 +1071,7 @@
    1.22  .[
    1.23  rose romine real work
    1.24  .]
    1.25 -Since then, the facility had existed but was deactivated by default.
    1.26 +Since then, the facility had existed but was inactive by default.
    1.27  The default activation and the related rework of the tools made it
    1.28  possible to remove the
    1.29  .Sw -[no]draftfolder ,
    1.30 @@ -1141,7 +1141,7 @@
    1.31  With
    1.32  .Sw -inplace ,
    1.33  the digest had been replaced by the table of contents (i.e. the
    1.34 -introduction text) and the bursted messages were placed right
    1.35 +introduction text) and the burst messages were placed right
    1.36  after this message, renumbering all following messages.
    1.37  Also, any trailing text of the digest was lost, though,
    1.38  in practice, it usually consists of an end-of-digest marker only.
    1.39 @@ -1658,7 +1658,7 @@
    1.40  functionality I considered ancient.
    1.41  The need for consensus with peers would have slowed this process down.
    1.42  Without the need to justify my decisions, I was able to rush forward.
    1.43 -In Dezember 2011, Paul Vixie motivated the nmh developers to just
    1.44 +In December 2011, Paul Vixie motivated the nmh developers to just
    1.45  do the work:
    1.46  .[
    1.47  paul vixie edginess nmh-workers
    1.48 @@ -1927,7 +1927,7 @@
    1.49  The idea is having a main text document with files of arbitrary kind
    1.50  attached to it.
    1.51  In MIME terms, this is a multi-part message having a text part first
    1.52 -and parts of arbitray type following.
    1.53 +and parts of arbitrary type following.
    1.54  .P
    1.55  MH's MIME support is a direct implementation of the RFCs.
    1.56  The perception of the topic described in the RFCs is clearly visible
    1.57 @@ -1964,7 +1964,7 @@
    1.58  .LP
    1.59  Unfortunately, the attachment system,
    1.60  like any new facilities in nmh,
    1.61 -was deactive by default.
    1.62 +was inactive by default.
    1.63  .P
    1.64  During my work in Argentina, I tried to improve the attachment system.
    1.65  But, because of great opposition in the nmh community,
    1.66 @@ -1972,7 +1972,7 @@
    1.67  .[
    1.68  nmh-workers attachment proposal
    1.69  .]
    1.70 -In Januar 2012, I extended the patch and applied it to mmh.
    1.71 +In January 2012, I extended the patch and applied it to mmh.
    1.72  .Ci 8ff284ff9167eff8f5349481529332d59ed913b1
    1.73  In mmh, the attachment system is active by default.
    1.74  Instead of command line switches, the
    1.75 @@ -2055,7 +2055,7 @@
    1.76  Then, at the WhatNow prompt, he needs to invoke
    1.77  .Cl "edit mhbuild
    1.78  to convert it to MIME.
    1.79 -Because the resulting draft does neither contain non-aASCII characters
    1.80 +Because the resulting draft does neither contain non-ASCII characters
    1.81  nor has it attachment headers, the attachment system will not touch it.
    1.82  .P
    1.83  The approach taken in mmh is taylored towards todays most common case:
    1.84 @@ -2174,7 +2174,7 @@
    1.85  .LP
    1.86  Now, the outcome of mmh's
    1.87  .Cl "mhstore -auto
    1.88 -can be forseen from the output of
    1.89 +can be foreseen from the output of
    1.90  .Cl "mhlist -verbose" .
    1.91  .P
    1.92  The
    1.93 @@ -2449,8 +2449,8 @@
    1.94  draft folder facility exists.
    1.95  It had been introduced already in July 1984
    1.96  by Marshall T. Rose.
    1.97 -The facility was deactivated by default.
    1.98 -Even in nmh, the draft folder facility remained deactivated by default.
    1.99 +The facility was inactive by default.
   1.100 +Even in nmh, the draft folder facility remained inactive by default.
   1.101  At least, Richard Coleman added the man page
   1.102  .Mp mh-draft(5)
   1.103  to document