fixed upper case / lower case mistakes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1891 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

appendixa/autoconf-desc.xml

@@ -7,20 +7,20 @@ ifnames</para></sect3>
 <sect3><title>Descriptions</title>
 
 <sect4><title>autoconf</title>
-<para>Autoconf is a tool for producing shell scripts that automatically
+<para>autoconf is a tool for producing shell scripts that automatically
 configure software source code packages to adapt to many kinds of
-UNIX-like systems.  The configuration scripts produced by Autoconf are
-independent of Autoconf when they are run, so their users do not need to
-have Autoconf.</para></sect4>
+UNIX-like systems.  The configuration scripts produced by autoconf are
+independent of autoconf when they are run, so their users do not need to
+have autoconf.</para></sect4>
 
 <sect4><title>autoheader</title>
 <para>The autoheader program can create a template file of C #define
 statements for configure to use</para></sect4>
 
 <sect4><title>autoreconf</title>
-<para>If there are a lot of Autoconf-generated configure scripts, the
+<para>If there are a lot of autoconf-generated configure scripts, the
 autoreconf program can save some work.  It runs autoconf (and
-autoheader, where appropriate) repeatedly to remake the Autoconf
+autoheader, where appropriate) repeatedly to remake the autoconf
 configure scripts and configuration header templates in the directory
 tree rooted at the current directory.</para></sect4>
 
@@ -34,7 +34,7 @@ is a preliminary configure.in for that package.</para></sect4>
 
 <sect4><title>autoupdate</title>
 <para>The autoupdate program updates a configure.in file that calls
-Autoconf macros by their old names to use the current 
+autoconf macros by their old names to use the current
 macro names.</para></sect4>
 
 <sect4><title>ifnames</title>

appendixa/automake-desc.xml

@@ -6,14 +6,14 @@
 <sect3><title>Descriptions</title>
 
 <sect4><title>aclocal</title>
-<para>Automake includes a number of Autoconf macros which can be used in
-packages; some of them are actually required by Automake in certain
+<para>automake includes a number of autoconf macros which can be used in
+packages; some of them are actually required by automake in certain
 situations. These macros must be defined in the aclocal.m4-file;
 otherwise they will not be seen by autoconf.</para>
 
 <para>The aclocal program will automatically generate aclocal.m4 files
 based on the contents of configure.in.  This provides a convenient
-way to get Automake-provided macros, without having to search around.
+way to get automake-provided macros, without having to search around.
 Also, the aclocal mechanism is extensible for use 
 by other packages.</para></sect4>
 

appendixa/bash-desc.xml

@@ -6,8 +6,8 @@
 <sect3><title>Descriptions</title>
 
 <sect4><title>bash</title>
-<para>Bash is the Bourne-Again SHell, which is a widely used command
-interpreter on Unix systems. Bash is a program that reads from standard
+<para>bash is the Bourne-Again SHell, which is a widely used command
+interpreter on Unix systems. The bash program reads from standard
 input, the keyboard. A user types something and the program will evaluate
 what he has typed and do something with it, like running a
 program.</para></sect4>

appendixa/binutils-desc.xml

@@ -34,7 +34,7 @@ user-level names so that the linker can keep these overloaded functions
 from clashing.</para></sect4>
 
 <sect4><title>gasp</title>
-<para>Gasp is the Assembler Macro Preprocessor.</para></sect4>
+<para>gasp is the Assembler Macro Preprocessor.</para></sect4>
 
 <sect4><title>gprof</title>
 <para>gprof displays call graph profile data.</para></sect4>

appendixa/bison-desc.xml

@@ -8,8 +8,8 @@
 
 <sect4><title>bison</title>
 
-<para>Bison is a parser generator, a replacement for YACC. YACC stands for Yet
-Another Compiler Compiler. What is Bison then? It is a program that
+<para>bison is a parser generator, a replacement for yacc. yacc stands for Yet
+Another Compiler Compiler. What is bison then? It is a program that
 generates a program that analyzes the structure of a text file. Instead of
 writing the actual program a user specifies how things should be connected
 and with those rules a program is constructed that analyzes the 
@@ -22,8 +22,7 @@ one of them is the calculator.</para>
 
 <para>A human can easily come to the result 7. Why? Because of the structure. 
 Our brain knows
-how to interpret the string. The computer doesn't know that and Bison
-is a
+how to interpret the string. The computer doesn't know that and bison is a
 tool to help it understand by presenting the string in the following way
 to the compiler:</para>
 
@@ -41,7 +40,7 @@ number 1 which are joined by the add symbol. Adding 1 to the previous
 result makes 7. In calculating the most complex calculations can be
 broken down in this tree format and the computer just starts at the
 bottom and works its way up to the top and comes with the correct
-answer. Of course, Bison isn't only used for calculators
+answer. Of course, bison isn't only used for calculators
 alone.</para></sect4>
 
 <sect4><title>yacc</title>

appendixa/bzip2-desc.xml

@@ -7,7 +7,7 @@ bzip2recover</para></sect3>
 <sect3><title>Descriptions</title>
 
 <sect4><title>bunzip2</title>
-<para>Bunzip2 decompresses files that are compressed with
+<para>bunzip2 decompresses files that are compressed with
 bzip2.</para></sect4>
 
 <sect4><title>bzcat</title>

appendixa/ed-desc.xml

@@ -6,7 +6,7 @@
 <sect3><title>Description</title>
 
 <sect4><title>ed</title>
-<para>Ed is a line-oriented text editor.  It is used to create, display,
+<para>ed is a line-oriented text editor.  It is used to create, display,
 modify and otherwise manipulate text files.</para></sect4>
 
 <sect4><title>red</title>

appendixa/file-desc.xml

@@ -6,7 +6,7 @@
 <sect3><title>Descriptions</title>
 
 <sect4><title>file</title>
-<para>File tests each specified file in an attempt to classify it. There are 
+<para>file tests each specified file in an attempt to classify it. There are
 three sets  of  tests,  performed in this order: filesystem tests, 
 magic number tests, and language tests. The first test that succeeds 
 causes the file type to be printed.</para></sect4>

appendixa/findutils-desc.xml

@@ -21,12 +21,12 @@ a certain criteria. If no criteria is given, it lists all files in the
 current directory and its subdirectories.</para></sect4>
 
 <sect4><title>frcode</title>
-<para>updatedb runs a program called frcode to compress the list of file names
+<para>frcode is called by updatedb to compress the list of file names
 using front-compression, which reduces the database size by a factor of
 4 to 5.</para></sect4>
 
 <sect4><title>locate</title>
-<para>Locate scans a database which contain all files and directories on a
+<para>locate scans a database which contain all files and directories on a
 filesystem. This program lists the files and directories in this
 database matching a certain criteria. If a user is looking for a file this
 program will scan the database and tell him exactly where the files he

appendixa/gcc-desc.xml

@@ -35,15 +35,15 @@ preprocessor does.</para></sect4>
 code through optimization.</para></sect4>
 
 <sect4><title>protoize</title>
-<para>Optional additional program which converts old-style pre-ANSI
-functions or definitions to new-style ANSI C prototypes. (default file
+<para>protoize converts old-style pre-ANSI
+functions or definitions to new-style ANSI C prototypes (the default file
 for looking known ones up is
-<filename>/usr/lib/gcc-lib/&lt;arch&gt;/&lt;version&gt;/SYSCALLS.c.X</filename>)</para></sect4>
+<filename>/usr/lib/gcc-lib/&lt;arch&gt;/&lt;version&gt;/SYSCALLS.c.X</filename>).</para></sect4>
 
 <sect4><title>unprotoize</title>
-<para>Optional additional program which converts prototypes made by
-protoize back to original old-style pre-ANSI (correct job only when
-converted before with protoize)</para></sect4>
+<para>unprotoize converts prototypes
+back to the original old-style pre-ANSI functions, doing a correct
+job only when they were converted with protoize.</para></sect4>
 
 </sect3>
 

appendixa/glibc-desc.xml

@@ -137,20 +137,20 @@ segfaults.</para></sect4>
 programs in Linux.</para></sect4>
 
 <sect4><title>libc, libc_nonshared, libc_p</title>
-<para>These files constitute the main C library.  The C Library is a
+<para>These files constitute the main C library.  The C library is a
 collection of commonly used functions in programs.
 This way a programmer doesn't need to create his own functions for every
 single task. The most common things like writing a string to the screen
 are already present and at the disposal of the programmer.</para>
 
-<para>The C library (actually almost every library) come in two flavors:
-dynamic ones and static ones. In short when a program uses a static C
-library, the code from the C library will be copied into the executable
-file. When a program uses a dynamic library, that executable will not
+<para>The C library (actually almost every library) comes in two flavors:
+a dynamic and a static one. In short, when a program uses a static C
+library, the code from the C library is copied into the executable file.
+When a program uses a dynamic library, the executable will not
 contain the code from the C library, but  instead a routine that loads
 the functions from the library at the time the program is run. This
 means a significant decrease in the file size of a program. The
-documentation that comes with the C Library describes this in more
+documentation that comes with the C library describes this in more
 detail, as it is too complicated to explain here in one or two
 lines.</para></sect4>
 

appendixa/libtool-desc.xml

@@ -6,7 +6,7 @@
 <sect3><title>Descriptions</title>
 
 <sect4><title>libtool</title>
-<para>Libtool provides generalized library-building 
+<para>libtool provides generalized library-building
 support services.</para></sect4>
 
 <sect4><title>libtoolize</title>
@@ -21,8 +21,8 @@ package.</para></sect4>
 <sect3><title>Descriptions</title>
 
 <sect4><title>libltdl</title>
-<para>Libtool provides a small library, called `libltdl', that aims at hiding 
-the various difficulties of dlopening libraries from programmers.</para></sect4>
+<para>libltdl is a small library that aims at hiding from programmers
+the various difficulties of dlopening libraries.</para></sect4>
 
 </sect3>
 

appendixa/m4-desc.xml

@@ -6,11 +6,11 @@
 <sect3><title>Descriptions</title>
 
 <sect4><title>m4</title>
-<para>M4 is a macro processor. It copies input to output expanding macros as it 
+<para>m4 is a macro processor. It copies input to output expanding macros as it
 goes. Macros are either built-in or user-defined and can take any number
 of arguments. Besides just doing macro expansion m4 has built-in functions 
 for including named files, running UNIX commands, doing integer arithmetic, 
-manipulating text in various ways, recursion, etc. M4 can be used either 
+manipulating text in various ways, recursion, etc. The m4 program can be used either
 as a front-end to a compiler or as a macro processor in its own
 right.</para></sect4>
 

appendixa/modutils-desc.xml

@@ -40,7 +40,7 @@ running kernel.</para></sect4>
 displays any  information that it can glean.</para></sect4>
 
 <sect4><title>modprobe</title>
-<para>Modprobe uses a Makefile-like dependency file, created by depmod, 
+<para>modprobe uses a Makefile-like dependency file, created by depmod,
 to automatically load the relevant module(s) from the set of modules 
 available in predefined directory trees.</para></sect4>
 

appendixa/ncurses-desc.xml

@@ -64,10 +64,9 @@ libncurses.[a,so], libncurses_g.a, libpanel.[a,so] and
 libpanel_g.a</para>
 
 <sect4><title>libcurses, libncurses++, libncurses, libncurses_g</title>
-<para>The libraries that make up the Ncurses library are used to display
+<para>These libraries are the base of the system and are used to display
 text (often in a fancy way) on the screen. An example where ncurses is used
-is in the kernel's <quote>make menuconfig</quote> process.  The
-libncurses libraries are the base of the system.</para></sect4>
+is in the kernel's <quote>make menuconfig</quote> process.</para></sect4>
 
 <sect4><title>libform, libform_g</title>
 <para>libform is used to implement forms in ncurses.</para></sect4>

appendixa/psmisc-desc.xml

@@ -17,7 +17,7 @@ systems.</para></sect4>
 commands.</para></sect4>
 
 <sect4><title>pidof</title>
-<para>Pidof finds the process id's (pids) of the named programs and
+<para>pidof finds the process id's (pids) of the named programs and
 prints those id's on standard output.</para></sect4>
 
 <sect4><title>pstree</title>

appendixa/shadowpwd-desc.xml

@@ -30,7 +30,7 @@ existing users.</para></sect4>
 user login shells.</para></sect4>
 
 <sect4><title>expiry</title>
-<para>Checks and enforces password expiration policy.</para></sect4>
+<para>expiry checks and enforces a password expiration policy.</para></sect4>
 
 <sect4><title>faillog</title>
 <para>faillog formats the contents of the failure log,/var/log/faillog, and 
@@ -107,9 +107,9 @@ files.</para></sect4>
 <para>sg executes command as a different group ID.</para></sect4>
 
 <sect4><title>su</title>
-<para>Change the effective user id and group id to that of a user. This
-replaces the su programs that's installed from the 
-Shellutils package.</para></sect4>
+<para>su changes the effective user id and group id to that of a given user.
+This replaces the su programs that's installed from the
+Sh-utils package.</para></sect4>
 
 <sect4><title>useradd</title>
 <para>useradd creates a new user or update default new user 

appendixa/shellutils-desc.xml

@@ -101,7 +101,7 @@ files.</para></sect4>
 <para>test checks file types and compares values.</para></sect4>
 
 <sect4><title>true</title>
-<para>True always exits with a status code indicating success.</para></sect4>
+<para>true always exits with a status code indicating success.</para></sect4>
 
 <sect4><title>tty</title>
 <para>tty prints the file name of the terminal connected to standard 

appendixa/sysklogd-desc.xml

@@ -10,7 +10,7 @@
 messages.</para></sect4>
 
 <sect4><title>syslogd</title>
-<para>Syslogd provides a kind of logging that many modern programs use. Every 
+<para>syslogd provides the kind of logging that many modern programs use. Every
 logged message contains at least a time and a hostname field, normally a 
 program name field, too, but that depends on how trusty the logging 
 program is.</para></sect4>

appendixa/sysvinit-desc.xml

@@ -37,7 +37,7 @@ since that file was created.</para></sect4>
 file /var/log/btmp, which contains all the bad login attempts.</para></sect4>
 
 <sect4><title>mesg</title>
-<para>Mesg controls the access to the users terminal by others. It's typically 
+<para>mesg controls the access to the user's terminal by others. It's typically
 used to allow or disallow other users to write to his terminal.</para></sect4>
 
 <sect4><title>pidof</title>

appendixa/textutils-desc.xml

@@ -40,8 +40,8 @@ standard output.</para></sect4>
 writing to standard output.</para></sect4>
 
 <sect4><title>head</title>
-<para>Print first xx (10 by default) lines of each specified file to standard 
-output.</para></sect4>
+<para>head prints the first xx (10 by default) lines of each specified file to
+standard output.</para></sect4>
 
 <sect4><title>join</title>
 <para>join joins lines of two files on a common field.</para></sect4>
@@ -101,7 +101,7 @@ in specified files.</para></sect4>
 output.</para></sect4>
 
 <sect4><title>uniq</title>
-<para>Uniq removes duplicate lines from a sorted file.</para></sect4>
+<para>uniq removes duplicate lines from a sorted file.</para></sect4>
 
 <sect4><title>wc</title>
 <para>wc prints line, word, and byte counts for each specified file, and a

index.xml

@@ -4,8 +4,8 @@
 
 <!ENTITY book SYSTEM "book/book.xml">
 
-<!ENTITY version "20020521">
-<!ENTITY releasedate "May 21st, 2002">
+<!ENTITY version "20020523">
+<!ENTITY releasedate "May 23rd, 2002">
 
 <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
 <!ENTITY http-root "http://ftp.linuxfromscratch.org">