From 6a84684571b5d4b1ba6765ff52139f5ab625589c Mon Sep 17 00:00:00 2001
From: David Lawrence Ramsey <pooka109@gmail.com>
Date: Sun, 27 Mar 2005 04:30:33 +0000
Subject: [PATCH] add more documentation fixes for consistency
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2438 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
---
ChangeLog | 4 ++--
doc/texinfo/nano.texi | 10 +++++-----
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index b42e290b..5ac54172 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 cc311496..190080b8 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
--
GitLab