Index: postlfs/filesystems/aboutlvm.xml
===================================================================
--- postlfs/filesystems/aboutlvm.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/aboutlvm.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -16,50 +16,70 @@
   <title>About Logical Volume Management (LVM)</title>
 
-  <para>LVM manages disk drives.  It allows multiple drives and partitions
-  to be combined into larger <emphasis>volume groups</emphasis>, assists in
-  making backups through a <emphasis>snapshot</emphasis>, and allows for
-  dynamic volume resizing. It can also provide mirroring similar to
-  a RAID 1 array.</para>
+  <para>
+    LVM manages disk drives.  It allows multiple drives and partitions
+    to be combined into larger <emphasis>volume groups</emphasis>, assists in
+    making backups through a <emphasis>snapshot</emphasis>, and allows for
+    dynamic volume resizing. It can also provide mirroring similar to
+    a RAID 1 array.
+  </para>
 
-  <para>A complete discussion of LVM is beyond the scope of this introduction,
-  but basic concepts are presented below.</para>
+  <para>
+    A complete discussion of LVM is beyond the scope of this introduction,
+    but basic concepts are presented below.
+  </para>
 
-  <para>To run any of the commands presented here, the <xref linkend='lvm2'/>
-  package must be installed.  All commands must be run as the <systemitem
-  class="username">root</systemitem> user.</para>
+  <para>
+    To run any of the commands presented here, the <xref linkend='lvm2'/>
+    package must be installed.  All commands must be run as the <systemitem
+    class="username">root</systemitem> user.
+  </para>
 
-  <para>Management of disks with lvm is accomplished using the following
-  concepts: </para>
+  <para>
+    Management of disks with lvm is accomplished using the following concepts: 
+  </para>
 
   <variablelist>
     <varlistentry>
       <term>physical volumes</term>
-      <listitem><para>These are physical disks or partitions such as
-      /dev/sda3 or /dev/sdb.</para></listitem>
+      <listitem>
+        <para>
+          These are physical disks or partitions such as
+          /dev/sda3 or /dev/sdb.
+        </para>
+      </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>volume groups</term>
-      <listitem><para>These are named groups of physical volumes that
-      can be manipulated by the administrator.  The number of physical
-      volumes that make up a volume group is arbitrary.  Physical volumes
-      can be dynamically added or removed from a volume group.
-      </para></listitem>
+      <listitem>
+        <para>
+          These are named groups of physical volumes that
+          can be manipulated by the administrator.  The number of physical
+          volumes that make up a volume group is arbitrary.  Physical volumes
+          can be dynamically added or removed from a volume group.
+        </para>
+      </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>logical volumes</term>
-      <listitem><para>Volume groups may be subdivided into logical volumes.
-      Each logical volume can then be individually formatted as if it were a
-      regular Linux partition. Logical volumes may be dynamically resized by
-      the administrator according to need.</para></listitem>
+      <listitem>
+        <para>
+          Volume groups may be subdivided into logical volumes. Each logical
+          volume can then be individually formatted as if it were a regular
+          Linux partition. Logical volumes may be dynamically resized by
+          the administrator according to need.
+        </para>
+      </listitem>
 
     </varlistentry>
   </variablelist>
 
-  <para>To give a concrete example, suppose that you have two 2 TB disks.
-  Also suppose a really large amount of space is required for a very large database,
-  mounted on <filename class='directory'>/srv/mysql</filename>.  This is what
-  the initial set of partitions would look like:</para>
+  <para>
+    To give a concrete example, suppose that you have two 2 TB disks. Also
+    suppose a really large amount of space is required for a very large
+    database, mounted on <filename class='directory'>/srv/mysql</filename>.
+    This is what the initial set of partitions would look like:
+  </para>
 
   <screen><literal>Partition  Use    Size      Partition Type
@@ -71,28 +91,40 @@
 /dev/sdb2  LVM    remainder 8e (LVM)</literal></screen>
 
-  <para>First initialize the physical volumes:</para>
+  <para>
+    First initialize the physical volumes:
+  </para>
 
   <screen><userinput>pvcreate /dev/sda4 /dev/sdb2</userinput></screen>
 
-  <note><para>A full disk can be used as part of a physical volume, but
-  beware that the <command>pvcreate</command> command will destroy any
-  partition information on that disk.</para></note>
+  <note>
+    <para>
+      A full disk can be used as part of a physical volume, but
+      beware that the <command>pvcreate</command> command will destroy any
+      partition information on that disk.
+    </para>
+  </note>
 
-  <para>Next create a volume group named lfs-lvm:</para>
+  <para>
+    Next create a volume group named lfs-lvm:
+  </para>
 
   <screen><userinput>vgcreate lfs-lvm /dev/sda4  /dev/sdb2</userinput></screen>
 
-  <para>The status of the volume group can be checked by running the command
-  <command>vgscan</command>. Now create the logical volumes.  Since there is
-  about 3900 GB available, leave about 900 GB free for expansion. Note that the
-  logical volume named <emphasis>mysql</emphasis> is larger than any physical
-  disk.  </para>
+  <para>
+    The status of the volume group can be checked by running the command
+    <command>vgscan</command>. Now create the logical volumes.  Since there
+    is about 3900 GB available, leave about 900 GB free for expansion. Note
+    that the logical volume named <emphasis>mysql</emphasis> is larger than
+    any physical disk.
+  </para>
 
   <screen><userinput>lvcreate --name mysql --size 2500G lfs-lvm
 lvcreate --name home  --size  500G lfs-lvm</userinput></screen>
 
-  <para>Finally the logical volumes can be formatted and mounted.  In this
-  example, the jfs file system (<xref linkend='jfsutils'/>) is used for
-  demonstration purposes.</para>
+  <para>
+    Finally the logical volumes can be formatted and mounted.  In this
+    example, the jfs file system (<xref linkend='jfsutils'/>) is used for
+    demonstration purposes.
+  </para>
 
   <screen><userinput>mkfs -t ext4 /dev/lfs-lvm/home
@@ -102,14 +134,20 @@
 mount /dev/lfs-lvm/mysql /srv/mysql</userinput></screen>
 
-  <para>The LFS boot scripts automatically make these file systems available
-  to the system in the checkfs script.  Edit the <filename>/etc/fstab</filename>
-  file as required to automatically mount them.</para>
+  <para>
+    The LFS boot scripts automatically make these file systems available to
+    the system in the checkfs script. Edit the <filename>/etc/fstab</filename>
+    file as required to automatically mount them.
+  </para>
 
-  <para>A LVM logical volume can host a root filesystem, but requires the use
-  of an initramfs (initial RAM file system) and is not discussed here.</para>
+  <para>
+    A LVM logical volume can host a root filesystem, but requires the use
+    of an initramfs (initial RAM file system) and is not discussed here.
+  </para>
 
-  <para>For a more information about LVM, see the <ulink
-  url="http://www.tldp.org/HOWTO/LVM-HOWTO/">LVM HOWTO</ulink> and
-  the lvm man pages.</para>
+  <para>
+    For a more information about LVM, see the <ulink
+    url="http://www.tldp.org/HOWTO/LVM-HOWTO/">LVM HOWTO</ulink> and
+    the lvm man pages.
+  </para>
 
 </sect1>
Index: postlfs/filesystems/aboutraid.xml
===================================================================
--- postlfs/filesystems/aboutraid.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/aboutraid.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -16,41 +16,55 @@
   <title>About RAID</title>
 
-  <para>The storage technology known as RAID (Redundant Array of
-  Independent Disks) combines multiple physical disks into a logical
-  unit.  The drives can generally be combined to provide data
-  redundancy or to extend the size of logical units beyond the
-  capability of the physical disks or both.  The technology
-  also allows for providing hardware maintenance without powering
-  down the system.</para>
-
-  <para>The types of RAID organization are described in the <ulink
-  url="https://raid.wiki.kernel.org/index.php/Overview#The_RAID_levels">
-  RAID Wiki</ulink>.</para>
-
-  <para>Note that while RAID provides protection against disk
-  failures, it is not a substitute for backups.  A file deleted
-  is still deleted on all the disks of a RAID array.  Modern backups
-  are generally done via <xref linkend='rsync'/>.</para>
-
-  <para>There are three major types of RAID implementation:
-  Hardware RAID, BIOS-based RAID, and Software RAID.</para>
+  <para>
+    The storage technology known as RAID (Redundant Array of
+    Independent Disks) combines multiple physical disks into a logical
+    unit.  The drives can generally be combined to provide data
+    redundancy or to extend the size of logical units beyond the
+    capability of the physical disks or both.  The technology
+    also allows for providing hardware maintenance without powering
+    down the system.
+  </para>
+
+  <para>
+    The types of RAID organization are described in the <ulink
+    url="https://raid.wiki.kernel.org/index.php/Overview#The_RAID_levels">
+    RAID Wiki</ulink>.
+  </para>
+
+  <para>
+    Note that while RAID provides protection against disk
+    failures, it is not a substitute for backups.  A file deleted
+    is still deleted on all the disks of a RAID array.  Modern backups
+    are generally done via <xref linkend='rsync'/>.
+  </para>
+
+  <para>
+    There are three major types of RAID implementation:
+    Hardware RAID, BIOS-based RAID, and Software RAID.
+  </para>
 
   <sect2 id="hwraid">
     <title>Hardware RAID</title>
-    <para>Hardware based RAID provides capability through proprietary
-    hardware and data layouts.  The control and configuration is generally
-    done via firmware in conjunction with executable programs made
-    available by the device manufacturer.  The capabilities are
-    generally supplied via a PCI card, although there are some
-    instances of RAID components integrated in to the motherboard.
-    Hardware RAID may also be available in a stand-alone enclosure.</para>
-
-    <para>One advantage of hardware-based RAID is that the drives
-    are offered to the operating system as a logical drive and no
-    operating system dependent configuration is needed.</para>
-
-    <para>Disadvantages include difficulties in transferring drives
-    from one system to another, updating firmware, or replacing
-    failed RAID hardware.</para>
+    <para>
+      Hardware based RAID provides capability through proprietary
+      hardware and data layouts.  The control and configuration is generally
+      done via firmware in conjunction with executable programs made
+      available by the device manufacturer.  The capabilities are
+      generally supplied via a PCI card, although there are some
+      instances of RAID components integrated in to the motherboard.
+      Hardware RAID may also be available in a stand-alone enclosure.
+    </para>
+
+    <para>
+      One advantage of hardware-based RAID is that the drives
+      are offered to the operating system as a logical drive and no
+      operating system dependent configuration is needed.
+    </para>
+
+    <para>
+      Disadvantages include difficulties in transferring drives
+      from one system to another, updating firmware, or replacing
+      failed RAID hardware.
+    </para>
 
   </sect2>
@@ -59,16 +73,22 @@
     <title>BIOS-based RAID</title>
 
-    <para>Some computers offter a hardware-like RAID implementation in the
-    system BIOS.  Sometime this is referred to as 'fake' RAID as the
-    capabilites are generally incorporated into firmware without any hardware
-    acceleration.</para>
-
-    <para>The advantages and disadvantages of BIOS-based RAID are generally
-    the same as hardware RAID with the additional disadvantage that there
-    is no hardware acceleration.</para>
-
-    <para>In some cases, BIOS-based RAID firmware is enabled by default (e.g.
-    some DELL systems).  If software RAID is desired, this option must be
-    explicitly disabled in the BIOS.</para>
+    <para>
+      Some computers offter a hardware-like RAID implementation in the
+      system BIOS.  Sometime this is referred to as 'fake' RAID as the
+      capabilites are generally incorporated into firmware without any hardware
+      acceleration.
+    </para>
+
+    <para>
+      The advantages and disadvantages of BIOS-based RAID are generally
+      the same as hardware RAID with the additional disadvantage that there
+      is no hardware acceleration.
+    </para>
+
+    <para>
+      In some cases, BIOS-based RAID firmware is enabled by default (e.g.
+      some DELL systems).  If software RAID is desired, this option must be
+      explicitly disabled in the BIOS.
+    </para>
 
   </sect2>
@@ -76,24 +96,30 @@
   <sect2 id="swraid">
   <title>Software RAID</title>
-    <para>Software based RAID is the most flexible form of RAID.  It is
-    easy to install and update and provides full capability on all or
-    part of any drives available to the system.  In BLFS, the RAID software
-    is found in <xref linkend='mdadm'/>.</para>
-
-    <para>Configuring a RAID device is straight forward using
-    <application>mdadm</application>.  Generally devices are created in the
-    <filename class='directory'>/dev</filename> directory as
-    <filename>/dev/mdx</filename> where <emphasis>x</emphasis> is an integer.
-    </para>
-
-    <para>The first step in creating a RAID array is to use partitioning software
-    such as <userinput>fdisk</userinput> or <xref linkend='parted'/> to define the
-    partitions needed for the array.  Usually, there will be one partition on
-    each drive participating in the RAID array, but that is not strictly necessary.
-    For this example, there will be four disk drives:
-    <filename>/dev/sda</filename>,
-    <filename>/dev/sdb</filename>,
-    <filename>/dev/sdc</filename>, and
-    <filename>/dev/sdd</filename>.  They will be partitioned as follows:</para>
+    <para>
+      Software based RAID is the most flexible form of RAID.  It is
+      easy to install and update and provides full capability on all or
+      part of any drives available to the system.  In BLFS, the RAID software
+      is found in <xref linkend='mdadm'/>.
+    </para>
+
+    <para>
+      Configuring a RAID device is straight forward using
+      <application>mdadm</application>.  Generally devices are created in the
+      <filename class='directory'>/dev</filename> directory as
+      <filename>/dev/mdx</filename> where <emphasis>x</emphasis> is an integer.
+    </para>
+
+    <para>
+      The first step in creating a RAID array is to use partitioning software
+      such as <userinput>fdisk</userinput> or <xref linkend='parted'/> to
+      define the partitions needed for the array.  Usually, there will be
+      one partition on each drive participating in the RAID array, but that
+      is not strictly necessary.  For this example, there will be four disk
+      drives:
+      <filename>/dev/sda</filename>,
+      <filename>/dev/sdb</filename>,
+      <filename>/dev/sdc</filename>, and
+      <filename>/dev/sdd</filename>.  They will be partitioned as follows:
+    </para>
 
 <screen><literal>Partition Size     Type                Use
@@ -114,16 +140,24 @@
 sdd2:     300 GB   fd Linux raid auto  /home    (RAID 5) /dev/md2 </literal></screen>
 
-    <para>Is this arrangement, a separate boot partition is created as the
-    first small RAID array and a root filesystem as the secong RAID array,
-    both mirrored.  The third partition is a large (about 1TB) array for the
-    <filename class='directory'>/home</filename> directory.  This provides
-    an ability to stripe data across multiple devices, improving speed for
-    botih reading and writing large files.  Finally, a fourth array is created
-    that concatenates two partitions into a larger device.</para>
-
-    <note><para>All <application>mdadm</application> commands must be run
-    as the <systemitem class="username">root</systemitem> user.</para></note>
-
-    <para>To create these RAID arrays the commands are:</para>
+    <para>
+      In this arrangement, a separate boot partition is created as the
+      first small RAID array and a root filesystem as the secong RAID array,
+      both mirrored.  The third partition is a large (about 1TB) array for the
+      <filename class='directory'>/home</filename> directory.  This provides
+      an ability to stripe data across multiple devices, improving speed for
+      both reading and writing large files.  Finally, a fourth array is created
+      that concatenates two partitions into a larger device.
+    </para>
+
+    <note>
+      <para>
+        All <application>mdadm</application> commands must be run
+        as the <systemitem class="username">root</systemitem> user.
+      </para>
+    </note>
+
+    <para>
+      To create these RAID arrays the commands are:
+    </para>
 
 <screen><userinput>/sbin/mdadm -Cv /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
@@ -133,7 +167,9 @@
         /dev/sda4 /dev/sdb4 /dev/sdc2 /dev/sdd2 </userinput></screen>
 
-    <para>The devices created can be examined by device.  For example,
-    to see the details of <filename>/dev/md1</filename>, use
-    <userinput>/sbin/mdadm --detail /dev/md1</userinput>:  </para>
+    <para>
+      The devices created can be examined by device.  For example,
+      to see the details of <filename>/dev/md1</filename>, use
+      <userinput>/sbin/mdadm --detail /dev/md1</userinput>:
+    </para>
 
 <screen><literal>        Version : 1.2
@@ -161,23 +197,34 @@
        1       8       17        1      active sync   /dev/sdb1</literal></screen>
 
-   <para>From this point, the partitions can be formated with the filesystem of
-   choice (e.g. ext3, ext4, <xref linkend='xfsprogs'/>, <xref linkend='reiserfs'/>,
-   etc).  The formatted partitions can then be mounted.  The
-   <filename>/etc/fstab</filename> file can use the devices created for mounting at
-   boot time and the linux command line in
-   <filename>/boot/grub/grub.cfg</filename> can specify
-   <option>root=/dev/md1</option>.</para>
-
-   <note><para>The swap devices should be specified in the <filename>/etc/fstab</filename>
-   file as normal.  The kernel normally stripes swap data across multiple swap
-   files and should not be made part of a RAID array.</para></note>
-
-   <para>For further options and management details of RAID devices, refer to
-   <userinput>man mdadm</userinput>.</para>
-
-   <para>Additional details for monitoring RAID arrays and dealing with
-   problems can be found at the <ulink
-   url="https://raid.wiki.kernel.org/index.php/Linux_Raid">Linux RAID
-   Wiki</ulink>.</para>
+    <para>
+      From this point, the partitions can be formated with the filesystem of
+      choice (e.g. ext3, ext4, <xref linkend='xfsprogs'/>, <xref
+      linkend='reiserfs'/>, etc).  The formatted partitions can then be
+      mounted.  The <filename>/etc/fstab</filename> file can use the devices
+      created for mounting at boot time and the linux command line in
+      <filename>/boot/grub/grub.cfg</filename> can specify
+      <option>root=/dev/md1</option>.
+    </para>
+
+    <note>
+      <para>
+        The swap devices should be specified in the
+        <filename>/etc/fstab</filename> file as normal.  The kernel normally
+        stripes swap data across multiple swap files and should not be made
+        part of a RAID array.
+      </para>
+    </note>
+
+    <para>
+      For further options and management details of RAID devices, refer to
+      <userinput>man mdadm</userinput>.
+    </para>
+
+    <para>
+      Additional details for monitoring RAID arrays and dealing with
+      problems can be found at the <ulink
+      url="https://raid.wiki.kernel.org/index.php/Linux_Raid">Linux RAID
+      Wiki</ulink>.
+    </para>
 
   </sect2>
Index: postlfs/filesystems/btrfs-progs.xml
===================================================================
--- postlfs/filesystems/btrfs-progs.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/btrfs-progs.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -30,6 +30,8 @@
     <title>Introduction to btrfs-progs</title>
 
-    <para>The <application>btrfs-progs</application> package contains administration
-    and debugging tools for the B-tree file system (btrfs).</para>
+    <para>
+      The <application>btrfs-progs</application> package contains
+      administration and debugging tools for the B-tree file system (btrfs).
+    </para>
 
     &lfs91_checked;
@@ -38,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&btrfs-progs-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&btrfs-progs-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &btrfs-progs-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &btrfs-progs-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &btrfs-progs-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &btrfs-progs-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&btrfs-progs-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&btrfs-progs-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &btrfs-progs-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &btrfs-progs-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &btrfs-progs-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &btrfs-progs-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -85,13 +99,19 @@
     <title>Kernel Configuration</title>
 
-    <para>Enable the following option in the kernel configuration
-    and recompile the kernel:</para>
+    <para>
+      Enable the following option in the kernel configuration
+      and recompile the kernel:
+    </para>
 
 <screen><literal>File systems ---&gt;
   &lt;*/M&gt; Btrfs filesystem support [CONFIG_BTRFS_FS]</literal></screen>
 
-    <note><para>CONFIG_BTRFS_FS_POSIX_ACL and 
-    CONFIG_REISERFS_FS_XATTR are required for some tests.
-    Other Btrfs options in the kernel are optional.</para></note>
+    <note>
+      <para>
+        CONFIG_BTRFS_FS_POSIX_ACL and 
+        CONFIG_REISERFS_FS_XATTR are required for some tests.
+        Other Btrfs options in the kernel are optional.
+      </para>
+    </note>
 
     <indexterm zone="btrfs-progs btrfs-progs-kernel">
@@ -104,6 +124,8 @@
     <title>Installation of btrfs-progs</title>
 
-    <para>Install <application>btrfs-progs</application> by running the following
-    commands:</para>
+    <para>
+      Install <application>btrfs-progs</application> by running the following
+      commands:
+    </para>
 
 <screen><userinput>./configure --prefix=/usr  \
@@ -113,10 +135,16 @@
 make</userinput></screen>
 
-    <note><para>Some tests require grep built with perl regular expressions. To
-    obtain this, rebuild grep with the LFS Chapter 6 instructions after
-    installing <xref linkend="pcre"/>.</para></note>
-
-    <para>Before running tests, build a support program and 
-    disable several that fail:</para>
+    <note>
+      <para>
+        Some tests require grep built with perl regular expressions. To
+        obtain this, rebuild grep with the LFS Chapter 6 instructions after
+        installing <xref linkend="pcre"/>.
+      </para>
+    </note>
+
+    <para>
+      Before running tests, build a support program and 
+      disable several that fail:
+    </para>
 
 <screen remap="test"><userinput>make fssum &amp;&amp;
@@ -131,6 +159,8 @@
 mv tests/misc-tests/025-zstd-compression/test.sh{,.broken}</userinput></screen> 
 
-    <para>To test the results, issue (as the <systemitem
-    class="username">root</systemitem> user): </para>
+    <para>
+      To test the results, issue (as the <systemitem
+      class="username">root</systemitem> user): 
+    </para>
 
 <screen role="root" remap="test"><userinput>pushd tests
@@ -143,6 +173,8 @@
 popd</userinput></screen>
 
-    <para>Install the package as the <systemitem
-    class="username">root</systemitem> user:</para>
+    <para>
+      Install the package as the <systemitem
+      class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>make install &amp;&amp;
@@ -158,15 +190,23 @@
     <title>Command Explanations</title>
 
-    <para><option>--disable-documentation</option>: This option
-    is needed if the recommended dependencies are not installed.</para>
-
-    <para><command>mv tests/{cli,convert,misc,fuzz}-tests/ ...</command>: Disables
-    tests that fail and prevent tests from completing.</para>
-
-    <para><command>ln -s ... /usr/lib/libbtrfs.so</command>: Creates a 
-    symbolic link in the directory where it is expected.</para>
-
-    <para><command>rm /lib/libbtrfs.{a,so}</command>: Removes unneeded
-    library entries.</para>
+    <para>
+      <option>--disable-documentation</option>: This option
+      is needed if the recommended dependencies are not installed.
+    </para>
+
+    <para>
+      <command>mv tests/{cli,convert,misc,fuzz}-tests/ ...</command>: Disables
+      tests that fail and prevent tests from completing.
+    </para>
+
+    <para>
+      <command>ln -s ... /usr/lib/libbtrfs.so</command>: Creates a 
+      symbolic link in the directory where it is expected.
+    </para>
+
+    <para>
+      <command>rm /lib/libbtrfs.{a,so}</command>: Removes unneeded
+      library entries.
+    </para>
 
   </sect2>
@@ -295,5 +335,7 @@
         <term><command>mkfs.btrfs</command></term>
         <listitem>
-          <para>creates a btrfs file system.</para>
+          <para>
+            creates a btrfs file system.
+          </para>
           <indexterm zone="btrfs-progs mkfs.btrfs">
             <primary sortas="b-mkfs.btrfs">mkfs.btrfs</primary>
Index: postlfs/filesystems/dosfstools.xml
===================================================================
--- postlfs/filesystems/dosfstools.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/dosfstools.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -30,6 +30,8 @@
     <title>Introduction to dosfstools</title>
 
-    <para>The <application>dosfstools</application> package contains various
-    utilities for use with the FAT family of file systems.</para>
+    <para>
+      The <application>dosfstools</application> package contains various
+      utilities for use with the FAT family of file systems.
+    </para>
 
     &lfs91_checked;
@@ -38,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&dosfstools-download-http;"/></para>
+        <para>
+          Download (HTTP): <ulink url="&dosfstools-download-http;"/>
+        </para>
       </listitem>
       <listitem>
-        <para>Download (FTP): <ulink url="&dosfstools-download-ftp;"/></para>
+        <para>
+          Download (FTP): <ulink url="&dosfstools-download-ftp;"/>
+        </para>
       </listitem>
       <listitem>
-        <para>Download MD5 sum: &dosfstools-md5sum;</para>
+        <para>
+          Download MD5 sum: &dosfstools-md5sum;
+        </para>
       </listitem>
       <listitem>
-        <para>Download size: &dosfstools-size;</para>
+        <para>
+          Download size: &dosfstools-size;
+        </para>
       </listitem>
       <listitem>
-        <para>Estimated disk space required: &dosfstools-buildsize;</para>
+        <para>
+          Estimated disk space required: &dosfstools-buildsize;
+        </para>
       </listitem>
       <listitem>
-        <para>Estimated build time: &dosfstools-time;</para>
+        <para>
+          Estimated build time: &dosfstools-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -65,6 +79,8 @@
     <title>Kernel Configuration</title>
 
-    <para>Enable the following option in the kernel configuration
-    and recompile the kernel:</para>
+    <para>
+      Enable the following option in the kernel configuration
+      and recompile the kernel:
+    </para>
 
 <screen><literal>File systems ---&gt;
@@ -82,6 +98,8 @@
     <title>Installation of dosfstools</title>
 
-    <para>Install <application>dosfstools</application> by running the
-    following commands:</para>
+    <para>
+      Install <application>dosfstools</application> by running the
+      following commands:
+    </para>
 
 <screen><userinput>./configure --prefix=/               \
@@ -91,8 +109,11 @@
 make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
+    <para>
+      This package does not come with a test suite.
+    </para>
 
-    <para>Now, as the <systemitem class="username">root</systemitem>
-    user:</para>
+    <para>
+      Now, as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>make install</userinput></screen>
@@ -135,6 +156,7 @@
         <term><command>fatlabel</command></term>
         <listitem>
-          <para>set or get a MS-DOS filesystem label from a given
-          device</para>
+          <para>
+            sets or gets a MS-DOS filesystem label from a given device.
+          </para>
           <indexterm zone="dosfstools fatlabel">
             <primary sortas="b-fatlabel">fatlabel</primary>
@@ -146,5 +168,7 @@
         <term><command>fsck.fat</command></term>
         <listitem>
-          <para>check and repair MS-DOS filesystems</para>
+          <para>
+            checks and repairs MS-DOS filesystems.
+          </para>
           <indexterm zone="dosfstools fsckfat">
             <primary sortas="b-fsckfat">fsck.fat</primary>
@@ -156,5 +180,7 @@
         <term><command>mkfs.fat</command></term>
         <listitem>
-          <para>create an MS-DOS filesystem under Linux</para>
+          <para>
+            creates an MS-DOS filesystem under Linux.
+          </para>
           <indexterm zone="dosfstools mkfsfat">
             <primary sortas="b-mkfsfat">mkfs.fat</primary>
Index: postlfs/filesystems/filesystems.xml
===================================================================
--- postlfs/filesystems/filesystems.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/filesystems.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -16,10 +16,12 @@
   <title>File Systems and Disk Management</title>
 
-  <para>Journaling file systems reduce the time needed to recover a file system
-  that was not unmounted properly.  While this can be extremely important in
-  reducing downtime for servers, it has also become popular for desktop
-  environments.  This chapter contains other journaling file systems you can
-  use instead of the default LFS extended file system (ext2/3/4). It also
-  provides introductory material on managing disk arrays.</para>
+  <para>
+    Journaling file systems reduce the time needed to recover a file system
+    that was not unmounted properly.  While this can be extremely important in
+    reducing downtime for servers, it has also become popular for desktop
+    environments.  This chapter contains other journaling file systems you can
+    use instead of the default LFS extended file system (ext2/3/4). It also
+    provides introductory material on managing disk arrays.
+  </para>
 
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="initramfs.xml"/>
Index: postlfs/filesystems/gptfdisk.xml
===================================================================
--- postlfs/filesystems/gptfdisk.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/gptfdisk.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -44,20 +44,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&gptfdisk-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&gptfdisk-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &gptfdisk-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &gptfdisk-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &gptfdisk-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &gptfdisk-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&gptfdisk-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&gptfdisk-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &gptfdisk-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &gptfdisk-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &gptfdisk-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &gptfdisk-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -66,6 +78,8 @@
     <itemizedlist spacing='compact'>
       <listitem>
-        <para>Recommended patch: <ulink
-          url="&patch-root;/gptfdisk-&gptfdisk-version;-convenience-1.patch"/></para>
+        <para>
+          Recommended patch: <ulink url=
+            "&patch-root;/gptfdisk-&gptfdisk-version;-convenience-1.patch"/>
+        </para>
       </listitem>
     </itemizedlist>
@@ -148,6 +162,7 @@
         <term><command>cgdisk</command></term>
         <listitem>
-          <para>is an ncurses-based tool for
-          manipulating GPT partitions.</para>
+          <para>
+            is an ncurses-based tool for manipulating GPT partitions.
+          </para>
           <indexterm zone="gptfdisk cgdisk">
             <primary sortas="b-cgdisk">cgdisk</primary>
@@ -159,6 +174,7 @@
         <term><command>gdisk</command></term>
         <listitem>
-          <para>is an interactive text-mode tool
-          for manipulating GPT partitions.</para>
+          <para>
+            is an interactive text-mode tool for manipulating GPT partitions.
+          </para>
           <indexterm zone="gptfdisk gdisk">
             <primary sortas="b-gdisk">gdisk</primary>
@@ -170,5 +186,7 @@
         <term><command>fixparts</command></term>
         <listitem>
-          <para>repairs mis-formatted MBR based disk partitions.</para>
+          <para>
+            repairs mis-formatted MBR based disk partitions.
+          </para>
           <indexterm zone="gptfdisk fixparts">
             <primary sortas="b-fixparts">fixparts</primary>
@@ -180,6 +198,8 @@
         <term><command>sgdisk</command></term>
         <listitem>
-          <para>is a partition manipulation program for
-          GPT partitions similar to <command>sfdisk</command>.</para>
+          <para>
+            is a partition manipulation program for
+            GPT partitions similar to <command>sfdisk</command>.
+          </para>
           <indexterm zone="gptfdisk sgdisk">
             <primary sortas="b-sgdisk">sgdisk</primary>
Index: postlfs/filesystems/initramfs.xml
===================================================================
--- postlfs/filesystems/initramfs.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/initramfs.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -16,41 +16,54 @@
   <title>About initramfs</title>
 
-  <para>The only purpose of an initramfs is to mount the root filesystem.  The
-  initramfs is a complete set of directories that you would find on a normal
-  root filesystem.  It is bundled into a single cpio archive and compressed
-  with one of several compression algorithms.</para>
-
-  <para>At boot time, the boot loader loads the kernel and the initramfs image
-  into memory and starts the kernel.  The kernel checks for the presence of the
-  initramfs and, if found, mounts it as / and runs /init. The init program is
-  typically a shell script.  Note that the boot process takes longer, possibly
-  significantly longer, if an initramfs is used.</para>
-
-  <para>For most distributions, kernel modules are the biggest reason to have an
-  initramfs.  In a general distribution, there are many unknowns such as file
-  system types and disk layouts.  In a way, this is the opposite of LFS where
-  the system capabilities and layout are known and a custom kernel is normally
-  built.  In this situation, an initramfs is rarely needed.</para>
-
-  <para>There are only four primary reasons to have an initramfs in the LFS
-  environment: loading the rootfs from a network, loading it from an LVM
-  logical volume, having an encrypted rootfs where a password is required, or
-  for the convenience of specifying the rootfs as a LABEL or UUID.  Anything
-  else usually means that the kernel was not configured properly.</para>
+  <para>
+    The only purpose of an initramfs is to mount the root filesystem.  The
+    initramfs is a complete set of directories that you would find on a normal
+    root filesystem.  It is bundled into a single cpio archive and compressed
+    with one of several compression algorithms.
+  </para>
+
+  <para>
+    At boot time, the boot loader loads the kernel and the initramfs image
+    into memory and starts the kernel.  The kernel checks for the presence
+    of the initramfs and, if found, mounts it as / and runs /init. The init
+    program is typically a shell script.  Note that the boot process takes
+    longer, possibly significantly longer, if an initramfs is used.
+  </para>
+
+  <para>
+    For most distributions, kernel modules are the biggest reason to have
+    an initramfs.  In a general distribution, there are many unknowns such
+    as file system types and disk layouts.  In a way, this is the opposite
+    of LFS where the system capabilities and layout are known and a custom
+    kernel is normally built.  In this situation, an initramfs is rarely
+    needed.
+  </para>
+
+  <para>
+    There are only four primary reasons to have an initramfs in the LFS
+    environment: loading the rootfs from a network, loading it from an LVM
+    logical volume, having an encrypted rootfs where a password is required, or
+    for the convenience of specifying the rootfs as a LABEL or UUID.  Anything
+    else usually means that the kernel was not configured properly.
+  </para>
 
   <sect2 id="initramfs-build">
     <title>Building an initramfs</title>
 
-    <para>If you do decide to build an initramfs, the following scripts
-    will provide a basis to do it.  The scripts will allow specifying a
-    rootfs via partition UUID or partition LABEL or a rootfs on an
-    LVM logical volume.  They do not support an encrypted root file system
-    or mounting the rootfs over a network card.  For a more complete
-    capability see <ulink url="http://www.linuxfromscratch.org/hints/read.html">
-    the LFS Hints</ulink> or <ulink url="http://fedoraproject.org/wiki/Dracut">
-    dracut</ulink>.</para>
-
-    <para>To install these scripts, run the following commands as the
-    <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      If you do decide to build an initramfs, the following scripts will
+      provide a basis to do it.  The scripts will allow specifying a rootfs
+      via partition UUID or partition LABEL or a rootfs on an LVM logical
+      volume.  They do not support an encrypted root file system or mounting
+      the rootfs over a network card.  For a more complete capability see
+      <ulink url="http://www.linuxfromscratch.org/hints/read.html"> the LFS
+      Hints</ulink> or <ulink
+      url="http://fedoraproject.org/wiki/Dracut">dracut</ulink>.
+    </para>
+
+    <para>
+      To install these scripts, run the following commands as the
+      <systemitem class="username">root</systemitem> user:
+    </para>
 
     <screen role="root"><userinput>cat &gt; /sbin/mkinitramfs &lt;&lt; "EOF"
@@ -434,29 +447,39 @@
 
 
-    <para>To build an initramfs, run the following as the  <systemitem
-    class="username">root</systemitem> user:</para>
+    <para>
+      To build an initramfs, run the following as the  <systemitem
+      class="username">root</systemitem> user:
+    </para>
 
     <screen role="nodump"><userinput>mkinitramfs [KERNEL VERSION]</userinput></screen>
 
-    <para>The optional argument is the directory where the appropriate kernel
-    modules are located. This must be a subdirectory of <filename
-    class='directory'> /lib/modules</filename>.  If no modules are specified,
-    then the initramfs is named <emphasis>initrd.img-no-kmods</emphasis>.  If a
-    kernel version is specified, the initrd is named
-    <emphasis>initrd.img-$KERNEL_VERSION</emphasis> and is only appropriate for
-    the specific kernel specified. The output file will be placed in the
-    current directory.</para>
-
-    <para>If early loading of microcode is needed (see <xref
-    linkend="cpu-microcode"/>), you can install the appropriate blob or
-    container in <filename class="directory">/lib/firmware</filename>.
-    It will be automatically added to the initrd when running
-    <command>mkinitramfs</command>.</para>
-
-    <para>After generating the initrd, copy it to the <filename
-    class='directory'>/boot</filename> directory.</para>
-
-    <para>Now edit <filename>/boot/grub/grub.cfg</filename> and add a new
-    menuentry.  Below are several examples.</para>
+    <para>
+      The optional argument is the directory where the appropriate kernel
+      modules are located. This must be a subdirectory of <filename
+      class='directory'> /lib/modules</filename>.  If no modules are specified,
+      then the initramfs is named <emphasis>initrd.img-no-kmods</emphasis>.
+      If a kernel version is specified, the initrd is named
+      <emphasis>initrd.img-$KERNEL_VERSION</emphasis> and is only appropriate
+      for the specific kernel specified. The output file will be placed in the
+      current directory.
+    </para>
+
+    <para>
+      If early loading of microcode is needed (see <xref
+      linkend="cpu-microcode"/>), you can install the appropriate blob or
+      container in <filename class="directory">/lib/firmware</filename>.
+      It will be automatically added to the initrd when running
+      <command>mkinitramfs</command>.
+    </para>
+
+    <para>
+      After generating the initrd, copy it to the <filename
+      class='directory'>/boot</filename> directory.
+    </para>
+
+    <para>
+      Now edit <filename>/boot/grub/grub.cfg</filename> and add a new
+      menuentry.  Below are several examples.
+    </para>
 
      <screen role="nodump"><userinput># Generic initramfs and root fs identified by UUID
@@ -481,5 +504,7 @@
 }</userinput></screen>
 
-    <para>Finally, reboot the system and select the desired system.</para>
+    <para>
+      Finally, reboot the system and select the desired system.
+    </para>
 
   </sect2>
Index: postlfs/filesystems/jfs.xml
===================================================================
--- postlfs/filesystems/jfs.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/jfs.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -30,6 +30,8 @@
     <title>Introduction to jfsutils</title>
 
-    <para>The <application>jfsutils</application> package contains administration
-    and debugging tools for the jfs file system.</para>
+    <para>
+      The <application>jfsutils</application> package contains administration
+      and debugging tools for the jfs file system.
+    </para>
 
     &lfs91_checked;
@@ -38,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&jfsutils-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&jfsutils-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &jfsutils-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &jfsutils-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &jfsutils-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &jfsutils-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&jfsutils-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&jfsutils-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &jfsutils-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &jfsutils-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &jfsutils-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &jfsutils-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -65,6 +79,8 @@
     <title>Kernel Configuration</title>
 
-    <para>Enable the following option in the kernel configuration
-    and recompile the kernel:</para>
+    <para>
+      Enable the following option in the kernel configuration
+      and recompile the kernel:
+    </para>
 
 <screen><literal>File systems  ---&gt;
@@ -80,6 +96,8 @@
     <title>Installation of jfsutils</title>
 
-    <para>Install <application>jfsutils</application> by running the following
-    commands:</para>
+    <para>
+      Install <application>jfsutils</application> by running the following
+      commands:
+    </para>
 
 <screen><userinput>sed -i "/unistd.h/a#include &lt;sys/types.h&gt;"    fscklog/extract.c &amp;&amp;
@@ -89,7 +107,11 @@
 make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
-
-    <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      This package does not come with a test suite.
+    </para>
+
+    <para>
+      Now, as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>make install</userinput></screen>
@@ -130,6 +152,8 @@
         <term><command>fsck.jfs</command></term>
         <listitem>
-          <para>is used to replay the JFS transaction log, check a
-          JFS formatted device for errors, and fix any errors found.</para>
+          <para>
+            is used to replay the JFS transaction log, check a
+            JFS formatted device for errors, and fix any errors found.
+          </para>
           <indexterm zone="jfsutils fsck.jfs">
             <primary sortas="b-fsck.jfs">fsck.jfs</primary>
@@ -141,5 +165,7 @@
         <term><command>jfs_fsck</command></term>
         <listitem>
-          <para>is a hard link to fsck.jfs.</para>
+          <para>
+            is a hard link to fsck.jfs.
+          </para>
           <indexterm zone="jfsutils jfs_fsck">
             <primary sortas="b-jfs_fsck">jfs_fsck</primary>
@@ -151,5 +177,7 @@
         <term><command>mkfs.jfs</command></term>
         <listitem>
-          <para>constructs an JFS file system.</para>
+          <para>
+            constructs an JFS file system.
+          </para>
           <indexterm zone="jfsutils mkfs.jfs">
             <primary sortas="b-mkfs.jfs">mkfs.jfs</primary>
@@ -161,5 +189,7 @@
         <term><command>jfs_mkfs</command></term>
         <listitem>
-          <para>is a hard link to mkfs.jfs.</para>
+          <para>
+            is a hard link to mkfs.jfs.
+          </para>
           <indexterm zone="jfsutils jfs_mkfs">
             <primary sortas="b-jfs_mkfs">jfs_mkfs</primary>
@@ -171,6 +201,8 @@
         <term><command>jfs_debugfs</command></term>
         <listitem>
-          <para>is a program which can be used to perform various low-level
-          actions on a JFS formatted device.</para>
+          <para>
+            is a program which can be used to perform various low-level
+            actions on a JFS formatted device.
+          </para>
           <indexterm zone="jfsutils jfs_debugfs">
             <primary sortas="b-jfs_debugfs">jfs_debugfs</primary>
@@ -182,6 +214,8 @@
         <term><command>jfs_fscklog</command></term>
         <listitem>
-          <para>extracts a JFS fsck service log into a file and/or formats and
-          displays the extracted file.</para>
+          <para>
+            extracts a JFS fsck service log into a file and/or formats and
+            displays the extracted file.
+          </para>
           <indexterm zone="jfsutils jfs_fscklog">
             <primary sortas="b-jfs_fscklog">jfs_fscklog</primary>
@@ -193,6 +227,8 @@
         <term><command>jfs_logdump</command></term>
         <listitem>
-          <para>dumps the contents of the journal log from the specified
-          JFS formatted device into output file ./jfslog.dmp.</para>
+          <para>
+            dumps the contents of the journal log from the specified
+            JFS formatted device into output file ./jfslog.dmp.
+          </para>
           <indexterm zone="jfsutils jfs_logdump">
             <primary sortas="b-jfs_logdump">jfs_logdump</primary>
@@ -204,5 +240,7 @@
         <term><command>jfs_tune</command></term>
         <listitem>
-          <para>adjusts tunable file system parameters on JFS file systems.</para>
+          <para>
+            adjusts tunable file system parameters on JFS file systems.
+          </para>
           <indexterm zone="jfsutils jfs_tune">
             <primary sortas="b-jfs_tune">jfs_tune</primary>
Index: postlfs/filesystems/mdadm.xml
===================================================================
--- postlfs/filesystems/mdadm.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/mdadm.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -30,6 +30,8 @@
     <title>Introduction to mdadm</title>
 
-    <para>The <application>mdadm</application> package contains administration
-    tools for software RAID.</para>
+    <para>
+      The <application>mdadm</application> package contains administration
+      tools for software RAID.
+    </para>
 
     &lfs91_checked;
@@ -38,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&mdadm-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&mdadm-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &mdadm-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &mdadm-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &mdadm-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &mdadm-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&mdadm-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&mdadm-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &mdadm-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &mdadm-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &mdadm-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &mdadm-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -79,7 +93,9 @@
     <title>Kernel Configuration</title>
 
-    <para>Enable the following options in the kernel configuration
-    and recompile the kernel, if necessary.  Only the RAID types desired
-    are required.</para>
+    <para>
+      Enable the following options in the kernel configuration
+      and recompile the kernel, if necessary.  Only the RAID types desired
+      are required.
+    </para>
 
 <screen><literal>Device Drivers ---&gt;
@@ -102,26 +118,40 @@
     <title>Installation of mdadm</title>
 
-    <para>Fix a build error introduced by gcc-7.1:</para>
+    <para>
+      Fix a build error introduced by gcc-7.1:
+    </para>
 
 <screen><userinput>sed 's@-Werror@@' -i Makefile</userinput></screen>
 
-    <para>Build <application>mdadm</application> by running the following
-    command:</para>
+    <para>
+      Build <application>mdadm</application> by running the following
+      command:
+    </para>
 
 <screen><userinput>make</userinput></screen>
 
-    <para>If you wish to run the tests, ensure that your kernel supports
-    RAID and that a version of mdadm is not already running.  As many as 9 out
-    of 124 tests may fail.</para>
-
-    <caution><para>The tests edit values in /proc and run tests on software raid devices.
-     They shouldn't be run on systems with active software RAID devices.</para></caution>
-
-    <para>Run the tests as the <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      If you wish to run the tests, ensure that your kernel supports RAID
+      and that a version of mdadm is not already running.  As many as 9 out
+      of 124 tests may fail.
+    </para>
+
+    <caution>
+      <para>
+        The tests edit values in /proc and run tests on software raid devices.
+        They shouldn't be run on systems with active software RAID devices.
+      </para>
+    </caution>
+
+    <para>
+      Run the tests as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"
         remap="test"><userinput>./test --keep-going --logdir=test-logs --save-logs</userinput></screen>
 
-    <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      Now, as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>make install</userinput></screen>
@@ -186,5 +216,7 @@
         <term><command>mdadm</command></term>
         <listitem>
-          <para>manages MD devices aka Linux Software RAID.</para>
+          <para>
+            manages MD devices aka Linux Software RAID.
+          </para>
           <indexterm zone="mdadm mdadm-prog">
             <primary sortas="b-mdadm-prog">mdadm</primary>
@@ -196,5 +228,7 @@
         <term><command>mdmon</command></term>
         <listitem>
-          <para>monitors MD external metadata arrays.</para>
+          <para>
+            monitors MD external metadata arrays.
+          </para>
           <indexterm zone="mdadm mdmon">
             <primary sortas="b-mdmon">mdmon</primary>
@@ -206,6 +240,8 @@
         <term><command>mdassemble</command></term>
         <listitem>
-          <para>is a tiny program that can be used to assemble MD devices
-          inside an initial ramdisk (initrd) or initramfs.</para>
+          <para>
+            is a tiny program that can be used to assemble MD devices
+            inside an initial ramdisk (initrd) or initramfs.
+          </para>
           <indexterm zone="mdadm mdassemble">
             <primary sortas="b-mdassemble">mdassemble</primary>
Index: postlfs/filesystems/parted.xml
===================================================================
--- postlfs/filesystems/parted.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/parted.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -40,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&parted-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&parted-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &parted-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &parted-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &parted-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &parted-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&parted-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&parted-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &parted-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &parted-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &parted-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &parted-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -63,6 +75,6 @@
         <listitem>
           <para>
-             Optional, to fix build without device mapper support:
-            <ulink url="&patch-root;/parted-&parted-version;-devmapper-1.patch"/>
+             Optional, to fix build without device mapper support: <ulink
+               url="&patch-root;/parted-&parted-version;-devmapper-1.patch"/>
           </para>
         </listitem>
@@ -111,6 +123,8 @@
 makeinfo --plaintext -o doc/parted.txt doc/parted.texi</userinput></screen>
 
-    <para>If you have <xref linkend="texlive"/> installed and wish to create
-    PDF and Postcript documentation issue the following commands:</para>
+    <para>
+      If you have <xref linkend="texlive"/> installed and wish to create
+      PDF and Postcript documentation issue the following commands:
+    </para>
 
 <screen remap="doc"><userinput>texi2pdf             -o doc/parted.pdf doc/parted.texi &amp;&amp;
@@ -118,6 +132,8 @@
 dvips                -o doc/parted.ps  doc/parted.dvi</userinput></screen>
 
-    <para>If you wish to run the test suite, first remove a couple of tests
-    that are known to fail in a BLFS environment:</para>
+    <para>
+      If you wish to run the test suite, first remove a couple of tests
+      that are known to fail in a BLFS environment:
+    </para>
  <!-- One of these is due to a C locale, and another is a problem in LVM. -->
 <screen remap="test"><userinput>sed -i '/t0251-gpt-unicode.sh/d' tests/Makefile &amp;&amp;
@@ -150,7 +166,9 @@
                     /usr/share/doc/parted-&parted-version;</userinput></screen>
 
-    <para>Install the optional PDF and Postscript documentation by issuing
-    the following command as the <systemitem class="username">root</systemitem>
-    user:</para>
+    <para>
+      Install the optional PDF and Postscript documentation by issuing the
+      following command as the <systemitem class="username">root</systemitem>
+      user:
+    </para>
 
 <screen role="root"
@@ -202,5 +220,7 @@
         <term><command>parted</command></term>
         <listitem>
-          <para>is a partition manipulation program.</para>
+          <para>
+            is a partition manipulation program.
+          </para>
           <indexterm zone="parted parted-prog">
             <primary sortas="b-parted">parted</primary>
@@ -212,5 +232,7 @@
         <term><command>partprobe</command></term>
         <listitem>
-          <para>informs the OS of partition table changes.</para>
+          <para>
+            informs the OS of partition table changes.
+          </para>
           <indexterm zone="parted partprobe">
             <primary sortas="b-partprobe">partprobe</primary>
Index: postlfs/filesystems/reiser.xml
===================================================================
--- postlfs/filesystems/reiser.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/reiser.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -30,6 +30,8 @@
     <title>Introduction to reiserfsprogs</title>
 
-    <para>The <application>reiserfsprogs</application> package contains various
-    utilities for use with the Reiser file system.</para>
+    <para>
+      The <application>reiserfsprogs</application> package contains various
+      utilities for use with the Reiser file system.
+    </para>
 
     &lfs91_checked;
@@ -38,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&reiser-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&reiser-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &reiser-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &reiser-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &reiser-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &reiser-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&reiser-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&reiser-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &reiser-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &reiser-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &reiser-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &reiser-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -65,6 +79,8 @@
     <title>Kernel Configuration</title>
 
-    <para>Enable the following option in the kernel configuration
-    and recompile the kernel:</para>
+    <para>
+      Enable the following option in the kernel configuration
+      and recompile the kernel:
+    </para>
 
 <screen><literal>File systems ---&gt;
@@ -80,6 +96,8 @@
     <title>Installation of reiserfsprogs</title>
 
-    <para>Install <application>reiserfsprogs</application> by running the following
-    commands:</para>
+    <para>
+      Install <application>reiserfsprogs</application> by running the following
+      commands:
+    </para>
 
 <screen><userinput>sed -i '/parse_time.h/i #define _GNU_SOURCE' lib/parse_time.c &amp;&amp;
@@ -90,7 +108,11 @@
 make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
-
-    <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      This package does not come with a test suite.
+    </para>
+
+    <para>
+      Now, as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>make install</userinput></screen>
@@ -138,9 +160,11 @@
         <term><command>debugreiserfs</command></term>
         <listitem>
-          <para>can sometimes help to solve problems with
-          <application>ReiserFS</application> file systems. If it is called
-          without options, it prints the super block of any
-          <application>ReiserFS</application> file
-          system found on the device.</para>
+          <para>
+            can sometimes help to solve problems with
+            <application>ReiserFS</application> file systems. If it is called
+            without options, it prints the super block of any
+            <application>ReiserFS</application> file
+            system found on the device.
+          </para>
           <indexterm zone="reiserfs debugreiserfs">
             <primary sortas="b-debugreiserfs">debugreiserfs</primary>
@@ -152,5 +176,7 @@
         <term><command>mkreiserfs</command></term>
         <listitem>
-          <para>creates a <application>ReiserFS</application> file system.</para>
+          <para>
+            creates a <application>ReiserFS</application> file system.
+          </para>
           <indexterm zone="reiserfs mkreiserfs">
             <primary sortas="b-mkreiserfs">mkreiserfs</primary>
@@ -162,6 +188,8 @@
         <term><command>reiserfsck</command></term>
         <listitem>
-          <para>is used to check or repair a
-          <application>ReiserFS</application> file system.</para>
+          <para>
+            is used to check or repair a
+            <application>ReiserFS</application> file system.
+          </para>
           <indexterm zone="reiserfs reiserfsck">
             <primary sortas="b-reiserfsck">reiserfsck</primary>
@@ -173,7 +201,9 @@
         <term><command>reiserfstune</command></term>
         <listitem>
-          <para>is used for tuning the <application>ReiserFS</application>
-          journal. <emphasis>WARNING</emphasis>: Don't use this utility without
-          first reading the man page thoroughly.</para>
+          <para>
+            is used for tuning the <application>ReiserFS</application>
+            journal. <emphasis>WARNING</emphasis>: Don't use this utility
+            without first reading the man page thoroughly.
+          </para>
           <indexterm zone="reiserfs reiserfstune">
             <primary sortas="b-reiserfstune">reiserfstune</primary>
@@ -185,6 +215,8 @@
         <term><command>resize_reiserfs</command></term>
         <listitem>
-          <para>is used to resize an unmounted
-          <application>ReiserFS</application> file system.</para>
+          <para>
+            is used to resize an unmounted
+            <application>ReiserFS</application> file system.
+          </para>
           <indexterm zone="reiserfs resize_reiserfs">
             <primary sortas="b-resize_reiserfs">resize_reiserfs</primary>
Index: postlfs/filesystems/smartmontools.xml
===================================================================
--- postlfs/filesystems/smartmontools.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/smartmontools.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -42,20 +42,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&smartmontools-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&smartmontools-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &smartmontools-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &smartmontools-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &smartmontools-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &smartmontools-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&smartmontools-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&smartmontools-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &smartmontools-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &smartmontools-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &smartmontools-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &smartmontools-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -97,5 +109,7 @@
 make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
+    <para>
+      This package does not come with a test suite.
+    </para>
 
     <para>
@@ -195,5 +209,7 @@
         <term><command>smartctl</command></term>
         <listitem>
-          <para>is the control and monitor utility for SMART Disks.</para>
+          <para>
+            is the control and monitor utility for SMART Disks.
+          </para>
           <indexterm zone="smartmontools smartctl">
             <primary sortas="b-smartctl">smartctl</primary>
@@ -205,5 +221,7 @@
         <term><command>smartd</command></term>
         <listitem>
-          <para>is the SMART disk monitoring daemon.</para>
+          <para>
+            is the SMART disk monitoring daemon.
+          </para>
           <indexterm zone="smartmontools smartd">
             <primary sortas="b-smartd">smartd</primary>
@@ -215,5 +233,7 @@
         <term><command>update-smart-drivedb</command></term>
         <listitem>
-          <para>is the update tool for the smartmontools drive database.</para>
+          <para>
+            is the update tool for the smartmontools drive database.
+          </para>
           <indexterm zone="smartmontools update-smart-drivedb">
             <primary sortas="b-update-smart-drivedb">update-smart-drivedb</primary>
Index: postlfs/filesystems/xfsprogs.xml
===================================================================
--- postlfs/filesystems/xfsprogs.xml	(revision 78d121b0d160eaf571690247ba91d95c3c1da526)
+++ postlfs/filesystems/xfsprogs.xml	(revision 29244b73b3857d77173c51d4cc661c1d49b975ba)
@@ -30,6 +30,8 @@
     <title>Introduction to xfsprogs</title>
 
-    <para>The <application>xfsprogs</application> package contains
-    administration and debugging tools for the XFS file system.</para>
+    <para>
+      The <application>xfsprogs</application> package contains
+      administration and debugging tools for the XFS file system.
+    </para>
 
     &lfs91_checked;
@@ -38,20 +40,32 @@
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Download (HTTP): <ulink url="&xfsprogs-download-http;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download (FTP): <ulink url="&xfsprogs-download-ftp;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum: &xfsprogs-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para>Download size: &xfsprogs-size;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated disk space required: &xfsprogs-buildsize;</para>
-      </listitem>
-      <listitem>
-        <para>Estimated build time: &xfsprogs-time;</para>
+        <para>
+          Download (HTTP): <ulink url="&xfsprogs-download-http;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download (FTP): <ulink url="&xfsprogs-download-ftp;"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download MD5 sum: &xfsprogs-md5sum;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Download size: &xfsprogs-size;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated disk space required: &xfsprogs-buildsize;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Estimated build time: &xfsprogs-time;
+        </para>
       </listitem>
     </itemizedlist>
@@ -65,6 +79,8 @@
     <title>Kernel Configuration</title>
 
-    <para>Enable the following options in the kernel configuration
-    and recompile the kernel:</para>
+    <para>
+      Enable the following options in the kernel configuration
+      and recompile the kernel:
+    </para>
 
 <screen><literal>File systems ---&gt;
@@ -80,6 +96,8 @@
     <title>Installation of xfsprogs</title>
 
-    <para>Install <application>xfsprogs</application> by running the following
-    commands:</para>
+    <para>
+      Install <application>xfsprogs</application> by running the following
+      commands:
+    </para>
 
  <screen><userinput>make DEBUG=-DNDEBUG     \
@@ -88,7 +106,11 @@
      LOCAL_CONFIGURE_OPTIONS="--enable-readline"</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
-
-    <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      This package does not come with a test suite.
+    </para>
+
+    <para>
+      Now, as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>make PKG_DOC_DIR=/usr/share/doc/xfsprogs-&xfsprogs-version; install     &amp;&amp;
@@ -105,20 +127,28 @@
     <title>Command Explanations</title>
 
-    <para><command>make DEBUG=-DNDEBUG</command>: Turns off debugging
-    symbols.</para>
-
-    <para><parameter>INSTALL_USER=root INSTALL_GROUP=root</parameter>: This
-    sets the owner and group of the installed files.</para>
-
-    <para><parameter>LOCAL_CONFIGURE_OPTIONS="..."</parameter>: This passes
-    extra configuration options to the <filename>configure</filename> script.
-    The example <parameter>--enable-readline</parameter> parameter
-    enables linking the XFS programs with the
-    <filename class="libraryfile">libreadline.so</filename> library, in order
-    to allow editing interactive commands.</para>
-
-    <para><option>OPTIMIZER="..."</option>: Adding this parameter to
-    the end of the <command>make</command> command overrides the
-    default optimization settings.</para>
+    <para>
+      <command>make DEBUG=-DNDEBUG</command>: Turns off debugging
+      symbols.
+    </para>
+
+    <para>
+      <parameter>INSTALL_USER=root INSTALL_GROUP=root</parameter>: This
+      sets the owner and group of the installed files.
+    </para>
+
+    <para>
+      <parameter>LOCAL_CONFIGURE_OPTIONS="..."</parameter>: This passes
+      extra configuration options to the <filename>configure</filename> script.
+      The example <parameter>--enable-readline</parameter> parameter
+      enables linking the XFS programs with the
+      <filename class="libraryfile">libreadline.so</filename> library, in order
+      to allow editing interactive commands.
+    </para>
+
+    <para>
+      <option>OPTIMIZER="..."</option>: Adding this parameter to
+      the end of the <command>make</command> command overrides the
+      default optimization settings.
+    </para>
 
   </sect2>
@@ -150,6 +180,8 @@
         <term><command>fsck.xfs</command></term>
         <listitem>
-          <para>simply exits with a zero status, since XFS
-          partitions are checked at mount time.</para>
+          <para>
+            simply exits with a zero status, since XFS
+            partitions are checked at mount time.
+          </para>
           <indexterm zone="xfsprogs fsck.xfs">
             <primary sortas="b-fsck.xfs">fsck.xfs</primary>
@@ -161,5 +193,7 @@
         <term><command>mkfs.xfs</command></term>
         <listitem>
-          <para>constructs an XFS file system.</para>
+          <para>
+            constructs an XFS file system.
+          </para>
           <indexterm zone="xfsprogs mkfs.xfs">
             <primary sortas="b-mkfs.xfs">mkfs.xfs</primary>
@@ -171,5 +205,7 @@
         <term><command>xfs_admin</command></term>
         <listitem>
-          <para>changes the parameters of an XFS file system.</para>
+          <para>
+            changes the parameters of an XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_admin">
             <primary sortas="b-xfs_admin">xfs_admin</primary>
@@ -181,5 +217,7 @@
         <term><command>xfs_bmap</command></term>
         <listitem>
-          <para>prints block mapping for an XFS file.</para>
+          <para>
+            prints block mapping for an XFS file.
+          </para>
           <indexterm zone="xfsprogs xfs_bmap">
             <primary sortas="b-xfs_bmap">xfs_bmap</primary>
@@ -191,6 +229,8 @@
         <term><command>xfs_copy</command></term>
         <listitem>
-          <para>copies the contents of an XFS file system
-          to one or more targets in parallel.</para>
+          <para>
+            copies the contents of an XFS file system
+            to one or more targets in parallel.
+          </para>
           <indexterm zone="xfsprogs xfs_copy">
             <primary sortas="b-xfs_copy">xfs_copy</primary>
@@ -202,7 +242,9 @@
         <term><command>xfs_estimate</command></term>
         <listitem>
-          <para>for each directory argument, estimates the space that directory
-          would take if it were copied to an XFS filesystem
-          (does not cross mount points).</para>
+          <para>
+            for each directory argument, estimates the space that directory
+            would take if it were copied to an XFS filesystem
+            (does not cross mount points).
+          </para>
           <indexterm zone="xfsprogs xfs_estimate">
             <primary sortas="b-xfs_estimate">xfs_estimate</primary>
@@ -214,5 +256,7 @@
         <term><command>xfs_db</command></term>
         <listitem>
-          <para>is used to debug an XFS file system.</para>
+          <para>
+            is used to debug an XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_db">
             <primary sortas="b-xfs_db">xfs_db</primary>
@@ -224,5 +268,7 @@
         <term><command>xfs_freeze</command></term>
         <listitem>
-          <para>suspends access to an XFS file system.</para>
+          <para>
+            suspends access to an XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_freeze">
             <primary sortas="b-xfs_freeze">xfs_freeze</primary>
@@ -234,8 +280,10 @@
         <term><command>xfs_fsr</command></term>
         <listitem>
-          <para>applicable only to XFS filesystems, improves the organization
-          of mounted filesystems, the reorganization algorithm operates on one
-          file at a time, compacting or othewise  improving the layout of the
-          file extents (contiguous blocks of file data).</para>
+          <para>
+            applicable only to XFS filesystems, improves the organization of
+            mounted filesystems, the reorganization algorithm operates on one
+            file at a time, compacting or othewise  improving the layout of the
+            file extents (contiguous blocks of file data).
+          </para>
           <indexterm zone="xfsprogs xfs_fsr">
             <primary sortas="b-xfs_fsr">xfs_fsr</primary>
@@ -247,5 +295,7 @@
         <term><command>xfs_growfs</command></term>
         <listitem>
-          <para>expands an XFS file system.</para>
+          <para>
+            expands an XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_growfs">
             <primary sortas="b-xfs_growfs">xfs_growfs</primary>
@@ -257,6 +307,8 @@
         <term><command>xfs_info</command></term>
         <listitem>
-          <para>is equivalent to invoking <command>xfs_growfs</command>, but
-          specifying that no change to the file system is to be made.</para>
+          <para>
+            is equivalent to invoking <command>xfs_growfs</command>, but
+            specifying that no change to the file system is to be made.
+          </para>
           <indexterm zone="xfsprogs xfs_info">
             <primary sortas="b-xfs_info">xfs_info</primary>
@@ -268,7 +320,9 @@
         <term><command>xfs_io</command></term>
         <listitem>
-          <para>is a debugging tool like <command>xfs_db</command>, but is
-          aimed at examining the regular file I/O path rather than the raw
-          XFS volume itself.</para>
+          <para>
+            is a debugging tool like <command>xfs_db</command>, but is
+            aimed at examining the regular file I/O path rather than the raw
+            XFS volume itself.
+          </para>
           <indexterm zone="xfsprogs xfs_io">
             <primary sortas="b-xfs_io">xfs_io</primary>
@@ -280,5 +334,7 @@
         <term><command>xfs_logprint</command></term>
         <listitem>
-          <para>prints the log of an XFS file system.</para>
+          <para>
+            prints the log of an XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_logprint">
             <primary sortas="b-xfs_logprint">xfs_logprint</primary>
@@ -290,5 +346,7 @@
         <term><command>xfs_mdrestore</command></term>
         <listitem>
-          <para>restores an XFS metadump image to a filesystem image.</para>
+          <para>
+            restores an XFS metadump image to a filesystem image.
+          </para>
           <indexterm zone="xfsprogs xfs_mdrestore">
             <primary sortas="b-xfs_mdrestore">xfs_mdrestore</primary>
@@ -300,5 +358,7 @@
         <term><command>xfs_metadump</command></term>
         <listitem>
-          <para>copies XFS filesystem metadata to a file.</para>
+          <para>
+            copies XFS filesystem metadata to a file.
+          </para>
           <indexterm zone="xfsprogs xfs_metadump">
             <primary sortas="b-xfs_metadump">xfs_metadump</primary>
@@ -310,5 +370,7 @@
         <term><command>xfs_mkfile</command></term>
         <listitem>
-          <para>creates an XFS file, padded with zeroes by default.</para>
+          <para>
+            creates an XFS file, padded with zeroes by default.
+          </para>
           <indexterm zone="xfsprogs xfs_mkfile">
             <primary sortas="b-xfs_mkfile">xfs_mkfile</primary>
@@ -320,6 +382,8 @@
         <term><command>xfs_ncheck</command></term>
         <listitem>
-          <para>generates pathnames from inode numbers for an
-          XFS file system.</para>
+          <para>
+            generates pathnames from inode numbers for an
+            XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_ncheck">
             <primary sortas="b-xfs_ncheck">xfs_ncheck</primary>
@@ -331,6 +395,8 @@
         <term><command>xfs_quota</command></term>
         <listitem>
-          <para>is a utility for reporting and editing various
-          aspects of filesystem quota.</para>
+          <para>
+            is a utility for reporting and editing various
+            aspects of filesystem quota.
+          </para>
           <indexterm zone="xfsprogs xfs_quota">
             <primary sortas="b-xfs_quota">xfs_quota</primary>
@@ -342,5 +408,7 @@
         <term><command>xfs_repair</command></term>
         <listitem>
-          <para>repairs corrupt or damaged XFS file systems.</para>
+          <para>
+            repairs corrupt or damaged XFS file systems.
+          </para>
           <indexterm zone="xfsprogs xfs_repair">
             <primary sortas="b-xfs_repair">xfs_repair</primary>
@@ -352,6 +420,8 @@
         <term><command>xfs_rtcp</command></term>
         <listitem>
-          <para>copies a file to the real-time partition on an
-          XFS file system.</para>
+          <para>
+            copies a file to the real-time partition on an
+            XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_rtcp">
             <primary sortas="b-xfs_rtcp">xfs_rtcp</primary>
@@ -363,6 +433,8 @@
         <term><command>xfs_spaceman</command></term>
         <listitem>
-          <para>reports and controls free space usage in an
-          XFS file system.</para>
+          <para>
+            reports and controls free space usage in an
+            XFS file system.
+          </para>
           <indexterm zone="xfsprogs xfs_spaceman">
             <primary sortas="b-xfs_spaceman">xfs_spaceman</primary>
@@ -374,7 +446,9 @@
         <term><filename class="libraryfile">libhandle.so</filename></term>
         <listitem>
-          <para>contains XFS-specific functions that provide a way to perform
-          certain filesystem  operations without using a file descriptor to
-          access filesystem objects.</para>
+          <para>
+            contains XFS-specific functions that provide a way to perform
+            certain filesystem  operations without using a file descriptor to
+            access filesystem objects.
+          </para>
           <indexterm zone="xfsprogs libhandle">
             <primary sortas="c-libhandle">libhandle.so</primary>
