X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/a0f9394df3989892854f5eab640752cb9beb4c7b..b9ba14bab3f9eb123457f98bcc090b823ab6bc85:/NEWS

diff --git a/NEWS b/NEWS
index 2a3bb7d3..3aa5c3af 100644
--- a/NEWS
+++ b/NEWS
@@ -52,7 +52,7 @@ The following are new features for the 1.6 release of nmh:
   message/rfc822 parts instead of messages formatted with RFC 934).
 - All proc entries (showproc, moreproc, etc) can now accept entries that
   contain spaces and shell metacharacters.  If found, such entries will
-  either be space-splitted or processed by /bin/sh.
+  either be space-split or processed by /bin/sh.
 - A new program, fmttest(1) is included to help debug format files.  See
   NOTABLE CHANGES below.
 - mhshow/mhstore now have support for RFC-2017 (access-type=url) for
@@ -69,7 +69,7 @@ The following are new features for the 1.6 release of nmh:
 - For the SMTP MTA TLS can now be negotiated at the beginning of the
   connection with the -initialtls switch.
 - Messages can now be selected using a relative offset from some other
-  message, or from the start or end of a sequence.  See mh-sequences(5).
+  message, or from the start or end of a sequence.  See mh-sequence(5).
 - The -changecur and -nochangecur switches have been added to mhlist(1).
 - mhbuild(1) can now encode 8-bit message headers using RFC-2047 encoding
   rules.  See NOTABLE CHANGES below.
@@ -96,7 +96,7 @@ The following are new features for the 1.6 release of nmh:
 - mh-mime(7) now provides an introduction to nmh's MIME handling.
 - mhshow(1) will now by default display all text content under one pager,
   and display markers for non-text and non-inline content.  The content
-  markers are changeable via mh-format(5).  See NOTABLE CHANGES bellow.
+  markers are changeable via mh-format(5).  See NOTABLE CHANGES below.
 
 -----------------
 OBSOLETE FEATURES
@@ -233,7 +233,7 @@ pagers for each part as was in the past.  Non-displayed parts will be
 indicated using a marker string, which can be customized by a new
 mh-format(5) string.
 
-All nmh utilites now understand RFC 2231-encoded MIME parameters and
+All nmh utilities now understand RFC 2231-encoded MIME parameters and
 will automatically convert the encoded parameters into the native
 character set, when appropriate (again, assuming nmh was built with
 iconv support).