afterlfs: several fixes

- Use <emphasis role="bold"> for bold, instead of <command>.
- Remove "X window" as some graphical environments are Wayland-based.
- "Full BLFS" -> "BLFS", and "partial BLFS" -> "basic LFS" (I guess some
  content is copied from Basic BLFS).

chapter11/afterlfs.xml

@@ -39,8 +39,8 @@
         <ulink url="&blfs-book;xfce/xfce.html">XFCE</ulink>,
         <ulink url="&blfs-book;kde/kde.html">KDE</ulink>, or
         <ulink url="&blfs-book;gnome/gnome.html">Gnome</ulink>
-        based on the
-        <ulink url="&blfs-book;x/installing.html">X Window graphical environment</ulink>
+        based on a basic
+        <ulink url="&blfs-book;x/installing.html">graphical environment</ulink>
         and several graphical based applications such as the
         <ulink url="&blfs-book;xsoft/firefox.html">Firefox web browser</ulink>,
         <ulink url="&blfs-book;xsoft/thunderbird.html">Thunderbird email client</ulink>,
@@ -54,7 +54,7 @@
      <para>
         In addition to the above, there is a set of applications that are
         suitable for all systems for system management. These applications are
-        all in the full BLFS book. Not
+        all in the BLFS book. Not
         all packages are needed in all environments. For example
         <ulink url="&blfs-book;basicnet/dhcpcd.html">dhcpcd</ulink>,
         is not appropriate for a server and
@@ -68,7 +68,7 @@
   </sect2>
 
   <sect2>
-  <title>Working in a partial BLFS environment</title>
+  <title>Working in a basic LFS environment</title>
 
     <para>
       When you initially boot into LFS, you have all the internal tools to build
@@ -91,7 +91,7 @@
        In order to properly build packages in chroot, you will also need to
        remember to mount the virtual file systems if they are not already
        mounted. One way to do this is to create a script on the
-       <command>HOST</command> system:
+       <emphasis role="bold">HOST</emphasis> system:
     </para>
 
 <screen><command>cat &gt; ~/mount-virt.sh &lt;&lt; "EOF"