diff --git a/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml b/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
index c4185e4d37..1c876bf8c8 100644
--- a/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
@@ -530,7 +530,7 @@
 		<emphasis>not</emphasis> a regular file.  It is an
 		<emphasis>image</emphasis> of the complete contents of
 		the memory stick.  It <emphasis>cannot</emphasis>
-		simply be copied like a regular file, but must be
+		be copied like a regular file, but must be
 		written directly to the target device with
 		&man.dd.1;:</para>
 
@@ -780,7 +780,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
 
 	<calloutlist>
 	  <callout arearefs="bsdinstall-prompt-single">
-	    <para>This is the prompt used on systems with just one
+	    <para>This is the prompt used on systems with one
 	      CPU.</para>
 	  </callout>
 
@@ -1384,8 +1384,8 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
 	</mediaobject>
       </figure>
 
-      <para>The entire disk can be allocated to &os;, or just a
-	portion of it.  If
+      <para>The entire disk or a portion of it can be allocated to &os;.
+	If
 	<guibutton>[&nbsp;Entire&nbsp;Disk&nbsp;]</guibutton> is
 	chosen, a general partition layout filling the whole disk is
 	created.  Selecting
@@ -1546,7 +1546,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
 
 	<listitem>
 	  <para><literal>freebsd-ufs</literal> - A &os; UFS
-	    filesystem.</para>
+	    file system.</para>
 	</listitem>
 
 	<listitem>
@@ -1562,11 +1562,11 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
 	of the available <acronym>GPT</acronym> partition
 	types.</para>
 
-      <para>Multiple filesystem partitions can be used, and some
+      <para>Multiple file system partitions can be used, and some
 	people may prefer a traditional layout with separate
 	partitions for the <filename>/</filename>,
 	<filename>/var</filename>, <filename>/tmp</filename>, and
-	<filename>/usr</filename> filesystems.  See
+	<filename>/usr</filename> file systems.  See
 	<xref linkend="bsdinstall-part-manual-splitfs"/> for an
 	example.</para>
 
@@ -1587,7 +1587,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
       </tip>
 
       <para>A mountpoint is needed if this partition will contain a
-	filesystem.  If only a single UFS partition will be created,
+	file system.  If only a single UFS partition will be created,
 	the mountpoint should be <filename>/</filename>.</para>
 
       <para>A <emphasis>label</emphasis> is also requested.  A label
@@ -1604,7 +1604,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
 	in <filename>/dev/</filename>.</para>
 
       <tip>
-	<para>Use a unique label on every filesystem to avoid
+	<para>Use a unique label on every file system to avoid
 	  conflicts from identical labels.  A few letters from the
 	  computer's name, use, or location can be added to the label.
 	  For instance, <literal>labroot</literal> or
@@ -1613,13 +1613,13 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
       </tip>
 
       <example xml:id="bsdinstall-part-manual-splitfs">
-	<title>Creating Traditional Split Filesystem
+	<title>Creating Traditional Split File System
 	  Partitions</title>
 
 	<para>For a traditional partition layout where the
 	  <filename>/</filename>, <filename>/var</filename>,
 	  <filename>/tmp</filename>, and <filename>/usr</filename>
-	  directories are separate filesystems on their own
+	  directories are separate file systems on their own
 	  partitions, create a GPT partitioning scheme, then create
 	  the partitions as shown.  Partition sizes shown are typical
 	  for a 20G target disk.  If more space is available on the
@@ -2909,7 +2909,8 @@ login:</screen>
       <title>&os; Shutdown</title>
 
       <para>Proper shutdown of a &os; computer helps protect data and
-	even hardware from damage.  Do not just turn off the power.
+	even hardware from damage.  Do not turn off the power before
+	the system has been properly shut down.
 	If the user is a member of the
 	<systemitem class="groupname">wheel</systemitem> group, become
 	the superuser by typing <command>su</command> at the command