Changeset 1e163254 for chapter01/how.xml

Timestamp:

09/15/2003 09:47:44 PM (21 years ago)

Author:

Alex Gronenwoud <alex@…>

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, 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:

1ce39f2

Parents:

6ebafb4d

Message:

Correcting several typos and some inconsistencies.

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

File:

• chapter01/how.xml (modified) (3 diffs)

chapter01/how.xml

@@ -17 +17 @@
 
 <para>Chapter 5 will then discuss the installation of a number of packages that 
-will form the basic development suite (or toolset) which is used to build the 
+will form the basic development suite (or tool-set) which is used to build the 
 actual system in Chapter 6. Some of these packages are needed to resolve 
 circular dependencies. For example, to compile a compiler you need a 
@@ -32 +32 @@
 the toolchain will be dynamically linked against the newly built Glibc. The 
 remaining Chapter 5 packages are all built using this second pass toolchain and 
-dynamically linked against the new host independant Glibc. When this is done, 
+dynamically linked against the new host-independent Glibc. When this is done, 
 the LFS installation process will no longer depend on the host distribution, 
 with the exception of the running kernel. This is known as <quote>self 
@@ -51 +51 @@
 until it is too late. A well known issue is that statically linked binaries 
 compiled on a Glibc-2.2.x based system that then contain calls to the 
-getpwuid() function crash when run on a glibc-2.3.x based system.  You are 
+<emphasis>getpwuid()</emphasis> function crash when run on a Glibc-2.3.x based
+system.  You are 
 about to build a Glibc-2.3.x based system.  You do not want to build something 
-that is going to crash do you?  Finally, the Glibc Autoconf tests produce 
+that is going to crash do you?  Finally, the Glibc autoconf tests produce 
 different results depending on whether an existing Glibc is found on the host 
 distribution. This can lead to inconsistencies and encourages hacks and