Changeset 2c094d6 for chapter06/introduction.xml

Timestamp:

09/28/2002 09:08:29 PM (22 years ago)

Author:

Timothy Bauscher <timothy@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

4d46e012

Parents:

f5cc1c17

Message:

Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.

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

File:

• chapter06/introduction.xml (modified) (3 diffs)

chapter06/introduction.xml

@@ -4 +4 @@
 
 <para>In this chapter we enter the building site, and start
-constructing our LFS system in earnest.  That is, we chroot into
+constructing our LFS system in earnest. That is, we chroot into
 our temporary mini Linux system, create some auxiliary things,
 and then start installing all the packages, one by one.</para>
@@ -22 +22 @@
 may also cause compilation difficulties. If a package refuses
 to compile when using optimization, try to compile it without
-optimization and see if  the problem goes away.</para>
+optimization and see if the problem goes away.</para>
 
 <para>The order in which packages are installed in this chapter has
@@ -28 +28 @@
 to <filename class="directory">/static</filename> hard-wired into it.
 For the same reason, <emphasis>do not </emphasis> compile packages
-in parallel.  Compiling in parallel may save you some time (especially on
+in parallel. Compiling in parallel may save you some time (especially on
 dual-CPU machines), but it could result in a program containing a
 hard-wired path to <filename class="directory">/static</filename>,