Changeset da6e70f

Timestamp:

11/26/2022 06:26:21 PM (17 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:

38311c3, b1c68c7

Parents:

295e337

Message:

Edited Pierre's recent additons,to improve English idiom. Also corrected
capitalization of a title.

Files:

• chapter04/creatingminlayout.xml (modified) (2 diffs)
• chapter07/creatingdirs.xml (modified) (1 diff)

chapter04/creatingminlayout.xml

@@ -9 +9 @@
   <?dbhtml filename="creatingminlayout.html"?>
 
-  <title>Creating a limited directory layout in LFS filesystem</title>
+  <title>Creating a Limited Directory Layout in the LFS Filesystem</title>
 
   <para>In this section, we begin populating the LFS filesystem with the
@@ -42 +42 @@
   <note>
     <para>
-      LFS editors have deliberately decided not to use a
+      The LFS editors have deliberately decided not to use a
       <filename class="directory">/usr/lib64</filename> directory.  Several
-      steps are taken so that the toolchain does not use it. If for any
+      steps are taken to be sure the toolchain will not use it. If for any
       reason this directory appears (either because you made an error in
-      following the instructions, or because you install a binary package that
-      creates it after finishing LFS), it may break the instructions given in
-      the book. You should often ensure that this directory is non-existent.
+      following the instructions, or because you installed a binary package that
+      created it after finishing LFS), it may break your system.
+      You should always be sure this directory does not exist.
     </para>
   </note>

chapter07/creatingdirs.xml

@@ -71 +71 @@
   <warning>
     <para>
-      The FHS does not enforce the existence of the directory
+      The FHS does not mandate the existence of the directory
       <filename class="directory">/usr/lib64</filename>, and the LFS editors
-      have decided not to use it. For the instructions in LFS and BLFS to work,
-      it is imperative that this directory be non-existent. You should often
-      check that it does not exist, because it is easy to inadvertently
-      create it, which will likely break your system.
+      have decided not to use it. For the instructions in LFS and BLFS to work correctly,
+      it is imperative that this directory be non-existent. From time to time you should
+      verify that it does not exist, because it is easy to create it
+      inadvertently, and this will probably break your system.
     </para>
   </warning>