X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/d1cb667bddf8d1c5c0721fc7ab642c22946baf1f..a6af8ec9d9c78f7a74b93814fb6031f98496ed50:/man/mh-mail.man

diff --git a/man/mh-mail.man b/man/mh-mail.man
index c6ebffa4..e4d5fa54 100644
--- a/man/mh-mail.man
+++ b/man/mh-mail.man
@@ -4,10 +4,6 @@
 .\"
 .SH NAME
 mh-mail \- message format for nmh message system
-.SH SYNOPSIS
-any
-.B nmh
-command
 .SH DESCRIPTION
 .B nmh
 processes messages in a particular format.  It should be noted
@@ -32,14 +28,14 @@ Messages are expected to consist of lines of text.  Graphics and binary
 data are not handled.  No data compression is accepted.  All text is
 clear ASCII 7-bit data.
 .PP
-The general \*(lqmemo\*(rq framework of RFC\-822 is used.  A message
+The general \*(lqmemo\*(rq framework of RFC 822 is used.  A message
 consists of a block of information in a rigid format, followed by
 general text with no specified format.  The rigidly formatted first
 part of a message is called the header, and the free-format portion is
 called the body.  The header must always exist, but the body is optional.
 These parts are separated by an empty line, i.e., two consecutive newline
 characters.  Within
-.B nmh ,
+.BR nmh ,
 the header and body may be separated by a line consisting of dashes:
 .PP
 .RS 5
@@ -60,7 +56,7 @@ are indicated by leading spaces or tabs.
 Each header item is called a component and is composed of a keyword or
 name, along with associated text.  The keyword begins at the left margin,
 may NOT contain spaces or tabs, may not exceed 63 characters (as specified
-by RFC\-822), and is terminated by a colon (`:').  Certain components
+by RFC 822), and is terminated by a colon (`:').  Certain components
 (as identified by their keywords) must follow rigidly defined formats
 in their text portions.
 .PP
@@ -295,6 +291,6 @@ option.
 .SH "SEE ALSO"
 .I
 Standard for the Format of ARPA Internet Text Messages
-(RFC\-822)
+(RFC 822)
 .SH CONTEXT
 None