diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index 92720541ad..fb08f6033a 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -14,7 +14,7 @@
 
     <corpauthor>The FreeBSD Documentation Project</corpauthor>
 
-    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.168 2001/04/10 17:14:48 jim Exp $</pubdate>
+    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.169 2001/04/11 01:44:24 murray Exp $</pubdate>
 
     <copyright>
       <year>1995</year>
@@ -1511,7 +1511,7 @@ File: +DESC (ignored)</screen>
             uses, and install new boot blocks that can handle the different
             partition ID.</para>
 
-          <para>First, you'll need to to restore the machine to a state where
+          <para>First, you'll need to restore the machine to a state where
             it can get through its self-test screen.  Doing this requires
             powering up the machine without letting it find a FreeBSD
             partition on its primary disk.  One way is to remove the hard disk
@@ -11843,7 +11843,7 @@ Cc: current@FreeBSD.org</programlisting>
 
           <para> The best way to track down the cause of a panic is by
             capturing a crash dump, then using <command>gdb(1)</command>
-            to to a stack trace on the crash dump. Of course, this depends
+            to a stack trace on the crash dump. Of course, this depends
             on <command>gdb(1)</command> in -CURRENT working correctly,
             which I can't guarantee (I recall somebody saying that the new
             ELF-ized <command>gdb(1)</command> didn't handle kernel crash
diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml
index 92720541ad..fb08f6033a 100644
--- a/en_US.ISO_8859-1/books/faq/book.sgml
+++ b/en_US.ISO_8859-1/books/faq/book.sgml
@@ -14,7 +14,7 @@
 
     <corpauthor>The FreeBSD Documentation Project</corpauthor>
 
-    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.168 2001/04/10 17:14:48 jim Exp $</pubdate>
+    <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.169 2001/04/11 01:44:24 murray Exp $</pubdate>
 
     <copyright>
       <year>1995</year>
@@ -1511,7 +1511,7 @@ File: +DESC (ignored)</screen>
             uses, and install new boot blocks that can handle the different
             partition ID.</para>
 
-          <para>First, you'll need to to restore the machine to a state where
+          <para>First, you'll need to restore the machine to a state where
             it can get through its self-test screen.  Doing this requires
             powering up the machine without letting it find a FreeBSD
             partition on its primary disk.  One way is to remove the hard disk
@@ -11843,7 +11843,7 @@ Cc: current@FreeBSD.org</programlisting>
 
           <para> The best way to track down the cause of a panic is by
             capturing a crash dump, then using <command>gdb(1)</command>
-            to to a stack trace on the crash dump. Of course, this depends
+            to a stack trace on the crash dump. Of course, this depends
             on <command>gdb(1)</command> in -CURRENT working correctly,
             which I can't guarantee (I recall somebody saying that the new
             ELF-ized <command>gdb(1)</command> didn't handle kernel crash