Changeset ebecd08 for chapter07/cleanup.xml

Timestamp:

11/16/2022 07:16:35 PM (18 months ago)

Author:

David Bryant <davidbryant@…>

Branches:

11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc

Children:

091d624d, 16a1647

Parents:

f2dff2d

git-author:

David Bryant <davidbryant@…> (11/16/2022 07:15:01 PM)

git-committer:

David Bryant <davidbryant@…> (11/16/2022 07:16:35 PM)

Message:

Corrected grammar, spelling, and idiom in chapter 7.

File:

• chapter07/cleanup.xml (modified) (10 diffs)

chapter07/cleanup.xml

@@ -14 +14 @@
     <title>Cleaning</title>
 
-    <para>First, remove the currently installed documentation to prevent them
+    <para>First, remove the currently installed documentation files to prevent them
     from ending up in the final system, and to save about 35 MB:</para>
 
@@ -20 +20 @@
 
     <para>Second, on a modern Linux system, the libtool .la files are only
-    useful for libltdl.  No libraries in LFS are expected to be loaded by
-    libltdl, and it's known that some .la files can cause BLFS packages
-    fail to build.  Remove those files now:</para>
+    useful for libltdl.  No libraries in LFS are loaded by
+    libltdl, and it's known that some .la files can cause BLFS package
+    failures.  Remove those files now:</para>
 
 <screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput></screen>
@@ -43 +43 @@
       backed up for later reuse. In case of fatal failures in the subsequent
       chapters, it often turns out that removing everything and starting over
-      (more carefully) is the best option to recover. Unfortunately, all the
+      (more carefully) is the best way to recover. Unfortunately, all the
       temporary files will be removed, too. To avoid spending extra time to
-      redo something which has been built successfully, creating a backup of
+      redo something which has been done successfully, creating a backup of
       the current LFS system may prove useful.
     </para>
@@ -59 +59 @@
     <para>
       The following steps are performed from outside the chroot
-      environment. That means, you have to leave the chroot environment
+      environment. That means you have to leave the chroot environment
       first before continuing. The reason for that is to
       get access to file system locations outside of the chroot
-      environment to store/read the backup archive which should
+      environment to store/read the backup archive, which ought
       not be placed within the
-      <filename class="directory">$LFS</filename> hierarchy for
-      safety reasons.
+      <filename class="directory">$LFS</filename> hierarchy.
     </para>
 
@@ -79 +78 @@
         <systemitem class="username">root</systemitem> on your host system.
         Take extra care about the commands you're going to run as mistakes
-        here can modify your host system. Be aware that the
+        made here can modify your host system. Be aware that the
         environment variable <envar>LFS</envar>
         is set for user <systemitem class="username">lfs</systemitem> by default
@@ -102 +101 @@
     <para>
       Make sure you have at least 1 GB free disk space (the source tarballs
-      will be included in the backup archive) on the filesystem containing
-      directory where you create the backup archive.
+      will be included in the backup archive) on the file system containing
+      the directory where you create the backup archive.
     </para>
 
@@ -109 +108 @@
       Note that the instructions below specify the home directory of the host
       system's <systemitem class="username">root</systemitem> user, which is
-      typically found on the root filesystem.
-    </para>
-
-    <para>
+      typically found on the root file system.
       Replace <envar>$HOME</envar> by a directory of your choice if you
       do not want to have the backup stored in <systemitem
@@ -150 +146 @@
       <filename class="directory">$LFS</filename>, they are included in the
       backup archive as well, so they do not need to be downloaded again. After
-      checking that <envar>$LFS</envar> is set properly,
+      checking that <envar>$LFS</envar> is set properly, you can
       restore the backup by executing the following commands:
     </para>
@@ -168 +164 @@
 
     <para>
-       Again, double check that the environment has been setup properly
+       Again, double check that the environment has been set up properly
        and continue building the rest of the system.
     </para>
@@ -176 +172 @@
          If you left the chroot environment to create a backup or restart
          building using a restore, remember to check that the virtual
-         filesystems are still mounted (<command>findmnt | grep
+         file systems are still mounted (<command>findmnt | grep
          $LFS</command>).  If they are not mounted, remount them now as
          described in <xref linkend='ch-tools-kernfs'/> and re-enter the chroot