Changeset b59b371 for chapter07/cleanup.xml

Timestamp:

11/19/2022 08:27:13 AM (18 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/clfs-ng

Children:

2ef64c4

Parents:

4d3f41c (diff), 651f491 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

File:

• chapter07/cleanup.xml (modified) (4 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>
@@ -72 +72 @@
       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