===================================================================
RCS file: /cvs/mandoc/Attic/manuals.7,v
retrieving revision 1.15
retrieving revision 1.20
diff -u -p -r1.15 -r1.20
--- mandoc/Attic/manuals.7	2009/06/25 10:55:40	1.15
+++ mandoc/Attic/manuals.7	2010/04/13 05:26:49	1.20
@@ -1,6 +1,6 @@
-.\"	$Id: manuals.7,v 1.15 2009/06/25 10:55:40 kristaps Exp $
+.\"	$Id: manuals.7,v 1.20 2010/04/13 05:26:49 kristaps Exp $
 .\"
-.\" Copyright (c) 2009 Kristaps Dzonsons <kristaps@kth.se>
+.\" Copyright (c) 2009 Kristaps Dzonsons <kristaps@bsd.lv>
 .\"
 .\" Permission to use, copy, modify, and distribute this software for any
 .\" purpose with or without fee is hereby granted, provided that the above
@@ -13,8 +13,8 @@
 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\" 
-.Dd $Mdocdate: June 25 2009 $
+.\"
+.Dd $Mdocdate: April 13 2010 $
 .Dt MANUALS 7
 .Os
 .\" SECTION
@@ -28,15 +28,15 @@
 .Pp
 A system component's documentation describes the utility of that
 component, whether it's a device driver, an executable or, most
-importantly, a game.  
+importantly, a game.
 .Pp
-This document serves as a tutorial to writing 
-.Ux 
+This document serves as a tutorial to writing
+.Ux
 documentation
 .Pq Dq manuals .
 .\" SECTION
-.Sh COMPOSITION
-First, copy over the manual template from 
+.Sh ENVIRONMENT
+First, copy over the manual template from
 .Pa /usr/share/misc/mdoc.template
 into your source directory.
 .Pp
@@ -66,7 +66,7 @@ file and wire protocol formats
 games
 .It 7
 tutorials, documents and papers
-.It 8 
+.It 8
 administrator utilities
 .It 9
 in-kernel routines
@@ -95,7 +95,7 @@ other manuals by that same name before committing:
 .Pp
 .Dl % apropos myname
 .Pp
-Manual files are named 
+Manual files are named
 .Pa myname.mysection ,
 such as
 .Pa manuals.7
@@ -103,62 +103,41 @@ for this document.  Rename the template file:
 .Pp
 .Dl % mv mdoc.template myname.mysection
 .\" SUBSECTION
-.Ss Input Language
-Manuals should 
-.Em always 
-be written in the
-.Xr mdoc 7
-formatting language.
-.Pp
-There exist other documentation-specific languages, such as the
-historical
-.Xr man 7
-package of 
-.Xr roff 7 ;
-newer languages such as DocBook or texinfo; or even ad-hoc conventions
-such as README files.  
-.Em Avoid these formats .
-.Pp
-There are two canonical references for writing mdoc.  Read them.
-.Pp
-.\" LIST
-.Bl -tag -width XXXXXXXXXXXXXXXX -offset indent -compact
-.It Xr mdoc 7
-formal language reference
-.It Xr mdoc.samples 7
-macro reference
-.El
-.Pp
-Open the template you've copied into
-.Pa myname.mysection
-and begin editing.
-.\" SUBSECTION
 .Ss Development Tools
 While writing, make sure that your manual is correctly structured:
 .Pp
-.Dl % mandoc \-Tlint \-Wall name.1
+.Dl % mandoc \-Tlint \-Wall \-fstrict name.1
 .Pp
+The quick-fix feature of
+.Xr vim 1
+is useful for checking over many manuals:
+.Bd -literal -offset indent
+% mandoc \-Wall \-fstrict \-Tlint \-fign-errors \e
+  ./path/to/manuals/* 2>&1 > /tmp/mandoc.errs
+% vim -q /tmp/mandoc.errs
+.Ed
+.Pp
 You may spell-check your work as follows:
 .Pp
 .Dl % deroff name.1 | spell
 .Pp
-If 
+If
 .Xr ispell 1
 is installed, it has a special mode for manuals:
 .Pp
 .Dl % ispell \-n name.1
 .Pp
-Use 
+Use
 .Xr cvs 1
 or
 .Xr rcs 1
 to version-control your work.  If you wish the last check-in to effect
 your document's date, use the following RCS tag for the date macro:
 .Pp
-.Dl \&.Dd $Mdocdate: June 25 2009 $
+.Dl \&.Dd $Mdocdate: April 13 2010 $
 .\" SUBSECTION
 .Ss Viewing
-mdoc documents may be paged to your terminal with 
+mdoc documents may be paged to your terminal with
 .Xr mandoc 1 .
 If you plan on distributing your work to systems without this tool,
 check it against
@@ -169,7 +148,7 @@ check it against
 .Ed
 .\" SUBSECTION
 .Ss Automation
-Consider adding your mdoc documents to 
+Consider adding your mdoc documents to
 .Xr make 1
 Makefiles in order to automatically check your input:
 .Bd -literal -offset indent
@@ -184,18 +163,20 @@ Makefiles in order to automatically check your input:
 Your manual must have a license.  It should be listed at the start of
 your document, just as in source code.
 .\" SECTION
-.Sh BEST PRACTICES
-The
+.Sh COMPOSITION
+Manuals should
+.Em always
+be written in the
 .Xr mdoc 7
-and 
-.Xr mdoc.samples 7
-files are indispensable in guiding composition.  In this section, we
-introduce some 
-.Ux
-manual best practises:
+formatting language.
+.\" PARAGRAPH
+.Pp
+Open the template you've copied into
+.Pa myname.mysection
+and begin editing.
 .\" SUBSECTION
 .Ss Language
-.Bl -enum 
+.Bl -enum
 .It
 Use clear, concise language.  Favour simplicity.
 .It
@@ -215,15 +196,15 @@ symbols and so on), use the escapes dictated in
 .Ss Style
 The structure of the mdoc language makes it very hard to have any
 particular format style.  Keep your lines under 72 characters in length.
-If you must have long option lines, use 
+If you must have long option lines, use
 .Sq \&Oo/Oc .
 The same goes for function prototypes.
 .Em \&Do not
-use 
+use
 .Sq \&Xo/Xc .
 Find another way to structure your line.
 .\" SUBSECTION
-.Ss References 
+.Ss References
 Other components may be referenced with the
 .Sq \&Xr
 and