[system-administrators-guide] Improve markup

[stephenw]

commit cf7d659bdfa9beaeb854b62a82be980ac32efd0d
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Sun Jan 25 10:14:01 2015 +0100

    Improve markup

 en-US/Working_with_the_GRUB_2_Boot_Loader.xml |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
index 22a5d92..1617520 100644
--- a/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
+++ b/en-US/Working_with_the_GRUB_2_Boot_Loader.xml
@@ -692,7 +692,7 @@ For more information on adding kernel options, see <xref linkend="sec-Editing_an
 	<section id="sec-Booting_to_Emergency_Mode">
 		<title>Booting to Emergency Mode</title>
 		<para>
-			 Emergency mode provides the most minimal environment possible and allows you to repair your system even in situations when the system is unable to enter rescue mode. In emergency mode, the system mounts the <systemitem class="username">root</systemitem> file system only for reading, does not attempt to mount any other local file systems, does not activate network interfaces, and only starts few essential services. In Fedora, emergency mode requires the root password. 
+			 Emergency mode provides the most minimal environment possible and allows you to repair your system even in situations when the system is unable to enter rescue mode. In emergency mode, the system mounts the <systemitem class="username">root</systemitem> file system only for reading, does not attempt to mount any other local file systems, does not activate network interfaces, and only starts few essential services. In Fedora, emergency mode requires the <systemitem class="username">root</systemitem> password. 
 		</para>
 		<procedure>
 			<step>
@@ -730,7 +730,7 @@ For more information on adding kernel options, see <xref linkend="sec-Editing_an
 			Note that in GRUB 2, resetting the password is no longer performed in single-user mode as it was in GRUB included in Fedora 15 and Red&nbsp;Hat Enterprise&nbsp;Linux&nbsp;6. The <systemitem class="username">root</systemitem> password is now required to operate in <literal>single-user</literal> mode as well as in <literal>emergency</literal> mode.
 		</para>
     <para>
-      Two procedures for changing the <systemitem class="username">root</systemitem> password are shown here. The <xref linkend="proc-Resetting_the_Root_Password_Using_bin_sh" /> procedure creates a shell, in a changed root environment, using <command>init=/bin/sh</command>. It is the shorter of the two procedures and does not require an SELinux relabel, which can be time consuming. But this procedure will not work if you have a USB keyboard, encrypted file systems, and does not work in certain virtual machines or systems. The <xref linkend="proc-Resetting_the_Root_Password_Using_rd.break" /> procedure makes use of <command>rd.break</command> to interrupt the boot process before control is passed from <systemitem>initramfs</systemitem> to <systemitem class="service">systemd</systemitem>. The disadvantage of this method is that you have to then change <systemitem class="username">root</systemitem> using the <command>sysroot</command> command.</para>
+      Two procedures for changing the <systemitem class="username">root</systemitem> password are shown here. The <xref linkend="proc-Resetting_the_Root_Password_Using_bin_sh" /> procedure creates a shell, in a changed <systemitem class="username">root</systemitem> environment, using <command>init=/bin/sh</command>. It is the shorter of the two procedures and does not require an SELinux relabel, which can be time consuming. But this procedure will not work if you have a USB keyboard, encrypted file systems, and does not work in certain virtual machines or systems. The <xref linkend="proc-Resetting_the_Root_Password_Using_rd.break" /> procedure makes use of <command>rd.break</command> to interrupt the boot process before control is passed from <systemitem>initramfs</systemitem> to <systemitem class="service">systemd</systemitem>. The disadvantage of this method is that you have to then change <systemitem class="username">root</systemitem> using the <command>sysroot</command> 
 command.</para>
 		<procedure id="proc-Resetting_the_Root_Password_Using_bin_sh">
 		<title>Resetting the Root Password Using /bin/sh</title>
 			<step>
@@ -863,7 +863,7 @@ For more information on adding kernel options, see <xref linkend="sec-Editing_an
 				</para>
 				<para>
 					Remount the file system as writable:
-			<screen>switch_root:/#&nbsp;<command>mount -o remount,rw /sysroot </command></screen>
+			<screen>switch_root:/#&nbsp;<command>mount -o remount,rw /sysroot</command></screen>
 				</para>
 			</step>
 			<step>