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

Use <quote></quote> instead of "".

Browse source 
Submitted by:	Shun SUZUKI <si006@ccm.gs.niigata-u.ac.jp>
This commit is contained in:
Hiroki Sato 2001-03-07 20:00:49 +00:00
parent 0464ef7ae5
commit 4f2d7e7a7d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8903
2 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.146 2001/02/26 21:51:48 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.147 2001/02/28 22:47:51 nik Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -3701,9 +3701,9 @@ quit</programlisting>
but the activity that the compiler is carrying out changes
each time.</para>
<para>For example, suppose you're running "make buildworld", and
<para>For example, suppose you're running <quote>make buildworld</quote>, 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 <quote>make buildworld</quote> 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.</para>
@ -3754,7 +3754,7 @@ quit</programlisting>
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 <quote>RAM Speed: Turbo</quote> 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!</para>

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

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.146 2001/02/26 21:51:48 nik Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.147 2001/02/28 22:47:51 nik Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -3701,9 +3701,9 @@ quit</programlisting>
but the activity that the compiler is carrying out changes
each time.</para>
<para>For example, suppose you're running "make buildworld", and
<para>For example, suppose you're running <quote>make buildworld</quote>, 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 <quote>make buildworld</quote> 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.</para>
@ -3754,7 +3754,7 @@ quit</programlisting>
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 <quote>RAM Speed: Turbo</quote> 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!</para>