Index: chapter01/changelog.xml
===================================================================
--- chapter01/changelog.xml	(revision 6851fc8b2f9a2c681619c9cec630f6b75c1df248)
+++ chapter01/changelog.xml	(revision beb80e291d09a6ca6f1855b42ae3178514b0a848)
@@ -45,4 +45,14 @@
 
     <listitem>
+      <para>2021-09-06</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Text clarifications in the backup/restore section
+          o fChapter 7. Thanks to Kevin Buckley for the patch.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
       <para>2021-09-01</para>
       <itemizedlist>
Index: chapter07/cleanup.xml
===================================================================
--- chapter07/cleanup.xml	(revision 6851fc8b2f9a2c681619c9cec630f6b75c1df248)
+++ chapter07/cleanup.xml	(revision beb80e291d09a6ca6f1855b42ae3178514b0a848)
@@ -21,5 +21,5 @@
     <para>Second, the libtool .la files are only useful when linking with static
     libraries. They are unneeded and potentially harmful when using dynamic
-    shared libraries, specially when using non-autotools build systems.
+    shared libraries, especially when using non-autotools build systems.
     While still in chroot, remove those files now:</para>
 
@@ -37,4 +37,15 @@
   <sect2>
     <title>Backup</title>
+
+    <para>
+      At this point the essential programs and libraries have been created
+      and your current LFS system is in a good state. Your system can now be
+      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
+      temporary files will be removed, too. To avoid spending extra time to
+      redo something which has been built successfully, creating a backup of
+      the current LFS system may prove useful.
+    </para>
 
     <note><para>
@@ -57,45 +68,52 @@
     </para>
 
+    <para>
+       If you have decided to make a backup, leave the chroot environment:
+    </para>
+
+<screen role="nodump"><userinput>exit</userinput></screen>
+
     <important>
-      <para>All of the following instructions are executed by
-        <systemitem class="username">root</systemitem>. Take extra
-        care about the commands you're going to run as mistakes
+      <para>
+        All of the following instructions are executed by
+        <systemitem class="username">root</systemitem> on your host system.
+        Take extra care about the commands you're going to run as mistakes
         here can modify your host system. Be aware that the
         environment variable <envar>LFS</envar> 
         is set for user <systemitem class="username">lfs</systemitem> by default 
         but may <emphasis>not</emphasis> be set for 
-        <systemitem class="username">root</systemitem>. Whenever 
-        commands are to be executed by <systemitem class="username">root</systemitem>, 
+        <systemitem class="username">root</systemitem>.
+     </para>
+     <para>
+        Whenever commands are to be executed by <systemitem class="username">root</systemitem>, 
         make sure you have set <envar>LFS</envar>.
+     </para>
+     <para>
         This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>.
       </para>
     </important>
 
-    <para>
-       Now, if you are making a backup, leave the chroot environment:
-    </para>
+    <para>Before making a backup, unmount the virtual file systems:</para>
 
-<screen role="nodump"><userinput>exit</userinput></screen>
+<screen role="nodump"><userinput>umount $LFS/dev/pts
+umount $LFS/{sys,proc,run,dev}</userinput></screen>
 
     <para>
-      At this point the essential programs and libraries have been created
-      and your current system is in a good state. Your system can now be
-      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
-      temporary files will be removed, too. To avoid spending extra time to
-      redo something which has been built successfully, prepare a backup.
+      Make sure you have at least 1 GB free disk space (the source tarballs
+      will be included in the backup archive) on the filesystem containing
+      directory where you create the backup archive.
     </para>
 
     <para>
-      Make sure you have at least 1 GB free disk space (the source tarballs
-      will be included in the backup archive) in the home directory of user 
-      <systemitem class="username">root</systemitem>.
+      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>Before we make a backup, unmount the virtual file systems:</para>
-
-<screen role="nodump"><userinput>umount $LFS/dev{/pts,}
-umount $LFS/{sys,proc,run}</userinput></screen>
+    <para>
+      Replace <envar>$HOME</envar> by a directory of your choice if you
+      do not want to have the backup stored in <systemitem 
+      class="username">root</systemitem>'s home directory.
+    </para>
 
     <para>
@@ -108,9 +126,4 @@
           long time (over 10 minutes) even on a resonably fast system.
        </para>
-       
-       <para>
-          Also, ensure the <envar>LFS</envar> environment variable is set 
-          for the root user.
-       </para>
     </note>
 
@@ -121,9 +134,4 @@
 tar -cJpf $HOME/lfs-temp-tools-&versiond;.tar.xz .</userinput></screen>
 
-    <para>
-      Replace <envar>$HOME</envar> by a directory of your choice if you
-      do not want to have the backup stored in <systemitem 
-      class="username">root</systemitem>'s home directory.
-    </para>
   </sect2>
 
