Date: Sun, 22 Nov 1998 05:46:20 -0800 (PST) From: PA@FreeBSD.ee.ntu.edu.tw To: freebsd-gnats-submit@FreeBSD.ORG Subject: docs/8792: Some misspelt words & some fix. Message-ID: <199811221346.FAA09493@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 8792
>Category: docs
>Synopsis: Some misspelt words & some fix.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Nov 22 05:50:01 PST 1998
>Last-Modified:
>Originator: Ming-I Hsieh
>Organization:
NCU CSIE Wireless Lab
>Release: FreeBSD 2.2.7-19980904-SNAP
>Environment:
FreeBSD vanish 2.2.7-19980904-SNAP FreeBSD 2.2.7-19980904-SNAP #0: Tue Oct 27 09
:39:27 CST 1998 PA@vanish:/usr/src/sys/compile/vanish i386
>Description:
Some misspelt words!
>How-To-Repeat:
WEB send-pr
>Fix:
--- admin.sgml.orig Sun Nov 22 21:26:50 1998
+++ admin.sgml Sun Nov 22 21:27:25 1998
@@ -323,7 +323,7 @@
table isn't of any use in this case, the machine is running
FreeBSD 24 hours per day, 7 days per week, no other operating
system should ever be booted on it. So, if you select
- ``A)ll FreeBSD'' in sysinstall's fdisk editor, and answer the
+ ``A) Use Entrie Disk'' in sysinstall's fdisk editor, and answer the
next question with ``No'', you'll get this mode. Note that
this means the BSD bootstrap also forms the MBR for this drive,
so there's no space left for anything like a boot manager.
--- hackers.sgml.orig Sun Nov 22 21:28:32 1998
+++ hackers.sgml Sun Nov 22 21:29:24 1998
@@ -396,7 +396,7 @@
CDs ship).
<p>
- In any case, the method I nornally use is this:
+ In any case, the method I normally use is this:
<itemize>
<item>Set up a kernel config file, optionally adding 'options DDB' if y
ou
@@ -437,7 +437,7 @@
<p> NOTE: FreeBSD crash dumps are usually the same size as the
physical RAM size of your machine. That is, if you have 64MB of
- RAM, you will geta 64MB crash dump. Therefore you must make sure
+ RAM, you will get a 64MB crash dump. Therefore you must make sure
there's enough space in <tt>/var/crash</tt> to hold the dump.
Alternatively, you run <tt/savecore(8)/ manually and have it
recover the crash dump to another directory where you have more
--- applications.sgml.orig Sun Nov 22 21:28:09 1998
+++ applications.sgml Sun Nov 22 21:28:18 1998
@@ -9,7 +9,7 @@
<p>Please take a look at <url url="../ports/"
name="the ports page"> for info on software packages ported to
- FreeBSD. The list currently tops 1000 and is growing daily, so come
+ FreeBSD. The list currently tops 1800 and is growing daily, so come
back to check often or subscribe to the <tt/freebsd-announce/
<ref id="mailing" name="mailing list"> for periodic updates on new
entries.
--- network.sgml.orig Sun Nov 22 21:29:36 1998
+++ network.sgml Sun Nov 22 21:30:39 1998
@@ -839,7 +839,7 @@
usually worth worrying about although it does slow down the
compression protocols substantially. If you have an external
modem, make sure your cable is properly shielded from
- interference - this may erradicate the problem.
+ interference - this may eradicate the problem.
<p>If your link freezes as soon as you've connected and you see
a large number of FCS errors, this may be because your link is
@@ -867,7 +867,7 @@
<p>If all else fails, send as much information as you can,
including your config files, how you're starting <bf/ppp/,
- the relevent parts of your log file and the output of the
+ the relevant parts of your log file and the output of the
<htmlurl url="http://www.freebsd.org/cgi/man.cgi?netstat"
name="netstat -rn"> command (before and after connecting) to the
<url url="mailto:freebsd-questions@FreeBSD.org"
--- troubleshoot.sgml.orig Sun Nov 22 21:31:01 1998
+++ troubleshoot.sgml Sun Nov 22 21:33:00 1998
@@ -204,7 +204,7 @@
<p>If you're using the BNC connector on your network card, you may
also see device timeouts because of bad termination. To check this,
- attach a terminator directly to the NIC (with no cabel) and see if
+ attach a terminator directly to the NIC (with no cable) and see if
the error messages go away.
<p>Some NE2000 compatible cards will give this error if there is
@@ -252,7 +252,7 @@
to notice that it's been fed, so be patient.
<p>Sometimes a SCSI CD-ROM may be missed because it hadn't enough time
- to answer the bus reset. In you have a SCSI CD-ROM please try to
+ to answer the bus reset. If you have a SCSI CD-ROM, please try to
add the following symbol into your kernel configuration file
and recompile.
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811221346.FAA09493>