Correct capitalization, spelling, grammar, and idiom. Tighten the

prose by removing some circumlocutions.

1 files changed, 12 insertions, 12 deletions

diff --git a/chapter08/introduction.xml b/chapter08/introduction.xml
index b23175b3f..b05a9761a 100644
--- a/chapter08/introduction.xml
+++ b/chapter08/introduction.xml
@@ -22,17 +22,17 @@
 
   <para>We do not recommend using optimizations.  They can make
   a program run slightly faster, but they may also cause compilation
-  difficulties and problems when running the program.  If a package refuses to
+  difficulties, and problems when running the program.  If a package refuses to
   compile when using optimization, try to compile it without optimization and
   see if that fixes the problem. Even if the package does compile when using
   optimization, there is the risk it may have been compiled incorrectly because
-  of the complex interactions between the code and build tools.  Also note that
+  of the complex interactions between the code and the build tools.  Also note that
   the <option>-march</option> and <option>-mtune</option> options using values
   not specified in the book have not been tested. This may cause problems with
   the toolchain packages (Binutils, GCC and Glibc).  The small potential gains
-  achieved in using compiler optimizations are often outweighed by the risks.
+  achieved by using compiler optimizations are often outweighed by the risks.
   First-time builders of LFS are encouraged to build without custom
-  optimizations. The subsequent system will still run very fast and be stable
+  optimizations. The resulting system will still run very fast, and be stable
   at the same time.</para>
 
   <para>Before the installation instructions, each installation page provides
@@ -42,31 +42,31 @@
   instructions, there is a list of programs and libraries (along with brief
   descriptions) that the package installs.</para>
 
-  <note><para>The SBU values and required disk space includes test suite data
+  <note><para>The SBU values and required disk space include test suite data
   for all applicable packages in <xref linkend="chapter-building-system"/>. SBU
   values have been calculated using a single CPU core (-j1) for all
   operations.</para></note>
 
   <sect2>
-    <title>About libraries</title>
+    <title>About Libraries</title>
 
     <para>In general, the LFS editors discourage building and installing static
-    libraries.  The original purpose for most static libraries has been made
+    libraries.  Most static libraries have been made
     obsolete in a modern Linux system.  In addition, linking a static library
     into a program can be detrimental.  If an update to the library is needed
-    to remove a security problem, all programs that use the static library will
-    need to be relinked to the new library.  Since the use of static libraries
+    to remove a security problem, every program that uses the static library will
+    need to be relinked with the new library.  Since the use of static libraries
     is not always obvious, the relevant programs (and the procedures needed to
     do the linking) may not even be known.</para>
 
-    <para>In the procedures in this chapter, we remove or disable installation of
+    <para>The procedures in this chapter remove or disable installation of
     most static libraries. Usually this is done by passing a
     <option>--disable-static</option> option to <command>configure</command>.
     In other cases, alternate means are needed. In a few cases, especially
-    glibc and gcc, the use of static libraries remains essential to the general
+    Glibc and GCC, the use of static libraries remains an essential feature of the
     package building process. </para>
 
-    <para>For a more complete discussion of libraries, see the discussion
+    <para>For a more complete discussion of libraries, see
     <ulink url="&blfs-book;introduction/libraries.html">
     Libraries: Static or shared?</ulink> in the BLFS book.</para>