Adding some markup, and other brush-ups.

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

1 files changed, 30 insertions, 28 deletions

diff --git a/chapter05/glibc-inst.xml b/chapter05/glibc-inst.xml
index 02c26237d..fcf891cba 100644
--- a/chapter05/glibc-inst.xml
+++ b/chapter05/glibc-inst.xml
@@ -9,8 +9,8 @@ Glibc-linuxthreads in that directory, not in the directory where you usually
 unpack all the sources.</para>
 
 <note><para>We are going to run the test suite for Glibc in this chapter.
-However, it's worth pointing out that the Glibc test suite we run in this
-section is considered not as important as the one we run in Chapter 6.</para></note>
+However, it's worth pointing out that running the Glibc test suite here 
+is considered not as important as running it in Chapter 6.</para></note>
 
 <para>This package is known to behave badly when you have changed its
 default optimization flags (including the -march and -mcpu options).
@@ -89,7 +89,7 @@ running the test suite.</para>
 <screen><userinput>make check</userinput></screen>
 
 <para>The Glibc test suite is highly dependent on certain functions of your host
-system, in particular the kernel. Additionally, here in Chapter 5, some tests
+system, in particular the kernel. Additionally, here in Chapter 5 some tests
 can be adversely affected by existing tools or environmental issues on the host
 system. Of course, these won't be a problem when we run the Glibc test suite
 inside the chroot environment of Chapter 6. In general, the Glibc test suite is
@@ -98,34 +98,36 @@ unavoidable in certain circumstances. Here is a list of the most common issues
 we are aware of:</para>
 
 <itemizedlist>
-<listitem><para>The math tests sometimes fail when running on systems where the 
-CPU is not a relatively new genuine Intel or genuine AMD. Certain optimization
-settings are also known to be a factor here.</para></listitem>
+<listitem><para>The <emphasis>math</emphasis> tests sometimes fail when running
+on systems where the CPU is not a relatively new genuine Intel or authentic AMD.
+Certain optimization settings are also known to be a factor here.</para></listitem>
 
-<listitem><para>The gettext test sometimes fails due to host system issues. The
-exact reasons are not yet clear.</para></listitem>
+<listitem><para>The <emphasis>gettext</emphasis> test sometimes fails due to
+host system issues. The exact reasons are not yet clear.</para></listitem>
 
-<listitem><para>The atime test sometimes fails when the LFS partition is mounted
-with the noatime option or due to other file system quirks.</para></listitem>
+<listitem><para>The <emphasis>atime</emphasis> test sometimes fails when the
+LFS partition is mounted with the <emphasis>noatime</emphasis> option, or due
+to other file system quirks.</para></listitem>
 
-<listitem><para>In general, when running on slower hardware, some tests might
-fail due to test timeouts being exceeded.</para></listitem>
+<listitem><para>The <emphasis>shm</emphasis> test might fail when the host
+system is running the devfs file system but doesn't have the tmpfs file system
+mounted at <filename>/dev/shm</filename> due to lack of support for tmpfs in
+the kernel.</para></listitem>
 
-<listitem><para>The shm test might fail in the circumstances of the host system
-running the devfs file system but not having the tmpfs file system mounted at
-/dev/shm due to lack of support for tmpfs in the kernel.</para></listitem>
+<listitem><para>When running on older and slower hardware, some tests might
+fail due to test timeouts being exceeded.</para></listitem>
 </itemizedlist>
 
 <para>In summary, don't worry too much if you see Glibc test suite failures here
 in Chapter 5. The Glibc in Chapter 6 is the one we'll ultimately end up using so
 that is the one we would really like to see pass. But please keep in mind, even
-in Chapter 6 some failures could still occur, the math tests for example. When
-experiencing a failure, note the failure then continue on by reissuing the
-<userinput>make check</userinput>. The test suite should pick up where it left
-off and continue on. You can circumvent this stop-start sequence by issuing a
-<userinput>make -k check</userinput>. But If you do that, be sure to log the
-output so that you can later on peruse the log file and examine the total number
-of failures.</para>
+in Chapter 6 some failures could still occur -- the <emphasis>math</emphasis>
+tests for example. When experiencing a failure, make a note of it, then
+continue by reissuing the <userinput>make check</userinput>. The test suite
+should pick up where it left off and continue on. You can circumvent this
+stop-start sequence by issuing a <userinput>make -k check</userinput>. But if
+you do that, be sure to log the output so that you can later peruse the log
+file and examine the total number of failures.</para>
 
 <para>Now install the package:</para>
 
@@ -134,8 +136,8 @@ of failures.</para>
 <para>Different countries and cultures have varying conventions for how to
 communicate. These conventions range from very simple ones, such as the format
 for representing dates and times, to very complex ones, such as the language
-spoken. This "internationalization" works by means of locales. We'll install the
-Glibc locales now:</para>
+spoken. The "internationalization" of GNU programs works by means of
+<emphasis>locales</emphasis>. We'll install the Glibc locales now:</para>
 
 <screen><userinput>make localedata/install-locales</userinput></screen>
 
@@ -143,10 +145,10 @@ Glibc locales now:</para>
 those locales which you need or want. This can be achieved by using the
 <userinput>localedef</userinput> command. Information on this can be
 found in the <filename>INSTALL</filename> file in the
-<filename>glibc-&glibc-version;</filename> source. However, there are a
-number of locales that are essential for the tests of future packages
-to pass correctly, in particular, the libstdc++ tests from GCC.  The following 
-instructions, instead of the install-locales command above, will install 
+<filename>glibc-&glibc-version;</filename> source. However, there are a number
+of locales that are essential for the tests of future packages to pass, in
+particular, the <emphasis>libstdc++</emphasis> tests from GCC.  The following
+instructions, instead of the install-locales target above, will install
 the minimum set of locales necessary for the tests to run successfully:</para>
 
 <screen><userinput>mkdir -p /tools/lib/locale