docs/master

changeset 124:3d30fd938aa9

Spellchecking.
author markus schnalke <meillo@marmaro.de>
date Sat, 30 Jun 2012 15:05:06 +0200
parents 740f4128dea7
children 0e102cec0c73
files discussion.roff
diffstat 1 files changed, 7 insertions(+), 7 deletions(-) [+]
line diff
     1.1 --- a/discussion.roff	Sat Jun 30 15:00:04 2012 +0200
     1.2 +++ b/discussion.roff	Sat Jun 30 15:05:06 2012 +0200
     1.3 @@ -2684,7 +2684,7 @@
     1.4  worked on the current message instead on message number 42,
     1.5  and
     1.6  .Cl "anno -list -number l:5
     1.7 -did not work on the last five messages but failed with the misterious
     1.8 +did not work on the last five messages but failed with the mysterious
     1.9  error message: ``anno: missing argument to -list''.
    1.10  Yet, the invocation matched the specification in the man page.
    1.11  There, the correct use of
    1.12 @@ -2999,7 +2999,7 @@
    1.13  .P
    1.14  Splitting the source code of a large program into multiple files can
    1.15  increase the readability of its source code.
    1.16 -Most of the mmh tools, however, are simple and staight-forward programs.
    1.17 +Most of the mmh tools, however, are simple and straight-forward programs.
    1.18  With the exception of the MIME handling tools,
    1.19  .Pn pick
    1.20  is the largest tools.
    1.21 @@ -3017,7 +3017,7 @@
    1.22  when parts of the code are reused in other programs,
    1.23  and the reused code fragment is not general enough
    1.24  for including it in the MH library,
    1.25 -or, if the code has depencencies on a library that only few programs need.
    1.26 +or, if the code has dependencies on a library that only few programs need.
    1.27  .Fn uip/packsbr.c ,
    1.28  for instance, provides the core program logic for the
    1.29  .Pn packf
    1.30 @@ -3131,7 +3131,7 @@
    1.31  .BU
    1.32  The influenced code area is small
    1.33  .BU
    1.34 -The boundaries are stictly defined
    1.35 +The boundaries are strictly defined
    1.36  .BU
    1.37  The code is written straight-forward
    1.38  .P
    1.39 @@ -3218,8 +3218,8 @@
    1.40  and
    1.41  .Fu exec()
    1.42  are expensive, the quicker response might be noticable.
    1.43 -In the old times, sacrifying readability and conceptional beauty for speed
    1.44 -might even have been a must to prevent MH from being unusably slow.
    1.45 +In the old times, sacrificing readability and conceptional beauty for
    1.46 +speed might even have been a must to prevent MH from being unusably slow.
    1.47  Whatever the reasons had been, today they are gone.
    1.48  No longer should we sacrifice readability or conceptional beauty.
    1.49  No longer should we violate the Unix philosophy's ``one tool, one job''
    1.50 @@ -3252,7 +3252,7 @@
    1.51  By changing the command line interfaces of tools, it is
    1.52  the developer's job to adjust the invocations of these tools as well.
    1.53  As this is a manual task and regression tests, which could detect such
    1.54 -problems, are not availabe yet, it is prone to errors.
    1.55 +problems, are not available yet, it is prone to errors.
    1.56  These errors will not be detected at compile time but at run time.
    1.57  Installing regression tests is a task left to do.
    1.58  In the best case, a uniform way of invoking tools from other tools