diff --git a/ChangeLog b/ChangeLog
index b42e290b1325b890d55e1cd196425d346a456139..5ac54172564d565cd3ea974620f28602c5bc0309 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -89,8 +89,8 @@ CVS code -
 	- Fix the description for the whitespace option to mention that
 	  only single-column characters are allowed. (DLR)
 - nano.1, nano.texi:
-	- Mention the -? alias for -h/--help, and synchronize the
-	  description and placement of the +LINE option. (DLR)
+	- Mention the -? alias for -h/--help, and add various
+	  consistency fixes. (DLR)
 - nanorc.5:
 	- Fix the description for the whitespace option to mention that
 	  only single-column characters are allowed. (DLR)
diff --git a/doc/texinfo/nano.texi b/doc/texinfo/nano.texi
index cc311496f2f2b8b2aa7ab3d8deee63afe21bf2b8..190080b8c0c9a68475fbf614346deecbeb11965e 100644
--- a/doc/texinfo/nano.texi
+++ b/doc/texinfo/nano.texi
@@ -94,7 +94,7 @@ internationalization support, and filename tab completion.
 @code{nano} +LINE [GNU long option] [option] [ @var{file ...} ]
 
 The original goal for @code{nano} was a complete bug-for-bug compatible
-emulation of Pico, but nano's main goal is to be as compatible as
+emulation of Pico, but @code{nano}'s main goal is to be as compatible as
 possible while offering a superset of Pico's functionality.  Also see
 @xref{Pico Compatibility}, for other differences.
 
@@ -448,7 +448,8 @@ Building @code{nano} from source is fairly straightforward if you are
 familiar with compiling programs with autoconf support:
 
 @itemize @bullet
-@item tar xvfz nano-x.y.z.tar.gz (where x.y.z is the version of nano)
+@item tar xvfz nano-x.y.z.tar.gz (where x.y.z is the version of
+@code{nano})
 @item cd nano-x.y.z/
 @item ./configure
 @item make
@@ -501,9 +502,8 @@ Disables Native Language support.  This will make the available GNU
 @code{nano} translations unusable.
 
 @item --with-slang
-Compiling GNU @code{nano} with Slang is supported, and will make the
-binary notably smaller than if compiled with ncurses or other curses
-libraries.
+Compiling @code{nano} with Slang is supported, and will make the binary
+notably smaller than if compiled with ncurses or other curses libraries.
 
 @end table