Changeset cc107b1

Timestamp:

04/12/2001 11:28:53 PM (23 years ago)

Author:

Gerard Beekmans <gerard@…>

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, v3_0, v3_1, v3_2, v3_3, 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:

bb24243

Parents:

280bcc8

Message:

Grammar fixes

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

File:

• chapter02/install.xml (modified) (4 diffs)

chapter02/install.xml

@@ -8 +8 @@
 Tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
 example.) I'm not going to write down every time how to ungzip and how 
-to untar an archive. I will tell how to do that once, in this section. 
+to untar an archive. I will explain how to do that once, in this section. 
 There is also the possibility that a .tar.bz2 file could be downloaded.
 Such a file would be tar'ed and compressed with the bzip2 program. 
@@ -73 +73 @@
 <para>
 When the archive is unpacked, a new directory will be created under the
-current directory (and this document assumes that the archives are unpacked
+current directory (and this book assumes that the archives are unpacked
 under the $LFS/usr/src directory). Please enter that new directory
 before continuing with the installation instructions. Again, every time
@@ -109 +109 @@
 After a package is installed, two things can be done with it:
 either the directory that contains the sources can be deleted,
-either it can be kept. If it is kept, that's fine with me, but if the 
+or it can be kept. If it is kept, that's fine with me, but if the 
 same package is needed again in a later chapter, the directory 
 needs to be deleted first before using it again. If this is not done, 
 you might end up in trouble because old settings will be used (settings 
-that apply to the normal Linux system but which don't always apply to 
+that apply to the host system but which don't always apply to 
 the LFS system). Doing a simple make clean or make distclean does not 
 always guarantee a totally clean source tree.
@@ -119 +119 @@
 
 <para>
-There is one exception to that rule: don't remove the linux kernel source
+There is one exception to that rule: don't remove the Linux kernel source
 tree. A lot of programs need the kernel headers, so that's the only
 directory that should not be removed, unless no software is to be compiled