os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix a couple of typos. ("to to" -> "to")

Browse source 
Submitted by:	Valentino Vaschetto <logo@osd.bsdi.com>
This commit is contained in:
Murray Stokely 2001-04-12 23:04:43 +00:00
parent 88334892d5
commit 703d60fd8f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9181
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -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

6
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -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