Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision cdd5a33b24d3bcf5121ad92bcd56f5488cc4472d)
+++ postlfs/config/bootdisk.xml	(revision acf7e2cff94e6c1a123e58c153c8dc5859e6901d)
@@ -36,5 +36,5 @@
     ways, it is equivalent to building an entire LFS system.
     In addition, it would be a repetition of information already available.
-    For these reasons, the procedures for a rescue device image are not
+    For these reasons, the procedures for creating a rescue device image are not
     presented here.</para>
 
@@ -65,6 +65,7 @@
     longer capable of building an entire LFS/BLFS system, but is still a
     good rescue CD-ROM.  If you download the
-    ISO image, use <xref linkend="xorriso"/> to copy the image to a
-    CD-ROM.</para>
+<!--    ISO image, use <xref linkend="xorriso"/> to copy the image to a-->
+    ISO image, use <ulink url="&blfs-book;multimedia/libisoburn.html">xorriso</ulink> 
+    to copy the image to a CD-ROM.</para>
 
     <para>The instructions for using GRUB2 to make a custom rescue CD-ROM are
@@ -78,5 +79,5 @@
     <title>Creating a Bootable USB Drive</title>
 
-    <para>A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as
+    <para>A USB pen drive, sometimes called a thumb drive, is recognized by Linux as
     a SCSI device.  Using one of these devices as a rescue device has the advantage
     that it is usually large enough to hold more than a minimal boot image.  You
@@ -86,4 +87,11 @@
     as well as the Linux kernel and supporting files.</para>
 
+    <para>Creating a bootable USB drive from a downloaded iso file is
+    relatively simple. For example, if the iso file is some-rescue.iso and when
+    inserting a usb drive into the system the drive is recognized as /dev/sdg,
+    the file can be copied to the drive (as the root user) with:</para>
+
+<screen><userinput>dd of=/dev/sdg bs=8M status=progress oflag=direct if=some-rescue.iso</userinput></screen>
+
     <para condition="html" role="usernotes">User Notes:
     <ulink url='&blfs-wiki;/CreatingaCustomBootDevice'/></para>
Index: postlfs/config/config.xml
===================================================================
--- postlfs/config/config.xml	(revision cdd5a33b24d3bcf5121ad92bcd56f5488cc4472d)
+++ postlfs/config/config.xml	(revision acf7e2cff94e6c1a123e58c153c8dc5859e6901d)
@@ -40,23 +40,24 @@
   <xref linkend="postlfs-config-vimrc"/>.</para>
 
-  <para> The remaining topics, <xref linkend="postlfs-config-logon"/>,
+<!--  <para> The remaining topics, <xref linkend="postlfs-config-logon"/>,
   <phrase revision="sysv"><xref linkend="postlfs-config-random"/>,</phrase>
   and <xref linkend="autofs"/> are then addressed, in that order. They
-  don't have much interaction with the other topics in this chapter.</para>
+  don't have much interaction with the other topics in this chapter.</para> -->
 
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="bootdisk.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="console-fonts.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="firmware.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="devices.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="skel.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="profile.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="vimrc.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="logon.xml"/>
+  <xi:include xmlns:xi="&xinclude;" href="bootdisk.xml"/>
+  <xi:include xmlns:xi="&xinclude;" href="console-fonts.xml"/>
+  <xi:include xmlns:xi="&xinclude;" href="firmware.xml"/>
+  <xi:include xmlns:xi="&xinclude;" href="../filesystems/initramfs.xml"/>
+  <xi:include xmlns:xi="&xinclude;" href="devices.xml"/>
+<!--  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="skel.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users.xml"/>-->
+  <xi:include xmlns:xi="&xinclude;" href="profile.xml"/>
+  <xi:include xmlns:xi="&xinclude;" href="vimrc.xml"/>
+<!--  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="logon.xml"/>-->
 
   <!-- sysv only -->
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="random.xml"/>
+  <!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="random.xml"/>
 
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="lsb-release.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="lsb-release.xml"/>-->
 
 </chapter>
Index: postlfs/config/console-fonts.xml
===================================================================
--- postlfs/config/console-fonts.xml	(revision cdd5a33b24d3bcf5121ad92bcd56f5488cc4472d)
+++ postlfs/config/console-fonts.xml	(revision acf7e2cff94e6c1a123e58c153c8dc5859e6901d)
@@ -22,5 +22,7 @@
   <para>
     An LFS system can be used without a graphical desktop, and unless or until
-    you install <xref linkend="x-window-system"/> you will have to work in the
+<!--    you install <xref linkend="x-window-system"/> you will have to work in the-->
+    you install <ulink url="&blfs-book;x/installing.html">the X Window System</ulink> 
+    you will have to work in the
     console. Most, if not all, PCs boot with an 8x16 font - whatever the actual
     screen size. There are a few things you can do to alter the display on the
@@ -53,8 +55,10 @@
       <literal>root=/dev/sda2 video=1024x768 ro</literal> based on the
       example in LFS section 8.4.4 :
-      <phrase revision="sysv">
+      <!--<phrase revision="sysv">
       <ulink url="&lfs-root;/chapter08/grub.html"/></phrase>
-      <phrase revision="systemd">
-      <ulink url="&lfs-rootd;/chapter08/grub.html"/></phrase>.
+      <ulink url="&lfs-root;/chapter08/grub.html"/></phrase>-->
+      <ulink url="&lfs-webroot;lfs/view/stable/chapter08/grub.html"/>
+      <!--<phrase revision="systemd">
+      <ulink url="&lfs-rootd;/chapter08/grub.html"/></phrase>.-->
     </para>
 
@@ -91,5 +95,5 @@
       to 512 characters (in which  case, the bright colours will not be
       available). Clearly, these console fonts cannot be used to display CJK
-      text - that would need thousands of available glyphs.
+      text &mdash; that would need thousands of available glyphs.
     </para>
 
@@ -154,6 +158,15 @@
       When you find a font which to wish to use, as the
       <systemitem class="username">root</systemitem> user) edit
+      the appropriate configururation file.  
+      
+      If your version of LFS is 
+      System V based, see LFS section 7.6.5 at
+      <ulink url="&lfs-webroot;lfs/view/stable/chapter07/usage.html"/>.
+      
+      If your version of LFS is 
+      systemd based, see LFS section 7.6 at
+      <ulink url="&lfs-webroot;lfs/view/stable-systemd/chapter07/console.html"/>.
+      <!--
       <phrase revision="sysv">
-      <filename>/etc/sysconfig/console</filename> as described in
       LFS section 7.6.5
       <ulink url="&lfs-root;/chapter07/usage.html"/>.</phrase>
@@ -162,4 +175,5 @@
       LFS section 7.6
       <ulink url="&lfs-rootd;/chapter07/console.html"/>.</phrase>.
+      -->
     </para>
 
@@ -218,5 +232,5 @@
       By default <application>terminus-fonts</application> will try to create
       several types of font, and it will fail if <command>bdftopcf</command>
-      from <xref linkend="xorg7-app"/> has not been installed. The configure
+      from <!--<xref linkend="xorg7-app"/>--> has not been installed. The configure
       script is only really useful if you go on to install
       <emphasis>all</emphasis> the fonts (console and X11 bitmap) to the
Index: postlfs/config/devices.xml
===================================================================
--- postlfs/config/devices.xml	(revision cdd5a33b24d3bcf5121ad92bcd56f5488cc4472d)
+++ postlfs/config/devices.xml	(revision acf7e2cff94e6c1a123e58c153c8dc5859e6901d)
@@ -126,5 +126,6 @@
     <note><para>The above line is used for descriptive purposes only. The
     scanner <application>udev</application> rules are put into place when
-    installing <xref linkend='sane'/>.</para></note>
+<!--    installing <xref linkend='sane'/>.</para></note>-->
+    installing  <ulink url='&blfs-book;/pst/sane.html'>sane</ulink>.</para></note>
 
   </sect2>
Index: postlfs/config/firmware.xml
===================================================================
--- postlfs/config/firmware.xml	(revision cdd5a33b24d3bcf5121ad92bcd56f5488cc4472d)
+++ postlfs/config/firmware.xml	(revision acf7e2cff94e6c1a123e58c153c8dc5859e6901d)
@@ -80,7 +80,9 @@
   firmware in order to load it into the system:
     <xref linkend="cpio"/>,
-    <xref linkend="git"/>,
-    <xref linkend="pciutils"/>, and
-    <xref linkend="wget"/></para></note>
+    <xref linkend="pciutils"/>, 
+    <xref linkend="wget"/>, and
+  <!--  <xref linkend="git"/>, -->
+    <ulink url="&blfs-book;/general/git.html">git</ulink>
+    </para></note>
 
   <para condition="html" role="usernotes">User Notes:
@@ -375,6 +377,6 @@
 
     <para>There are actually two ways of installing this firmware. BLFS, in the
-    'Kernel Configuration for additional firmware' section part of the <xref
-    linkend="xorg-ati-driver"/> section  gives an example of compiling the
+    'Kernel Configuration for additional firmware' section part of the <!--<xref
+    linkend="xorg-ati-driver"/>--> section  gives an example of compiling the
     firmware into the kernel - that is slightly faster to load, but uses more
     kernel memory. Here we will use the alternative method of making the radeon
