docs/master

changeset 228:a1468cf505fd

Spellchecked.
author markus schnalke <meillo@marmaro.de>
date Sun, 15 Jul 2012 23:58:14 +0200
parents 157c92fc1597
children a03308feb1f2
files colophon.roff discussion.roff intro.roff summary.roff
diffstat 4 files changed, 13 insertions(+), 13 deletions(-) [+]
line diff
     1.1 --- a/colophon.roff	Sun Jul 15 23:44:15 2012 +0200
     1.2 +++ b/colophon.roff	Sun Jul 15 23:58:14 2012 +0200
     1.3 @@ -12,7 +12,7 @@
     1.4  .I ms
     1.5  macro package.
     1.6  To meet my personal wishes, I added further macros and replaced
     1.7 -clumpsy parts of ms.
     1.8 +clumsy parts of ms.
     1.9  My own macro code comprises about 400 lines.
    1.10  Unfortunately, I must admit that the troff sources are not perfectly
    1.11  portable as I accessed Heirloom troff extensions and ms internals,
    1.12 @@ -33,7 +33,7 @@
    1.13  .I "Nroff/Troff User's Manual
    1.14  helped with definitive answers.
    1.15  .P
    1.16 -The mail agent diagramm was written in
    1.17 +The mail agent diagram was written in
    1.18  .I pic .
    1.19  The figures displaying the number of switches and the amount of
    1.20  code through time were created with
    1.21 @@ -53,7 +53,7 @@
    1.22  Dimitar Zhekov's \fITerminus\fP font.
    1.23  Both are free typefaces.
    1.24  .P
    1.25 -The layout of the inner pages of this document were modelled after
    1.26 +The layout of the inner pages of this document were modeled after
    1.27  the German book \fIEinf\[udieresis]hrung in die Automatentheorie,
    1.28  Formale Sprache und Komplexit\[adieresis]tstheorie\fP
    1.29  by Hopcroft and Ullman, Addison-Wesley, 1990.
     2.1 --- a/discussion.roff	Sun Jul 15 23:44:15 2012 +0200
     2.2 +++ b/discussion.roff	Sun Jul 15 23:58:14 2012 +0200
     2.3 @@ -189,7 +189,7 @@
     2.4  .P
     2.5  As it had already been possible to use an external MSA and MRA,
     2.6  why should the internal version not be kept for convenience?
     2.7 -Transfered to a different area, the question,
     2.8 +Transferred to a different area, the question,
     2.9  whether there is sense in having a fall-back pager in all
    2.10  the command line tools for the cases when
    2.11  .Pn more
    2.12 @@ -1319,7 +1319,7 @@
    2.13  .Mp mhbuild (1)
    2.14  man page states that
    2.15  ``This provides an accurate count at the expense of a small delay''
    2.16 -with the small delay not being noticable on modern systems.
    2.17 +with the small delay not being noticeable on modern systems.
    2.18  .P
    2.19  The
    2.20  .Sw -[no]check
    2.21 @@ -2830,7 +2830,7 @@
    2.22  The number of tabs corresponds to the nesting level \(en
    2.23  one tab, one level.
    2.24  Tab characters provide flexible visual appearance because developers
    2.25 -can adjust their width as prefered.
    2.26 +can adjust their width as preferred.
    2.27  There is no more need to check for the correct mixture of
    2.28  tabs and spaces.
    2.29  Two simple rules ensure the integrity and flexibility of the visual
    2.30 @@ -3518,10 +3518,10 @@
    2.31  when you run a command by hand, then you want your own defaults...
    2.32  .QE
    2.33  .LP
    2.34 -The explanation neither matches the problem concered exactly
    2.35 +The explanation neither matches the problem concerned exactly
    2.36  nor is the interpretation clear.
    2.37  If the described desire addresses the technical level,
    2.38 -then it conflicts fundametally with the Unix philosophy,
    2.39 +then it conflicts fundamentally with the Unix philosophy,
    2.40  precisely because the indistinquishability of human and script
    2.41  input is the main reason for the huge software leverage in Unix.
    2.42  If, however, the described desire addresses the user's view,
     3.1 --- a/intro.roff	Sun Jul 15 23:44:15 2012 +0200
     3.2 +++ b/intro.roff	Sun Jul 15 23:58:14 2012 +0200
     3.3 @@ -128,7 +128,7 @@
     3.4  one beyond the last message.
     3.5  (In mmh, the names of these sequences are abbreviated to the
     3.6  first character.)
     3.7 -User-definded sequences can be bound to the folder containing the
     3.8 +User-defined sequences can be bound to the folder containing the
     3.9  messages (\fIpublic sequences\fP) or to the user's context
    3.10  (\fIprivate sequences\fP).
    3.11  .P
    3.12 @@ -249,7 +249,7 @@
    3.13  At that time no more than three commits were made to nmh
    3.14  since the beginning of 2011, the latest one being
    3.15  .Ci a01a41d031c796b526329a4170eb23f0ac93b949 ,
    3.16 -commited on 2011-04-13.
    3.17 +committed on 2011-04-13.
    3.18  In December, when I announced my work in progress on the
    3.19  nmh-workers mailing list,
    3.20  .[
     4.1 --- a/summary.roff	Sun Jul 15 23:44:15 2012 +0200
     4.2 +++ b/summary.roff	Sun Jul 15 23:58:14 2012 +0200
     4.3 @@ -7,8 +7,8 @@
     4.4  activating modern features per default.
     4.5  Furthermore, I have improved the style by refactoring clumpsy code
     4.6  and by identifying and forcing clear concepts.
     4.7 -All my work was motivated by Antoine de Saint Exupery's well-known
     4.8 -statement:
     4.9 +All my work was motivated by Antoine de Saint Exup\[eacute]ry's
    4.10 +well-known statement:
    4.11  .[
    4.12  antoine de saint exupery wind sand and stars
    4.13  .]
    4.14 @@ -79,7 +79,7 @@
    4.15  .P
    4.16  The features most often asked for are IMAP and Maildir support.
    4.17  But, both of them collide with MH in the same fundamental way as
    4.18 -different filesystem approaches collide with Unix.
    4.19 +different file system approaches collide with Unix.
    4.20  Nevertheless, an abstraction layer could provide a mapping between such
    4.21  storage back-ends and the MH storage format.
    4.22  Or, the mmh tool chest could be reworked to operate on a generic back-end,