Changeset 58f92b0 for chapter02/creatingpartition.xml

Timestamp:

09/22/2022 07:31:32 PM (2 years ago)

Author:

David Bryant <davidbryant@…>

Branches:

11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

4ca79662

Parents:

b00063f

Message:

Correcting idiom / syntax again, based on feedback from Bruce & Doug.

File:

• chapter02/creatingpartition.xml (modified) (5 diffs)

chapter02/creatingpartition.xml

@@ -95 +95 @@
     <para>Swapping is never good. For mechanical hard drives you can generally
     tell if a system is swapping by just listening to disk activity and
-    observing how the system reacts to commands. With an SSD drive you will not
+    observing how the system reacts to commands. With an SSD you will not
     be able to hear swapping, but you can tell how much swap space is being used
     by running the <command>top</command> or <command>free</command> programs.  Use of
-    an SSD drive for a swap partition should be avoided if possible.  The first
+    an SSD for a swap partition should be avoided if possible.  The first
     reaction to swapping should be to check for an unreasonable command such as
     trying to edit a five gigabyte file. If swapping becomes a normal
@@ -113 +113 @@
     loader. This partition will normally be labeled 'BIOS Boot' if using
     <command>fdisk</command> or have a code of <emphasis>EF02</emphasis> if
-    using the <command>gdisk</command>.</para>
+    using the <command>gdisk</command> command.</para>
 
     <note><para>The Grub Bios partition must be on the drive that the BIOS
@@ -156 +156 @@
       <filename class="directory">/usr</filename> is normally not needed.
       If you create it anyway, you should make a partition large enough to
-      fit all the programs and libraries in the system.  The root partition can be
+      fit all the programs and libraries in the system. The root partition can be
       very small (maybe just one gigabyte) in this configuration, so it's
       suitable for a thin client or diskless workstation (where
       <filename class="directory">/usr</filename> is mounted from a remote
-      server).  However you should be aware that an initramfs (not covered by
+      server). However, you should be aware that an initramfs (not covered by
       LFS) will be needed to boot a system with a separate
       <filename class="directory">/usr</filename> partition.</para></listitem>
@@ -175 +175 @@
       gigabytes.  If you have enough RAM, you can mount a
       <systemitem class='filesystem'>tmpfs</systemitem> on /tmp to make
-      the accesses to temporary files faster.</para></listitem>
+      access to temporary files faster.</para></listitem>
 
       <listitem revision='systemd'><para>/tmp &ndash; By default, systemd
       mounts a <systemitem class='filesystem'>tmpfs</systemitem> here.
-      If you want to override the behavior, follow
-      <xref linkend='systemd-no-tmpfs'/> configuring the LFS
+      If you want to override that behavior, follow
+      <xref linkend='systemd-no-tmpfs'/> when configuring the LFS
       system.</para></listitem>
 
@@ -191 +191 @@
     </itemizedlist>
 
-    <para>Any separate partition that you want automatically mounted upon boot
-    needs to be specified in the <filename>/etc/fstab</filename>. Details
-    about how to specify partitions will be discussed in <xref
-    linkend="ch-bootable-fstab"/>.  </para>
+    <para>Any separate partition that you want automatically mounted when the
+    system starts must be specified in the <filename>/etc/fstab</filename> file.
+    Details about how to specify partitions will be discussed in <xref
+    linkend="ch-bootable-fstab"/>.</para>
 
     </sect3>