Text updates in preface for cross2

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11908 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

5 files changed, 34 insertions, 18 deletions

diff --git a/general.ent b/general.ent
index a0a3cd90f..4a52f3b41 100644
--- a/general.ent
+++ b/general.ent
@@ -1,13 +1,13 @@
-<!ENTITY version         "20200603-cross2">
+<!ENTITY version         "20200608-cross2">
 <!ENTITY short-version   "svn">  <!-- Used below in &blfs-book; 
                                       Change to x.y for release but not -rc releases -->
 <!ENTITY generic-version "cross-chap5"> <!-- Use "development"  or "x.y[-pre{x}]" -->
 
-<!ENTITY versiond        "20200606-cross2-systemd">
+<!ENTITY versiond        "20200608-cross2-systemd">
 <!ENTITY short-versiond  "systemd">
-<!ENTITY generic-versiond "systemd"> 
+<!ENTITY generic-versiond "20200608-cross2-systemd"> 
 
-<!ENTITY releasedate     "June 6th, 2020">
+<!ENTITY releasedate     "June 8th, 2020">
 
 <!ENTITY copyrightdate   "1999-2020"><!-- jhalfs needs a literal dash, not &ndash; -->
 
diff --git a/prologue/architecture.xml b/prologue/architecture.xml
index f23d19cab..9916840f5 100644
--- a/prologue/architecture.xml
+++ b/prologue/architecture.xml
@@ -32,7 +32,7 @@ using 4 cores, the following statistics were measured:</para>
 <para>As you can see, on the same hardware, the 64-bit build is only 3% faster
 and is 22% larger than the 32-bit build. If you plan to use LFS as a LAMP
 server, or a firewall, a 32-bit CPU may be largely sufficient. On the other
-hand, several packages in BLFS now need more that 4GB of RAM to be built
+hand, several packages in BLFS now need more than 4GB of RAM to be built
 and/or to run, so that if you plan to use LFS as a desktop, the LFS authors
 recommend building on a 64-bit system.</para>
 
diff --git a/prologue/organization.xml b/prologue/organization.xml
index 4be1ef81c..814bc6025 100644
--- a/prologue/organization.xml
+++ b/prologue/organization.xml
@@ -29,9 +29,16 @@
   </sect2>
 
   <sect2>
-    <title>Part III - Building the LFS System</title>
+    <title>Part III - Building the LFS Cross Toolchain and Temporary Tools</title>
 
-    <para>Part III guides the reader through the building of the LFS
+    <para>Part III provides instructions for building the tools
+    needed for construction the final LFS system.</para>
+  </sect2>
+
+  <sect2>
+    <title>Part IV - Building the LFS System</title>
+
+    <para>Part IV guides the reader through the building of the LFS
     system&mdash;compiling and installing all the packages one by one,
     setting up the boot scripts, and installing the kernel. The resulting
     Linux system is the foundation on which other software can be built to
@@ -40,4 +47,14 @@
     important files that have been installed.</para>
   </sect2>
 
+  <sect2>
+    <title>Part V - Appendices</title>
+
+    <para>Part V provides information about the book itself including
+    acronyms and terms, acknowledgments, package dependencies, 
+    a listing of LFS boot scripts, licenses for the distribution of the 
+    book, and a comprehensive index of packages, programs, libraries, 
+    and scripts.</para>
+  </sect2>
+
 </sect1>
diff --git a/prologue/typography.xml b/prologue/typography.xml
index 86cbfc6b1..e4c7b5c78 100644
--- a/prologue/typography.xml
+++ b/prologue/typography.xml
@@ -80,8 +80,8 @@ EOF</userinput></screen>
   <command>man passwd</command> will print the first man page it finds that
   matches <quote>passwd</quote>, which will be
   <filename>/usr/share/man/man1/passwd.1</filename>. For this example, you will
-  need to run <command>man 5 passwd</command> in order to read the specific page
-  being referred to. It should be noted that most man pages do not have duplicate
+  need to run <command>man 5 passwd</command> in order to read the page
+  being specified. Note that most man pages do not have duplicate
   page names in different sections. Therefore, <command>man <replaceable>&lt;program
   name&gt;</replaceable></command> is generally sufficient.</para>
 
diff --git a/prologue/why.xml b/prologue/why.xml
index 4b1b263e1..ca100e1f9 100644
--- a/prologue/why.xml
+++ b/prologue/why.xml
@@ -118,8 +118,7 @@
       <listitem>
         <para>DejaGNU</para>
 
-        <para>This package contains a framework for testing other programs.
-        It is only installed in the temporary toolchain.</para>
+        <para>This package contains a framework for testing other programs.</para>
       </listitem>
 
       <listitem>
@@ -141,8 +140,9 @@
       <listitem revision="sysv">
         <para>Eudev</para>
 
-        <para>This package is a device manager.  It dynamically controls the entries
-        in the /dev directory as devices are added or removed from the system.
+        <para>This package is a device manager.  It dynamically controls the ownership,
+        permissions, names, and symbolic links of devices in the /dev directory as 
+        devices are added or removed from the system.
         </para>
       </listitem>
 
@@ -166,7 +166,7 @@
         <para>File</para>
 
         <para>This package contains a utility for determining the type of a
-        given file or files. A few packages need it to build.</para>
+        given file or files. A few packages need it in their build scripts.</para>
       </listitem>
 
       <listitem>
@@ -218,7 +218,7 @@
       <listitem>
         <para>Glibc</para>
 
-        <para>This package contains the main C library.  Linux programs would
+        <para>This package contains the main C library.  Linux programs will
         not run without it.</para>
       </listitem>
 
@@ -472,7 +472,7 @@
       <listitem>
         <para>Pkg-config</para>
 
-        <para>This package provides a program to return meta-data about an
+        <para>This package provides a program that returns meta-data about an
         installed library or package.</para>
       </listitem>
 
@@ -558,8 +558,7 @@
         <para>Tcl</para>
 
         <para>This package contains the Tool Command Language used
-        in many test suites in LFS packages.  It is only installed in
-        the temporary toolchain.</para>
+        in many test suites in LFS packages.</para>
       </listitem>
 
       <listitem>