diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml
index ed4bf9d2a1..2b764023f2 100644
--- a/en_US.ISO8859-1/books/faq/book.xml
+++ b/en_US.ISO8859-1/books/faq/book.xml
@@ -1258,7 +1258,7 @@
 		floppy, track for track, and is not meant to be placed
 		on the floppy as a regular file.  You have to transfer
 		it to the floppy <quote>raw</quote>, using the low-level
-		tools (e.g. <command>fdimage</command> or
+		tools (e.g., <command>fdimage</command> or
 		<command>rawrite</command>) described in the <ulink
 		  url="&url.books.handbook;/install.html">installation guide to &os;</ulink>.
 		</para>
@@ -1351,7 +1351,7 @@
 		<guimenuitem>Partition</guimenuitem>.  Select the drive
 		which used to contain your boot manager (likely the
 		first one) and when you come to the partition editor for
-		it, as the very first thing (e.g.  do not make any
+		it, as the very first thing (e.g., do not make any
 		changes) press <keycap>W</keycap>.  This will ask for
 		confirmation, select &gui.yes;, and when you get the
 		Boot Manager selection prompt, be sure to select the
@@ -2809,8 +2809,8 @@ quit</programlisting>
 		on the processor might have died.  In either case you
 		need to ensure that you have hardware running at what it
 		is specified to run at, at least while trying to solve
-		this problem.  i.e.  Clock it back to the default
-		settings.</para>
+		this problem (in other words, clock it back to the default
+		settings.)</para>
 
 	      <para>If you are overclocking then note that it is far
 		cheaper to have a slow system than a fried system that
@@ -3409,7 +3409,7 @@ chip1@pci0:31:5:        class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
 	      <para>Break the warnings by changing the value of
 		<varname>MAX_STRAY_LOG</varname> from
 		<literal>5</literal> to <literal>0</literal> in your
-		platform's (e.g.  &i386;)
+		platform's (e.g., &i386;)
 		<filename>intr_machdep.c</filename> file and rebuild the
 		new kernel and all the warnings will be
 		suppressed.</para>
@@ -4633,7 +4633,7 @@ kern.sched.name: ULE</screen>
 	    &os; lists your disks, first IDE, then SCSI.</para>
 
 	  <para>When you are slicing up your disk, check that the disk
-	    geometry displayed in the FDISK screen is correct (ie.  it
+	    geometry displayed in the FDISK screen is correct (i.e., it
 	    matches the BIOS numbers); if it is wrong, use the
 	    <keycap>G</keycap> key to fix it.  You may have to do this
 	    if there is absolutely nothing on the disk, or if the disk
@@ -5007,7 +5007,7 @@ C:\="DOS"</programlisting>
 	    following to your configuration file
 	    <filename>/boot/grub/menu.lst</filename> (or
 	    <filename>/boot/grub/grub.conf</filename> in some systems,
-	    e.g. Red Hat Linux and its derivatives).</para>
+	    e.g., Red Hat Linux and its derivatives).</para>
 
 	  <programlisting>title &os; 6.1
 	root <replaceable>(hd0,a)</replaceable>
@@ -7556,7 +7556,7 @@ Key F15        A        A        Menu Workplace Nop</programlisting>
 
 	      <para>The most common way to accomplish this is to build a
 		simulated environment in a subdirectory and then run the
-		processes in that directory chroot'd (i.e. <filename
+		processes in that directory chroot'd (i.e., <filename
 		  class="directory">/</filename> for that process is this
 		directory, not the real <filename
 		  class="directory">/</filename> of the system).</para>
@@ -10110,7 +10110,7 @@ panic: page fault</programlisting>
 	<answer>
 	  <para>By default, the kernel address space is 1&nbsp;GB
 	    (2&nbsp;GB for PAE) for i386.  If you run a
-	    network-intensive server (e.g. a large FTP or HTTP server),
+	    network-intensive server (e.g., a FTP or HTTP server),
 	    or you want to use ZFS, you might find that is not
 	    enough.</para>