Improve these comments a bit.

[nmh] / man / mhbuild.man

diff --git a/man/mhbuild.man b/man/mhbuild.man
index 7667b3a353b7a3ba0b3019ab7ab3d207350ae18e..b95c79482c3df93441c004b5165c9c656551c7de 100644 (file)
--- a/man/mhbuild.man
+++ b/man/mhbuild.man
@@ -765,17 +765,19 @@ switch will indicate which algorithm to use when encoding any message headers
 that contain 8\-bit characters.
 The valid arguments are
 .I base64
 that contain 8\-bit characters.
 The valid arguments are
 .I base64

-for based\-64 encoding,
+for base\-64 encoding,

 .I quoted
 for quoted\-printable encoding, and
 .I quoted
 for quoted\-printable encoding, and

-.I utf-8
-which requires that all 8-bit header field bodies be encoded as UTF-8
-(RFC 6530) and that the SMTP server support SMTPUTF8 (RFC 6531).
+.I utf\-8
+which requires that all 8\-bit header field bodies be encoded as UTF\-8
+(RFC 6530) and that the message be sent to a SMTP server that supports
+SMTPUTF8 (RFC 6531).

 The
 .B \-autoheaderencoding
 The
 .B \-autoheaderencoding

-switch will instruct
+switch instructs

 .B mhbuild
 .B mhbuild

-to automatically pick the algorithm that results in a shorter encoded string.
+to automatically pick the encoding, either base64 or quoted\-printable,
+that results in a shorter encoded string.

 .PP
 Putting this all together,
 here is an example of a more complicated message draft.
 .PP
 Putting this all together,
 here is an example of a more complicated message draft.


@@ -829,7 +831,7 @@ the
 switch, then
 .B mhbuild
 will encode each content with
 switch, then
 .B mhbuild
 will encode each content with

-a transfer encoding, even it the content contains only 7\-bit data.
+a transfer encoding, even if the content contains only 7\-bit data.

 This
 is to increase the likelihood that the content is not changed while in
 transport.
 This
 is to increase the likelihood that the content is not changed while in
 transport.