docs/master

diff preface.roff @ 212:9317d789cef9

Various improvements and rework.
author markus schnalke <meillo@marmaro.de>
date Thu, 12 Jul 2012 22:04:51 +0200
parents c299ed65d015
children de8172bcdc5e
line diff
     1.1 --- a/preface.roff	Thu Jul 12 20:01:46 2012 +0200
     1.2 +++ b/preface.roff	Thu Jul 12 22:04:51 2012 +0200
     1.3 @@ -86,8 +86,8 @@
     1.4  I had to discover that the community was reluctant to change.
     1.5  Its wish for compatibility was much stronger than its
     1.6  wish for convenient out-of-the-box setups \(en in contrast to my opinion.
     1.7 -This, once again, led to long discussions.
     1.8 -I came to understand their point of view, but it was different to mine.
     1.9 +Once again, this led to long discussions.
    1.10 +I came to understand their point of view, but it is different from mine.
    1.11  At the end of my three-month project, I had become familiar with
    1.12  nmh's code base and community,
    1.13  I had improved the project in minor ways,
    1.14 @@ -173,7 +173,7 @@
    1.15  The reader is expected to know the format of email messages and
    1.16  the structure of email transfer systems, at least on a basic level.
    1.17  It's advisable to have cross-read RFC\|821 and RFC\|822.
    1.18 -Furthermore, basic understanding of MIME [RFC\|2045\(enRFC\|2049]
    1.19 +Furthermore, basic understanding of MIME [RFC\|2045\(en2049]
    1.20  is good to have.
    1.21  The Wikipedia provides good introduction-level information about email.
    1.22  .[
    1.23 @@ -247,23 +247,15 @@
    1.24  In this case it is a reference to the man page of
    1.25  .Pn cat ,
    1.26  which is in section one of the Unix manual.
    1.27 -Internet technologies are specified by \fIRequests for Comments\fP (RFCs).
    1.28 -Throughout the document, they are referenced similar to ``RFC\|821''.
    1.29 +\fIRequests for Comments\fP (RFCs), which describe the working
    1.30 +of the Internet, are referenced as ``RFC\|821''.
    1.31  A list of relevant RFCs is located at the end of the document.
    1.32  Literature is cited in brackets, such as
    1.33  .[ ``[
    1.34  kernighan pike unix programming env
    1.35  .]]''.
    1.36 -Citations of email messages and websites are in the same style
    1.37 -but distinguished by a prefix.
    1.38 -For example:
    1.39 -.[ ``[
    1.40 -website mmh
    1.41 -.]]''
    1.42 -and
    1.43 -.[ ``[
    1.44 -nmh-workers mmh announce
    1.45 -.]]''.
    1.46 +Citations of email messages and websites are distinguished by
    1.47 +``mail:'' and ``web:'' prefixes.
    1.48  All references are collected at the end of the document.
    1.49  .P
    1.50  This document describes practical programming work.