1.1 --- a/preface.roff	Sun May 20 11:40:19 2012 +0200
     1.2 +++ b/preface.roff	Sun May 20 12:11:42 2012 +0200
     1.3 @@ -10,7 +10,7 @@
     1.4  .U2 "Background to this Thesis
     1.5  .P
     1.6  I have discovered nmh in September 2009. At that time I used to use the
     1.7 -mail client \fImutt\fP, like many advanced Unix users do.
     1.8 +mail client \fImutt\fP, as many advanced Unix users do.
     1.9  As I read about nmh, its concepts had convinced me at once.
    1.10  Learning its different model of email handling had been relatively easy,
    1.11  because my starting situation was being convinced of the concepts.
    1.12 @@ -19,13 +19,13 @@
    1.13  managers, or like editing with vi when being used to modeless editors.
    1.14  Such a change is not trivial, but in being convinced by the
    1.15  concepts and by having done similar transitions for file management
    1.16 -and editing already, it was not too difficult neither.
    1.17 +and editing already, it was neither too difficult.
    1.18  In contrast, setting up nmh to a convenient state became a tedious task
    1.19  that took several months.
    1.20  .P
    1.21  Once having nmh arranged to a convenient state, I enjoyed using it
    1.22  because of its conceptional elegance and its scripting capabilities.
    1.23 -On the other hand, however, it still was
    1.24 +On the other hand, nevertheless, it still was
    1.25  inconvenient for handling attachments, non-ASCII character encodings,
    1.26  and similar features of modern emailing.
    1.27  My setup demanded more and more additional configuration and helper scripts
    1.28 @@ -37,7 +37,7 @@
    1.29  In Spring 2010, I asked on the \fInmh-workers\fP mailing list for the
    1.30  possibility to offer a Google Summer of Code project.
    1.31  Participating in the development this way appeared attractive to me,
    1.32 -as it would have been possible to have the project
    1.33 +because it would have been possible to have the project
    1.34  accepted at university. Although generally the nmh community
    1.35  had been positive on the
    1.36  suggestion, the administrative work had been to much, eventually.
    1.37 @@ -76,7 +76,7 @@
    1.38  larger code changes, I had to discover that the community was reluctant
    1.39  to change. Its wish for compatibility was much stronger than its
    1.40  wish for convenient out-of-the-box setups \(en in contrast to my opinion.
    1.41 -This lead to long discussions, again.
    1.42 +This led to long discussions, again.
    1.43  I came to understand their point of view, but it is different to mine.
    1.44  At the end of my three-month project, I had become familiar with
    1.45  nmh's code base and community. I had improved the project in minor ways,
    1.46 @@ -84,7 +84,7 @@
    1.47  .P
    1.48  Another half a year later, the end of my studies came within reach.
    1.49  I needed a topic for my master's thesis.
    1.50 -There was no question: I wanted to work on nmh.
    1.51 +No question, I wanted to work on nmh.
    1.52  But well, not exactly on nmh,
    1.53  because I had accepted that the nmh community has different goals
    1.54  than I have. This would result in much discussion and thus little progress.
    1.55 @@ -116,11 +116,11 @@
    1.56  .P
    1.57  This document is written for the community around MH-like mail systems,
    1.58  including developers and users.
    1.59 -First of all, the document shall explain the design goals and
    1.60 -implementation decisions for mmh. But as well, it shall clarify my
    1.61 +First, the document explains the design goals and
    1.62 +implementation decisions for mmh. But as well, it clarifies my
    1.63  personal perception of the
    1.64  concepts of MH and Unix, and explain my therefrom resulting point of view.
    1.65 -Despite the focus on MH-like systems, this document may be worthwhile
    1.66 +Despite the focus on MH-like systems, this document is may be precious
    1.67  to anyone interested in the Unix philosophy and anyone in contact to
    1.68  old software projects, be it code or community-related.
    1.69  .P
    1.70 @@ -146,8 +146,8 @@
    1.71  kernighan ritchie c prog lang
    1.72  .]
    1.73  is the definitive guide to C.
    1.74 -Some book about system-level C programming is worthwhile additional
    1.75 -literature. Rochkind and Curry have written such books.
    1.76 +Some book about system-level C programming can be helpful
    1.77 +additional literature. Rochkind and Curry have written such books.
    1.78  .[
    1.79  rochkind advanced unix prog
    1.80  .]
    1.81 @@ -193,9 +193,9 @@
    1.82  This document is neither a user's tutorial to mmh nor an introduction
    1.83  to any of the topics covered. It discusses Unix, email
    1.84  and system design on an advanced level.
    1.85 -However, as knowledge of the fundamental concepts is the most valuable
    1.86 +Nevertheless, as knowledge of the fundamental concepts is the most valuable
    1.87  information a user can acquire about some program or software system,
    1.88 -this document might be worth a read for non-developers as well.
    1.89 +this document may be worth a read for non-developers as well.
    1.90  
    1.91  
    1.92  .U2 "Organization