Fixed typos, removed old command explanation.

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

appendixa/flex-desc.xml

@@ -12,8 +12,8 @@
 patterns in text.  Pattern recognition is very useful in many applications. 
 A user sets up rules 
 what to look for and flex will make a program that looks for those
-patterns. The reason people use flex is that it is much easier to sets up 
+patterns. The reason people use flex is that it is much easier to set up 
-rules for what to look for than to write the actual program that finds 
+rules for what to look for than to write the actual program which finds 
 the text.</para></sect4>
 
 <sect4><title>flex++</title>

chapter01/changelog.xml

@@ -56,6 +56,10 @@
 </itemizedlist>
 </para></listitem>
 
+<listitem><para>September 18th, 2002 [timothy]: Chapter 06 - Ncurses:
+Removed old <userinput>mv /lib/*.a /usr/lib</userinput> command
+explanation.</para></listitem>
+
 <listitem><para>September 13th, 2002 [gerard]: Chapter 06 - Shadow: Added
 --libdir=/usr/lib to the configure script options. This way a proper
 <filename>libshadow.la</filename> is generated. Also changed the

chapter01/how.xml

@@ -3,7 +3,7 @@
 <?dbhtml filename="how.html" dir="chapter01"?>
 
 <para>We are going to build the LFS system by using a previously installed
-Linux distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc.
+Linux distribution such as Debian, SuSE, Slackware, Mandrake, RedHat, etc.
 We will use the existing Linux system as the development platform, because
 we need tools like a compiler, linker, text editor, and other necessary
 development tools to build our system. Ordinarily, the required tools are
@@ -19,12 +19,14 @@ packages that will form the basic development suite which is used to
 build the actual system, or needed to resolve circular dependencies. For
 example, you need a compiler to build a new compiler, and you need a shell
 in order to install a new shell. The packages in this chapter will be linked
-statically. Static linking describes a method of compiling software so that
+statically.</para>
+
+<para>Static linking describes a method of compiling software so that
 it does not require the presence of libraries when building is complete.
 The resulting program is able to function on its own. The program is able to
 do so because the pieces of the program that would normally remain in the
 libraries are copied from the libraries and built right into the program.
-Ordinarily software is built with dynamic linking. This conserves storage
+Ordinarily, software is built with dynamic linking. This conserves storage
 space and increases the efficiency of many programs. We statically link
 our software in chapter 5 because we will in theory be moving our
 development system to a virtual environment where the already mentioned

chapter02/aboutlfs.xml

@@ -10,8 +10,8 @@ explained in full detail in chapter 4. For example, let's assume that
 the LFS partition is mounted on /mnt/lfs.</para>
 
 <para>For example when you are told to run a command like
-<userinput>./configure --prefix=$LFS</userinput> you actually have to
+<userinput>./configure --prefix=$LFS/static</userinput> you actually have to
-execute <userinput>./configure --prefix=/mnt/lfs</userinput></para>
+execute <userinput>./configure --prefix=/mnt/lfs/static</userinput>.</para>
 
 <para>It's important that this is done no matter where it is read; be it in
 commands entered in a shell, or in a file edited or created.</para>
@@ -23,7 +23,7 @@ This way $LFS can be entered literally instead of replacing it with
 <para><screen><userinput>export LFS=/mnt/lfs</userinput></screen></para>
 
 <para>Now, if you are told to run a command like <userinput>./configure
---prefix=$LFS</userinput> you can type that literally. Your shell will
+--prefix=$LFS/static</userinput> you can type that literally. Your shell will
 replace $LFS with /mnt/lfs when it processes the command line (meaning
 when you hit enter after having typed the command).</para>
 

chapter05/bash-inst.xml

@@ -9,7 +9,7 @@ the instructions of the book version you read exactly.</para>
 
 <para>If both of the files are missing, you have to install the Ncurses
 development package. This package is often called something like 
-<emphasis>Ncurses-dev</emphasis>. If this package is already installed,
+<emphasis>ncurses-dev</emphasis>. If this package is already installed,
 or you just installed it, check for the two files again. Often the 
 <filename>libcurses.a</filename> file is (still) missing. If so, then 
 create <filename>libcurses.a</filename> as a symlink by running the 

chapter05/fileutils-inst.xml

@@ -14,7 +14,7 @@ and has Glibc-2.2.3 (or higher) installed. If that's the case, you'll need
 to remove the fileutils-&fileutils-version; directory and unpack it again
 from the tarball before continuing. We believe this may be the case when
 your distribution has altered Glibc-2.2.3 somehow, but details are
-unavailable at the time.</para>
+unavailable at this time.</para>
 
 <para>To fix this package to compile properly on AMD/Glibc-2.2.3
 machines, run the following command. Do <emphasis>not</emphasis>

chapter06/gcc-exp.xml

@@ -7,13 +7,10 @@ linux distributions.</para>
 
 <para><userinput>--enable-clocale=gnu:</userinput> There is a risk that
 some people will build ABI incompatible C++ libraries if they didn't install
-all the glibc localedata. Using --enable-clocale=gnu ensures that the "right
+all of the glibc localedata. Using --enable-clocale=gnu ensures that the
-thing" is done in all cases. If you don't want to use this option and don't
+"right thing" is done in all cases. If you don't wish to use this option,
-want to build all the locales, then at least make sure you installed the
+then at least build the <emphasis>de_DE</emphasis> locale. When GCC finds
-<emphasis>de_DE</emphasis> locale with Glibc, since that's the specific locale
+this specific locale, then the correct locale mode (<emphasis>gnu</emphasis>)
-GCC will check for to determine which locale mode to use (if de_DE is
+is implemented.</para>
-found, <emphasis>gnu</emphasis> mode is used, which is the corrent one to
-use).</para>
 
 </sect2>
-

chapter06/ncurses-exp.xml

@@ -8,11 +8,6 @@ constructions that are no longer valid in the new C++ standard.</para>
 <para><userinput>--with-shared:</userinput> This enables the build of the
 shared ncurses library files.</para>
 
-<para><userinput>mv /lib/*.a /usr/lib :</userinput> This
-moves all of the static ncurses library files from /lib to /usr/lib.
-/lib should only contain the shared files which are essential to the
-system when /usr may not be mounted.</para>
-
 <para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
 executable.  Ncurses install routine doesn't set the permissions
 properly so we do it manually instead.</para>

entities/makedev.ent

@@ -13,7 +13,7 @@
 <!ENTITY makedev-depversion "1.5">
 <!ENTITY makedev-contversion "1.5">
 <!ENTITY makedev-size "8 KB">
-<!ENTITY makedev-package "MAKEDEV-&makedev-version;.tar.bz2">
+<!ENTITY makedev-package "MAKEDEV-&makedev-version;.bz2">
 
 <!ENTITY makedev-compsize "50 KB">
 <!ENTITY makedev-time "0.07 SBU">

index.xml

@@ -4,8 +4,8 @@
 
 <!ENTITY book SYSTEM "book/book.xml">
 
-<!ENTITY version "20020914">
+<!ENTITY version "20020918">
-<!ENTITY releasedate "September 14th, 2002">
+<!ENTITY releasedate "September 18th, 2002">
 
 <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
 <!ENTITY http-root "http://ftp.linuxfromscratch.org">