1.1 --- a/intro.roff	Sun Jul 08 17:25:35 2012 +0200
     1.2 +++ b/intro.roff	Mon Jul 09 11:16:30 2012 +0200
     1.3 @@ -19,6 +19,7 @@
     1.4  .P
     1.5  MH is a conceptual email system design and its concrete implementation.
     1.6  Notably, MH had started as a design proposal at RAND Corporation,
     1.7 +.\" XXX ref to rand corp.
     1.8  where the first implementation followed later.
     1.9  In spirit, MH is similar to Unix, which
    1.10  influenced the world more in being a set of system design concepts
    1.11 @@ -153,7 +154,7 @@
    1.12  peek mh book
    1.13  .], Part II]
    1.14  Rose and Romine provide a deeper and more technical
    1.15 -though slightly outdated introduction in only about two dozens pages.
    1.16 +though slightly outdated introduction in only about two dozen pages.
    1.17  .[
    1.18  rose romine real work
    1.19  .]
    1.20 @@ -203,6 +204,7 @@
    1.21  While clearly separated on the outside,
    1.22  the programs turned out to be fairly interweaved inside.
    1.23  .\" XXX FIXME rewrite...
    1.24 +.\" nicht zweimal ``interweaved''
    1.25  .\" Unfortunately, the clear separation on the outside turned out to be
    1.26  .\" fairly interweaved inside.
    1.27  .P
    1.28 @@ -213,7 +215,7 @@
    1.29  such approaches, but unfortunately, it led to duplicated functions
    1.30  and half-hearted implementation of the concepts.
    1.31  .P
    1.32 -To provide backward-compatibility, it is a common understanding to not
    1.33 +To provide backward-compatibility, it is a common understanding not to
    1.34  change the default settings.
    1.35  In consequence, the user needs to activate modern features explicitly
    1.36  to be able to use them.
    1.37 @@ -224,6 +226,7 @@
    1.38  emailing.
    1.39  The small but mature community around nmh needs few change
    1.40  as they have had their convenient setups for decades.
    1.41 +.\" XXX Explain more
    1.42  
    1.43  
    1.44  .H1 "mmh
    1.45 @@ -251,10 +254,12 @@
    1.46  emphasizing that the project follows my visions and preferences.
    1.47  (My login name is \fImeillo\fP.)
    1.48  This project model was inspired by \fIdwm\fP,
    1.49 +.\" XXX Ref
    1.50  which is Anselm Garbe's personal window manager \(en
    1.51  targeted to satisfy Garbe's personal needs whenever conflicts appear.
    1.52  Dwm had retained its lean elegance and its focused character, whereas
    1.53  its community-driven predecessor \fIwmii\fP had grown fat over time.
    1.54 +.\" XXX ref
    1.55  The development of mmh should remain focused.
    1.56  
    1.57  
    1.58 @@ -311,7 +316,7 @@
    1.59  ideas can be implemented and demonstrated,
    1.60  without the need to change nmh or its community.
    1.61  Of course, the results of the mmh project shall improve nmh, in the end.
    1.62 -By no means is my intend to work against the nmh project.
    1.63 +By no means it is my intent to work against the nmh project.
    1.64  
    1.65  
    1.66  .U2 "Target Field
    1.67 @@ -339,7 +344,7 @@
    1.68  .P
    1.69  The typical users invoke mmh commands directly in an interactive
    1.70  shell session, but they use them to automate mail handling tasks as well.
    1.71 -Likely, they runs their mail setup on a server machine,
    1.72 +Likely, they run their mail setup on a server machine,
    1.73  to which they connect via ssh.
    1.74  They might also have local mmh installations on their workstations,
    1.75  where they tend to work with mmh directly in the shell instead
    1.76 @@ -381,7 +386,7 @@
    1.77  .IP "Modernizing
    1.78  Mmh's feature set needs to become more modern.
    1.79  Better support for attachment and digital cryptography should be added.
    1.80 -MIME support should to be integrated deeper and more naturally.
    1.81 +MIME support should be integrated deeper and more naturally.
    1.82  The modern email features need to be readily available, out-of-the-box.
    1.83  On the other hand,
    1.84  bulletin board support and similar obsolete facilities can be dropped out.