Refer to just "root" in slocal man page.

[mmh] / man / slocal.man

diff --git a/man/slocal.man b/man/slocal.man
index e6d0dd8..d0b24e4 100644 (file)
--- a/man/slocal.man
+++ b/man/slocal.man
@@ -1,4 +1,4 @@
-.TH SLOCAL %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
+.TH SLOCAL %manext1% "November 9, 2012" "%nmhversion%"
 .\"
 .\" %nmhwarning%
 .\"
@@ -117,7 +117,6 @@ allow you to see the decisions and actions that
 is taking, as well as check for syntax errors in your
 .RI \*(lq \&.maildelivery \*(rq
 file.
-
 .SS "Message Transfer Agents"
 Most modern MTAs including
 .BR sendmail ,
@@ -134,7 +133,6 @@ in your \&.forward file in your home directory.  This will cause
 your MTA to invoke
 .B slocal
 on your behalf when a message arrives.
-
 .SS "The Maildelivery File"
 The
 .RI \*(lq \&.maildelivery \*(rq
@@ -276,7 +274,6 @@ message is considered delivered.
 The delivery file is always read completely, so that several matches
 can be made and several actions can be taken.
 .RE
-
 .SS "Security of Delivery Files"
 In order to prevent security problems, the
 .RI \*(lq \&.maildelivery \*(rq
@@ -292,12 +289,11 @@ perform an action which delivers the message, then
 will check for a global delivery file at
 .IR %etcdir%/maildelivery .
 This file is read according to the same rules.  This file must be
-owned by the root and must be writable only by the root.
+owned by root and must be writable only by root.
 .PP
 If a global delivery file cannot be found or does not perform an
 action which delivers the message, then standard delivery to the
 user's maildrop is performed.
-
 .SS "Example Delivery File"
 To summarize, here's an example delivery file:
 .PP
@@ -334,7 +330,6 @@ default   \-        file    ?       mailbox
 # always run rcvtty
 *         \-        pipe    R       %libdir%/rcvtty
 .fi
-
 .SS "Sub-process environment"
 When a process is invoked, its environment is: the user/group-ids are
 set to recipient's ids; the working directory is the recipient's home
@@ -360,14 +355,13 @@ failed.
 .PP
 In order to avoid any time limitations, you might implement a process
 that began by
-.BR fork ()-ing.
+.IR fork ()-ing.
 The parent would return the appropriate
 value immediately, and the child could continue on, doing whatever it
 wanted for as long as it wanted.  This approach is somewhat risky if
 the parent is going to return an exit status of zero.  If the parent is
 going to return a non-zero exit status, then this approach can lead to
 quicker delivery into your maildrop.
-
 .SH FILES
 .fc ^ ~
 .nf
@@ -377,10 +371,12 @@ quicker delivery into your maildrop.
 ^%etcdir%/maildelivery~^Rather than the standard file
 ^%mailspool%/$USER~^The default maildrop
 .fi
-
 .SH "SEE ALSO"
-rcvdist(1), rcvpack(1), rcvstore(1), rcvtty(1), mh\-format(5)
-
+.IR rcvdist (1),
+.IR rcvpack (1),
+.IR rcvstore (1),
+.IR rcvtty (1),
+.IR mh\-format (5)
 .SH DEFAULTS
 .nf
 .RB ` \-noverbose '
@@ -390,10 +386,8 @@ rcvdist(1), rcvpack(1), rcvstore(1), rcvtty(1), mh\-format(5)
 .RB ` \-file "' defaults to stdin"
 .RB ` \-user "' defaults to the current user"
 .fi
-
 .SH CONTEXT
 None
-
 .SH HISTORY
 .B Slocal
 was originally designed to be backward-compatible with
@@ -422,7 +416,6 @@ value
 .B RP_MECH
 (200), which means
 \*(lquse an alternate route\*(rq (deliver the message to the maildrop).
-
 .SH BUGS
 Only two return codes are meaningful, others should be.
 .PP