1.1 --- a/intro.roff	Tue Jul 10 15:58:46 2012 +0200
     1.2 +++ b/intro.roff	Tue Jul 10 16:49:03 2012 +0200
     1.3 @@ -64,7 +64,7 @@
     1.4  Today, nmh has almost completely replaced the original MH.
     1.5  Some systems might still provide old MH, but mainly for historical reasons.
     1.6  .P
     1.7 -In the last years, the work on nmh was mostly maintenance work.
     1.8 +In the last years, the changes in nmh were mostly maintenance work.
     1.9  However, the development was revived in December 2011
    1.10  and stayed busy since then.
    1.11  
    1.12 @@ -200,16 +200,16 @@
    1.13  .P
    1.14  Despite the separation of the tool chest approach at the surface
    1.15  \(en a collection of small, separate programs \(en
    1.16 -on the source code level, it is much more interweaved.
    1.17 +on the source code level, it is much more interwoven.
    1.18  Several separate components were compiled into one program
    1.19  for efficiency reasons.
    1.20  This led to intricate innards.
    1.21  While clearly separated on the outside,
    1.22 -the programs turned out to be fairly interweaved inside.
    1.23 +the programs turned out to be fairly interwoven inside.
    1.24  .\" XXX FIXME rewrite...
    1.25 -.\" nicht zweimal ``interweaved''
    1.26 +.\" nicht zweimal ``interwoven''
    1.27  .\" Unfortunately, the clear separation on the outside turned out to be
    1.28 -.\" fairly interweaved inside.
    1.29 +.\" fairly interwoven inside.
    1.30  .P
    1.31  The advent of MIME raised the complexity of email by a magnitude.
    1.32  This is visible in nmh. The MIME-related parts are the most complex ones.
    1.33 @@ -224,9 +224,10 @@
    1.34  to be able to use them.
    1.35  This puts a burden on new users, because out-of-the-box nmh remains
    1.36  in the same ancient style.
    1.37 -If nmh is seen to be a back-end, then this compatibility surely is important.
    1.38 -However, in the same go, new users have difficulties using nmh for modern
    1.39 -emailing.
    1.40 +If nmh is seen to be a back-end,
    1.41 +then this compatibility surely is important.
    1.42 +However, at the same time, new users have difficulties using nmh for
    1.43 +modern emailing.
    1.44  The small but mature community around nmh needs few change
    1.45  as they have had their convenient setups for decades.
    1.46  .\" XXX Explain more
    1.47 @@ -381,7 +382,7 @@
    1.48  .IP "Streamlining
    1.49  Mmh should be stripped down to its core, which is the user agent (MUA).
    1.50  The feature set should be distilled to the indispensable ones,
    1.51 -effectively removing corner-cases.
    1.52 +effectively removing corner cases.
    1.53  Parts that don't add to the main task of being a conceptionally
    1.54  appealing MUA should be removed.
    1.55  This includes the mail submission and mail retrieval facilities.