diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
index 80699108bd..d3ce85d834 100644
--- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
+++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
@@ -823,18 +823,18 @@ Reading symbols from /sys/modules/linux/linux.ko...done.
   </sect1>
 
   <sect1 id="kerneldebug-deadlocks">
-    <title>Debugging the Deadlocks</title>
+    <title>Debugging Deadlocks</title>
 
     <para>You may experience so called deadlocks, the situation where
-      system stops doing useful work. To provide the helpful bug report
-      in this situation, you shall use ddb as described above. Please,
-      include the output of <command>ps</command> and
+      a system stops doing useful work. To provide a helpful bug report
+      in this situation, use &man.ddb.4; as described above.
+      Include the output of <command>ps</command> and
       <command>trace</command> for suspected processes in the
       report.</para>
 
-    <para>If possible, consider doing further investigation. Receipt
-      below is especially useful if you suspect deadlock occurs in the
-      VFS layer. Add the options
+    <para>If possible, consider doing further investigation. The receipt
+      below is especially useful if you suspect that a deadlock occurs in the
+      VFS layer. Add the following options
       <programlisting>makeoptions		DEBUG=-g
 	options		INVARIANTS
 	options		INVARIANT_SUPPORT
@@ -843,15 +843,15 @@ Reading symbols from /sys/modules/linux/linux.ko...done.
 	options		DEBUG_VFS_LOCKS
 	options		DIAGNOSTIC</programlisting>
 
-      to the kernel config. When deadlock occurs, in addition to the
+      to the kernel configuration file. When a deadlock occurs, in addition to the
       output of the <command>ps</command> command, provide information
       from the <command>show allpcpu</command>, <command>show
       alllocks</command>, <command>show lockedvnods</command> and
       <command>show alltrace</command>.</para>
 
-    <para>For threaded processes, to obtain meaningful backtraces, use
+    <para>To obtain meaningful backtraces for threaded processes, use
       <command>thread thread-id</command> to switch to the thread
-      stack, and do backtrace with <command>where</command>.</para>
+      stack, and do a backtrace with <command>where</command>.</para>
   </sect1>
 </chapter>