Rather than standard message skeleton
with
User message skeleton
My thinking here is that a) we can do away with the kinda weird
'Rather than', b) I find the distinction between 'default' and
'standard' to be vague and c) it only appears in a few pages
and is easily remedied. It turns up in comp(1) as "An alternative
to the standard skeleton.", where 'standard' is used in the same
way as 'default' is used in rcvdist(1), so I think it's worth
settling on something 'better' and applying it consistently.
My proposal is 'Default foo', for the foo in %nmhetcdir% and
'User foo' for the foo in the user's <mh-dir>.
-.TH RCVDIST %manext1% "January 18, 2001" "%nmhversion%"
+.TH RCVDIST %manext1% "December 31, 2016" "%nmhversion%"
\&...
.ad
.SH DESCRIPTION
\&...
.ad
.SH DESCRIPTION
-program will accept a message on its standard input
-and resend a copy of this message to all of the addresses listed on its
-command line.
+accepts a message on its standard input and resends a copy of
+the message to all of the addresses listed on its command line.
-When a message is redistributed with the
-.B rcvdist
-command, the
-format of the Resent-xxx header fields is controlled by the forms files
+The format of the Resent-xxx header fields is specified by the form file
.RI \*(lq rcvdistcomps \*(rq.
If a file named
.RI \*(lq rcvdistcomps \*(rq
.RI \*(lq rcvdistcomps \*(rq.
If a file named
.RI \*(lq rcvdistcomps \*(rq
-exists in the user's nmh
-directory, it will be used instead of the default one. You may specify
-an alternate forms file with the switch
+exists in the user's nmh directory, it will be used instead of the
+default file.
+You may specify an alternate forms file with
.B \-form
.IR formfile .
.PP
.B \-form
.IR formfile .
.PP
.IR mh\-format (5).
In addition to the standard format escapes,
.B rcvdist
.IR mh\-format (5).
In addition to the standard format escapes,
.B rcvdist
-also recognizes the following additional
+also recognizes the following
.PP
By default,
.B rcvdist
.PP
By default,
.B rcvdist
-to do the actual
-delivery of the message, although this can be changed by defining the
+program to deliver the message, although this can be changed by
+defining the
.I postproc
profile component.
.SH FILES
.I postproc
profile component.
.SH FILES
.nf
.ta \w'%nmhetcdir%/ExtraBigFileName 'u
^%nmhetcdir%/rcvdistcomps~^Default message skeleton
.nf
.ta \w'%nmhetcdir%/ExtraBigFileName 'u
^%nmhetcdir%/rcvdistcomps~^Default message skeleton
-^or <mh\-dir>/rcvdistcomps~^Rather than standard message skeleton
+^or <mh\-dir>/rcvdistcomps~^User's message skeleton
^%nmhetcdir%/mts.conf~^nmh mts configuration file
^%nmhetcdir%/mts.conf~^nmh mts configuration file
-^$HOME/\&.maildelivery~^The file controlling local delivery
-^%nmhetcdir%/maildelivery~^Rather than the standard file
+^%nmhetcdir%/maildelivery~^Default delivery file
+^$HOME/\&.maildelivery~^User's delivery file
.fi
.SH "SEE ALSO"
.IR rcvpack (1),
.IR rcvstore (1),
.fi
.SH "SEE ALSO"
.IR rcvpack (1),
.IR rcvstore (1),
.IR slocal (1),
.IR mh\-format (5)
.IR slocal (1),
.IR mh\-format (5)