1.1 --- a/intro.roff	Mon Jul 02 23:14:19 2012 +0200
     1.2 +++ b/intro.roff	Tue Jul 03 11:11:12 2012 +0200
     1.3 @@ -165,7 +165,7 @@
     1.4  .VF input/mh-session
     1.5  
     1.6  
     1.7 -.H1 "nmh: Code and Community
     1.8 +.H1 "nmh
     1.9  .P
    1.10  In order to understand the condition, goals and dynamics of a project,
    1.11  one needs to know the reasons behind them.
    1.12 @@ -377,6 +377,7 @@
    1.13  appealing MUA should be removed.
    1.14  This includes the mail submission and mail retrieval facilities.
    1.15  Choice should be reduced to the main options.
    1.16 +All tools should be tightly shaped.
    1.17  .IP "Modernizing
    1.18  Mmh's feature set needs to become more modern.
    1.19  Better support for attachment and digital cryptography should be added.
    1.20 @@ -384,9 +385,10 @@
    1.21  The modern email features need to be readily available, out-of-the-box.
    1.22  On the other hand,
    1.23  bulletin board support and similar obsolete facilities can be dropped out.
    1.24 -Likewise, ancient technologies such as hardcopy terminals
    1.25 -need not to be supported any further.
    1.26 -.IP "Code style
    1.27 +Likewise, ancient technologies should not be supported any further.
    1.28 +The available concepts need to be expanded as far as possible.
    1.29 +A small set of concepts should recur consistently.
    1.30 +.IP "Styling
    1.31  Mmh's source code needs to be updated to modern standards.
    1.32  Standardized library functions should replace non-standard versions
    1.33  whenever possible.
    1.34 @@ -394,8 +396,5 @@
    1.35  Time and space optimizations should to be replaced by
    1.36  clear and readable code.
    1.37  A uniform programming style should prevail.
    1.38 -.IP "Homogeneity
    1.39 -The available concepts need to be expanded as far as possible.
    1.40 -A small set of concepts should recur consistently.
    1.41  The whole system should appear to be of-one-style;
    1.42  it should feel like being cast as one.