Remove spurious return statements after exit().

[nmh] / man / mhbuild.man

diff --git a/man/mhbuild.man b/man/mhbuild.man
index 6510b12b545dcbdfa7a3680d856325737a9b37fc..ab757d3465dfff12089a562958e523aff01d202e 100644 (file)
--- a/man/mhbuild.man
+++ b/man/mhbuild.man
@@ -27,12 +27,12 @@ command will translate a MIME composition draft into
 a valid MIME message.
 .PP
 .B mhbuild
 a valid MIME message.
 .PP
 .B mhbuild

-creates multi-media messages as specified in RFC\-2045
-to RFC\-2049.  Currently
+creates multi-media messages as specified in RFC 2045
+to RFC 2049.  Currently

 .B mhbuild
 only supports encodings in
 message bodies, and does not support the encoding of message headers as
 .B mhbuild
 only supports encodings in
 message bodies, and does not support the encoding of message headers as

-specified in RFC\-2047.
+specified in RFC 2047.

 .PP
 If you specify the name of the composition file as \*(lq-\*(rq,
 then
 .PP
 If you specify the name of the composition file as \*(lq-\*(rq,
 then


@@ -281,7 +281,7 @@ would be as follows:
 .fi
 .RE
 .PP
 .fi
 .RE
 .PP

-Any long URLs will be wrapped according to RFC\-2017 rules.
+Any long URLs will be wrapped according to RFC 2017 rules.

 .PP
 The \*(lqmessage\*(rq directive (#forw) is used to specify a message or
 group of messages to include.  You may optionally specify the name of
 .PP
 The \*(lqmessage\*(rq directive (#forw) is used to specify a message or
 group of messages to include.  You may optionally specify the name of


@@ -291,7 +291,7 @@ given, it defaults to the current message.  Hence, the message directive
 is similar to the
 .B forw
 command, except that the former uses
 is similar to the
 .B forw
 command, except that the former uses

-the MIME rules for encapsulation rather than those specified in RFC\-934.
+the MIME rules for encapsulation rather than those specified in RFC 934.

 For example,
 .PP
 .RS 5
 For example,
 .PP
 .RS 5


@@ -314,8 +314,8 @@ switch.  This switch will indicate that
 .B mhbuild
 should attempt to utilize the MIME encapsulation rules
 in such a way that the \*(lqmultipart/digest\*(rq that is created
 .B mhbuild
 should attempt to utilize the MIME encapsulation rules
 in such a way that the \*(lqmultipart/digest\*(rq that is created

-is (mostly) compatible with the encapsulation specified in RFC\-934.
-If given, then RFC\-934 compliant user-agents should be able to burst the
+is (mostly) compatible with the encapsulation specified in RFC 934.
+If given, then RFC 934 compliant user-agents should be able to burst the

 message on reception\0--\0providing that the messages being encapsulated
 do not contain encapsulated messages themselves.  The drawback of this
 approach is that the encapsulations are generated by placing an extra
 message on reception\0--\0providing that the messages being encapsulated
 do not contain encapsulated messages themselves.  The drawback of this
 approach is that the encapsulations are generated by placing an extra


@@ -685,27 +685,27 @@ is checked.
 .IR mhstore (1)
 .PP
 .I "Proposed Standard for Message Encapsulation"
 .IR mhstore (1)
 .PP
 .I "Proposed Standard for Message Encapsulation"

-(RFC\-934),
+(RFC 934),

 .PP
 .I "The Content-MD5 Header Field"
 .PP
 .I "The Content-MD5 Header Field"

-(RFC\-1864),
+(RFC 1864),

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"

-(RFC\-2045),
+(RFC 2045),

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"

-(RFC\-2046),
+(RFC 2046),

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text"

-(RFC\-2047),
+(RFC 2047),

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"

-(RFC\-2048),
+(RFC 2048),

 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples"
 .PP
 .I "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples"

-(RFC\-2049)
+(RFC 2049)

 .I "Definition of the URL MIME External-Body Access-Type"
 .I "Definition of the URL MIME External-Body Access-Type"

-(RRC\-2017)
+(RFC 2017)

 .SH DEFAULTS
 .nf
 .RB ` \-headers '
 .SH DEFAULTS
 .nf
 .RB ` \-headers '