1.1 --- a/intro.roff	Mon Jul 09 22:32:24 2012 +0200
     1.2 +++ b/intro.roff	Mon Jul 09 23:42:59 2012 +0200
     1.3 @@ -38,7 +38,7 @@
     1.4  Before the prototype's existence, the concept was
     1.5  believed to be practically unusable.
     1.6  But the prototype proved successful and replaced MS thereafter.
     1.7 -In replacing MS, MH grew to an all-in-one mail system.
     1.8 +In replacing MS, MH grew to provide anything necessary for emailing.
     1.9  .P
    1.10  In the early eighties,
    1.11  the University of California at Irvine (UCI) started to use MH.
    1.12 @@ -83,7 +83,8 @@
    1.13  The specific format of the mail storage characterizes MH in the same way
    1.14  as the format of the file system characterizes Unix.
    1.15  .P
    1.16 -MH tools maintain a \fIcontext\fP, which includes the current mail folder.
    1.17 +MH tools maintain a \fIcontext\fP, which includes for instance the
    1.18 +current mail folder.
    1.19  Processes in Unix have a similar context, containing the current working
    1.20  directory, for instance. In contrast, the process context is maintained
    1.21  by the Unix kernel automatically, whereas MH tools need to maintain the MH
    1.22 @@ -91,8 +92,9 @@
    1.23  The user can have one MH context or multiple ones; he can even share it
    1.24  with others.
    1.25  .P
    1.26 -Messages are named by their numeric filename, but they can have symbolic names,
    1.27 -too. These are either automatically updated
    1.28 +Messages are named by their numeric filename,
    1.29 +but they can have symbolic names, too.
    1.30 +These are either automatically updated
    1.31  position names such as the next or the last message,
    1.32  or user-settable group names for arbitrary sets of messages.
    1.33  These names are called sequences.
    1.34 @@ -101,8 +103,8 @@
    1.35  The user's \fIprofile\fP is a file that contains his MH configuration.
    1.36  Default switches for the individual tools can be specified to
    1.37  adjust them to the user's personal preferences.
    1.38 -Multiple versions of the same command with different
    1.39 -default values can also be created very easily.
    1.40 +Additionally, a single command can be linked under different names
    1.41 +with different default values easily.
    1.42  Form templates for new messages or for replies are easily changeable,
    1.43  and output is adjustable with format files.
    1.44  Almost every part of the system can be adjusted to personal preference.
    1.45 @@ -177,7 +179,8 @@
    1.46  Then it grew, spread and adapted to the changes email went through.
    1.47  Its core-concepts, however, remained the same.
    1.48  During the eighties, students at UCI actively worked on MH.
    1.49 -They added new features and optimized the code for the then popular systems.
    1.50 +They added new features and optimized the code for the systems
    1.51 +popular at that time.
    1.52  All this still was in times before POSIX and ANSI C.
    1.53  As large parts of the code stem from this time, today's nmh source code
    1.54  still contains many ancient parts.
    1.55 @@ -231,6 +234,7 @@
    1.56  
    1.57  .H1 "mmh
    1.58  .P
    1.59 +.\" XXX which version did I ``fork''?
    1.60  I started to work on my experimental version in October 2011,
    1.61  at a time when there had been no more than three commits to nmh
    1.62  since the beginning of the year.
    1.63 @@ -247,6 +251,7 @@
    1.64  After long years of stagnation, nmh became actively developed again.
    1.65  Hence, while I was working on mmh, the community was once more working
    1.66  on nmh, in parallel.
    1.67 +.\" XXX interaction between nmh and mmh
    1.68  .P
    1.69  The name \fImmh\fP may stand for \fImodern mail handler\fP,
    1.70  because the project tries to modernize nmh.
    1.71 @@ -314,7 +319,7 @@
    1.72  .P
    1.73  The mmh project provides the basis on which the aforementioned
    1.74  ideas can be implemented and demonstrated,
    1.75 -without the need to change nmh or its community.
    1.76 +without the need to change the nmh project or its community.
    1.77  Of course, the results of the mmh project shall improve nmh, in the end.
    1.78  By no means it is my intent to work against the nmh project.
    1.79  
    1.80 @@ -339,8 +344,8 @@
    1.81  non-ASCII text, and digital cryptography.
    1.82  They are able to setup email system components besides mmh,
    1.83  and actually like to have the choice to pick the ones they prefer.
    1.84 -They have a reasonably modern operating system that complies to standards,
    1.85 -like POSIX and ANSI C.
    1.86 +They have a reasonably modern operating system that complies to the
    1.87 +POSIX and ANSI C standards.
    1.88  .P
    1.89  The typical users invoke mmh commands directly in an interactive
    1.90  shell session, but they use them to automate mail handling tasks as well.
    1.91 @@ -385,7 +390,8 @@
    1.92  All tools should be tightly shaped.
    1.93  .IP "Modernizing
    1.94  Mmh's feature set needs to become more modern.
    1.95 -Better support for attachment and digital cryptography should be added.
    1.96 +Better support for attachments, digital signatures and message encryption
    1.97 +should be added.
    1.98  MIME support should be integrated deeper and more naturally.
    1.99  The modern email features need to be readily available, out-of-the-box.
   1.100  On the other hand,