1.1 --- a/preface.roff	Tue Jul 10 15:58:46 2012 +0200
     1.2 +++ b/preface.roff	Tue Jul 10 16:49:03 2012 +0200
     1.3 @@ -1,7 +1,7 @@
     1.4  .H0 "Preface" no
     1.5  
     1.6  .P
     1.7 -I have discovered the mail client \fInmh\fP in Fall 2009.
     1.8 +I have discovered the mail client \fInmh\fP in fall 2009.
     1.9  At that time I used \fImutt\fP, as many advanced Unix users do.
    1.10  When I read about nmh, its concepts convinced me at once.
    1.11  The transition from mutt to nmh was similar to beginning with
    1.12 @@ -22,12 +22,12 @@
    1.13  expectations were rather common for modern emailing.
    1.14  As a computer scientist and programmer, I wanted to improve the situation.
    1.15  .P
    1.16 -In Spring 2010, I sent a message to the \fInmh-workers\fP mailing list,
    1.17 +In spring 2010, I sent a message to the \fInmh-workers\fP mailing list,
    1.18  asking for the possibility to offer a Google Summer of Code project for me.
    1.19  Participating in the development of nmh in this manner appeared attractive
    1.20  to me, because I would have been able to work full time on nmh.
    1.21  Although the nmh community had reacted generally positive to the suggestion,
    1.22 -the administrative work for a GSoC project would had been too much.
    1.23 +the administrative work for such a project would had been too much.
    1.24  Nonetheless, my proposal had activated the nmh community.
    1.25  In the following weeks, goals for nmh's future were discussed.
    1.26  In these discussions, I became involved in the
    1.27 @@ -59,7 +59,7 @@
    1.28  was simply set too high.
    1.29  Instead, I improved the code base as I read through it.
    1.30  I found minor bugs for which I proposed fixes.
    1.31 -In the same go, I improved the documentation in minor ways.
    1.32 +Additionally, I improved the documentation in minor ways.
    1.33  When I started with larger code changes,
    1.34  I had to discover that the community was reluctant to change.
    1.35  Its wish for compatibility was much stronger than its
    1.36 @@ -89,6 +89,7 @@
    1.37  .P
    1.38  This document explains the design goals and implementation decisions
    1.39  for mmh.
    1.40 +.\" XXX mmh taucht hier zum ersten mal auf.
    1.41  It discusses technical, historical, social and philosophical considerations.
    1.42  On the technical side, this document
    1.43  explains how an existing project was streamlined by removing rough edges
    1.44 @@ -202,7 +203,8 @@
    1.45  a look into the future of the mmh project.
    1.46  .P
    1.47  .I "Italic font
    1.48 -is used to emphasize new terms.
    1.49 +is used to emphasize new terms, and to name software projects and
    1.50 +man pages.
    1.51  .CW "Constant width font
    1.52  is used to denote names of programs, files,
    1.53  functions, command lines, code excrepts, program input and output.