docs/master

diff discussion.roff @ 125:0e102cec0c73

s/stream-line/streamline/; s/motorbike/motorcycle/
author markus schnalke <meillo@marmaro.de>
date Sat, 30 Jun 2012 15:07:35 +0200
parents 3d30fd938aa9
children 3aafbd32d77b
line diff
     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 ,