diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
index 71cb3baecb..cd3cde051a 100644
--- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
@@ -643,7 +643,7 @@ before running "/usr/sbin/freebsd-update install"</screen>
 	</author>
       </authorgroup>
     </sect1info>
-    <title>Portsnap: A Ports Collection Update Tool</title>
+    <title>Portsnap: a Ports Collection Update Tool</title>
 
     <indexterm><primary>Updating and Upgrading</primary></indexterm>
     <indexterm>
@@ -1767,7 +1767,7 @@ Fetching 133 new ports or files... done.</screen>
     </warning>
 
     <warning>
-      <title>Do not use <command>make world</command></title>
+      <title>Do Not Use <command>make world</command></title>
 
       <para>A lot of older documentation recommends using
 	<command>make world</command> for this.  Doing that skips
@@ -1932,16 +1932,16 @@ Fetching 133 new ports or files... done.</screen>
 	</listitem>
       </orderedlist>
 
-      <para>Note that if you're upgrading from one release of the same &os;
+      <para>Note that if you are upgrading from one release of the same &os;
 	branch to a more recent release of the same branch, i.e., from 7.0 to
 	7.1, then this procedure may not be absolutely necessary, since
-	you're unlikely to run into serious mismatches between compiler,
+	you are unlikely to run into serious mismatches between compiler,
 	kernel, userland and configuration files.  The older approach
 	of <command>make <maketarget>world</maketarget></command> followed
 	by building and installing a new kernel might work well enough for
 	minor updates.</para>
 
-      <para>But, when upgrading across major releases, people who don't
+      <para>But, when upgrading across major releases, people who do not
 	follow this procedure should expect some problems.</para>
 
       <para>It is also worth noting that many upgrades
@@ -2965,7 +2965,7 @@ Building everything..
 	</author>
       </authorgroup>
     </sect1info>
-    <title>Deleting obsolete files, directories and libraries</title>
+    <title>Deleting Obsolete Files, Directories and Libraries</title>
     <indexterm>
       <primary>Deleting obsolete files, directories and libraries</primary>
     </indexterm>
@@ -3049,7 +3049,7 @@ Building everything..
       role="package">ports-mgmt/portmaster</filename> and <filename
       role="package">ports-mgmt/portupgrade</filename> utilities can be used to
       automate this process.  After you've made sure that all ports are rebuilt
-      and do not use the old libraries anymore, you can delete them using the
+      and do not use the old libraries any more, you can delete them using the
       following command:</para>
 
     <screen>&prompt.root; <userinput>make delete-old-libs</userinput></screen>