diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index a9d21c6c95..0c7d10b740 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -11,7 +11,7 @@
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.146 2001/02/26 21:51:48 nik Exp $
+ $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.147 2001/02/28 22:47:51 nik Exp $
This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@@ -3701,9 +3701,9 @@ quit
but the activity that the compiler is carrying out changes
each time.
- For example, suppose you're running "make buildworld", and
+ For example, suppose you're running make buildworld
, and
the compile fails while trying to compile ls.c in to ls.o. If
- you next run "make buildworld" again, and the compile fails in
+ you next run make buildworld
again, and the compile fails in
the same place then this is a broken build -- try updating your
sources and try again. If the compile fails elsewhere then this
is almost certainly hardware.
@@ -3754,7 +3754,7 @@ quit
settings, and some motherboard jumpers you have options to
set various timings, mostly the defaults will be
sufficient, but sometimes, setting the wait states on RAM
- too low, or setting the "RAM Speed: Turbo" option, or
+ too low, or setting the RAM Speed: Turbo
option, or
similar in the BIOS will cause strange behaviour. A
possible idea is to set to BIOS defaults, but it might be
worth noting down your settings first!
diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml
index a9d21c6c95..0c7d10b740 100644
--- a/en_US.ISO_8859-1/books/faq/book.sgml
+++ b/en_US.ISO_8859-1/books/faq/book.sgml
@@ -11,7 +11,7 @@
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.146 2001/02/26 21:51:48 nik Exp $
+ $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.147 2001/02/28 22:47:51 nik Exp $
This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@@ -3701,9 +3701,9 @@ quit
but the activity that the compiler is carrying out changes
each time.
- For example, suppose you're running "make buildworld", and
+ For example, suppose you're running make buildworld
, and
the compile fails while trying to compile ls.c in to ls.o. If
- you next run "make buildworld" again, and the compile fails in
+ you next run make buildworld
again, and the compile fails in
the same place then this is a broken build -- try updating your
sources and try again. If the compile fails elsewhere then this
is almost certainly hardware.
@@ -3754,7 +3754,7 @@ quit
settings, and some motherboard jumpers you have options to
set various timings, mostly the defaults will be
sufficient, but sometimes, setting the wait states on RAM
- too low, or setting the "RAM Speed: Turbo" option, or
+ too low, or setting the RAM Speed: Turbo
option, or
similar in the BIOS will cause strange behaviour. A
possible idea is to set to BIOS defaults, but it might be
worth noting down your settings first!