1.1 --- a/discussion.roff	Sat Jun 30 15:05:06 2012 +0200
     1.2 +++ b/discussion.roff	Sat Jun 30 15:07:35 2012 +0200
     1.3 @@ -11,7 +11,7 @@
     1.4  
     1.5  
     1.6  
     1.7 -.H1 "Stream-Lining
     1.8 +.H1 "Streamlining
     1.9  
    1.10  .P
    1.11  MH had been considered an all-in-one system for mail handling.
    1.12 @@ -50,7 +50,7 @@
    1.13  In consequence, I believe that the available development resources
    1.14  should focus on the point where MH is most unique.
    1.15  This is clearly the user interface \(en the MUA.
    1.16 -Peripheral parts should be removed to stream-line mmh for the MUA task.
    1.17 +Peripheral parts should be removed to streamline mmh for the MUA task.
    1.18  
    1.19  
    1.20  .H2 "Mail Transfer Facilities
    1.21 @@ -269,7 +269,7 @@
    1.22  should be removed.
    1.23  Loosely related and rarely used tools distract from the lean appearance.
    1.24  They require maintenance work without adding much to the core task.
    1.25 -By removing these tools, the project shall become more stream-lined
    1.26 +By removing these tools, the project shall become more streamlined
    1.27  and focused.
    1.28  In mmh the following tools are not available anymore:
    1.29  .BU
    1.30 @@ -366,7 +366,7 @@
    1.31  .Pn msgchk
    1.32  are assumed to be rarely used and can be implemented in different ways,
    1.33  why should one keep them?
    1.34 -Removing them stream-lines mmh.
    1.35 +Removing them streamlines mmh.
    1.36  .Pn viamail 's
    1.37  use case is now partly obsolete and partly covered by
    1.38  .Pn forw ,

     2.1 --- a/preface.roff	Sat Jun 30 15:05:06 2012 +0200
     2.2 +++ b/preface.roff	Sat Jun 30 15:07:35 2012 +0200
     2.3 @@ -91,7 +91,7 @@
     2.4  for mmh.
     2.5  It discusses technical, historical, social and philosophical considerations.
     2.6  On the technical side, this document
     2.7 -explains how an existing project was stream-lined by removing rough edges
     2.8 +explains how an existing project was streamlined by removing rough edges
     2.9  and better exploitation of the central concepts.
    2.10  On the historical side, changes through time are discussed,
    2.11  regarding the use cases and the email features,
    2.12 @@ -113,7 +113,7 @@
    2.13  .P
    2.14  The reader is expected to be familiar with Unix, C and emailing.
    2.15  Good Unix shell knowledge is required, because MH relies fundamentally
    2.16 -on the shell. Without the power of the shell, MH becomes a motorbike
    2.17 +on the shell. Without the power of the shell, MH becomes a motorcycle
    2.18  without winding roads: boring.
    2.19  Introductions to Unix and its shell can be found in ``The UNIX Programming
    2.20  Environment'' by Kernighan and Pike