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

Fix a typo (accellerator -> accelerator) and a missing space.

Browse source 
PR:		13208
Submitted by:	Mark Ovens <mark@ukug.uk.freebsd.org>
This commit is contained in:
Chris Piazza 1999-08-24 02:35:59 +00:00
parent 122d319794
commit 38949d4e41
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=5434
2 changed files with 4 additions and 4 deletions
en_US.ISO8859-1/books/faq
book.sgml
en_US.ISO_8859-1/books/faq
book.sgml

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

@ -10,7 +10,7 @@
</author>
</authorgroup>
<pubdate>$Date: 1999-08-18 19:16:52 $</pubdate>
<pubdate>$Date: 1999-08-24 02:35:59 $</pubdate>
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
@ -2637,7 +2637,7 @@ the remote machine.</para>
relating to interrupts. It may be due to bugs but can also happen
by nature of certain devices. Running TCP/IP over the parallel
port using a large MTU is one good way to provoke this problem.
Graphics accelleratorscan also get you here, in which case you
Graphics accelerators can also get you here, in which case you
should check the interrupt setting of the card first.</para>
<para>A side effect of this problem are dying processes with the

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

@ -10,7 +10,7 @@
</author>
</authorgroup>
<pubdate>$Date: 1999-08-18 19:16:52 $</pubdate>
<pubdate>$Date: 1999-08-24 02:35:59 $</pubdate>
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
@ -2637,7 +2637,7 @@ the remote machine.</para>
relating to interrupts. It may be due to bugs but can also happen
by nature of certain devices. Running TCP/IP over the parallel
port using a large MTU is one good way to provoke this problem.
Graphics accelleratorscan also get you here, in which case you
Graphics accelerators can also get you here, in which case you
should check the interrupt setting of the card first.</para>
<para>A side effect of this problem are dying processes with the