Changeset 87c057b

Timestamp:

03/22/2001 03:27:52 AM (23 years ago)

Author:

Simon Perreault <nomis80@…>

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:

d251197

Parents:

9bfaaae

Message:

Grammar fixes.

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

Location:

chapter02

Files:

• bootscripts.xml (modified) (1 diff)
• commands.xml (modified) (3 diffs)
• install.xml (modified) (5 diffs)

chapter02/bootscripts.xml

@@ -3 +3 @@
 
 <para>
-Typing out all the bootscripts in chapters 7 and 9 can be a long tedious
+Typing out all the bootscripts in chapters 7 and 9 can be a long, tedious
 process, not to mention very error-prone.
 </para>

chapter02/commands.xml

@@ -6 +6 @@
 commands for the packages installed in this book. These files can be
 used to dump to a shell and install the packages, though some files 
-need to be modified (for example when the console-tools package is 
-installed it is needed to select the keyboard layout file which can't be
+need to be modified (for example, when the console-tools package is 
+installed, it is needed to select the keyboard layout file, which can't be
 guessed).
 </para>
@@ -15 +15 @@
 changed between the different LFS versions as well. A user just downloads the
 lfs-commands tarball for this book version and the previous book version 
-and run a diff on the files. That way it is possible to see which packages
+and runs a diff on the files. That way it is possible to see which packages
 have 
-updated installation instructions and he can modify his own scripts, or 
+updated installation instructions, and he can modify his own scripts or 
 reinstall a package if it seems necessary.
 </para>
@@ -26 +26 @@
 http://download.linuxfromscratch.org/lfs-commands/</ulink> or <ulink
 url="ftp://download.linuxfromscratch.org/lfs-commands/">
-ftp://download.linuxfromscratch.org/lfs-commands/</ulink>
+ftp://download.linuxfromscratch.org/lfs-commands/</ulink>.
 </para>
 

chapter02/install.xml

@@ -5 +5 @@
 Before a user can actually start doing something with a package, he needs
 to unpack it first. Often the package files are tar'ed and
-gzip'ed. (that can determined by looking at the extension of the file.
-tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
+gzip'ed. (That can determined by looking at the extension of the file.
+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. 
-There is also the possibility  that a .tar.bz2 file can be downloaded.
-Such a file is tar'ed and compressed with the bzip2 program. 
+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. 
 Bzip2 achieves a better compression than the commonly used gzip does. In 
-order to use bz2 archives the bzip2 program needs to be installed. 
-Most if not every distribution comes with this program so chances are 
-high it is already installed on the host-system. If not, it's installed using 
+order to use bz2 archives, the bzip2 program needs to be installed. 
+Most if not every distribution comes with this program, so chances are 
+high it is already installed on the host system. If not, it's installed using 
 the distribution's installation tool.
 </para>
@@ -56 +56 @@
 Some tar programs (most of them nowadays but not all of them) are
 slightly modified to be able to use bzip2 files directly using either
-the I or the y tar parameter which works the same as the z tar parameter
+the I or the y tar parameter, which works the same as the z tar parameter
 to handle gzip archives.
 </para>
@@ -71 +71 @@
 
 <para>
-When the archive is unpacked a new directory will be created under the
+When the archive is unpacked, a new directory will be created under the
 current directory (and this document assumes that the archives are unpacked
 under the $LFS/usr/src directory). A user has to enter that new directory
-before continuing with the installation instructions. So every time the
+before continuing with the installation instructions. So, every time the
 book is going to install a program, it's up to the user to unpack the source
 archive.
@@ -80 +80 @@
 
 <para>
-f a file is gzip'ed, it is unpacked by running:
+If a file is gzip'ed, it is unpacked by running:
 </para>
 
@@ -90 +90 @@
 
 <para>
-After a package is installed two things can be done with it. 
-Either the directory that contains the sources can be deleted 
-or it can be kept.
-If it is kept, that's fine with me. But, if the same package is needed
+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 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, it might end up in trouble because old