4 files changed, 11 insertions, 11 deletions

diff --git a/FAQ/applications.sgml b/FAQ/applications.sgml
index 742c0032ee..542fdb54c9 100644
--- a/FAQ/applications.sgml
+++ b/FAQ/applications.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: applications.sgml,v 1.7 1998-09-07 09:19:29 wosch Exp $ -->
+<!-- $Id: applications.sgml,v 1.8 1998-11-22 14:03:32 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
   <sect>
@@ -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.
diff --git a/FAQ/hackers.sgml b/FAQ/hackers.sgml
index fdb1932c30..279e5fde06 100644
--- a/FAQ/hackers.sgml
+++ b/FAQ/hackers.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: hackers.sgml,v 1.7 1998-11-08 11:47:01 jkh Exp $ -->
+<!-- $Id: hackers.sgml,v 1.8 1998-11-22 14:03:32 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
   <sect>
@@ -396,7 +396,7 @@ Cc: current@FreeBSD.ORG
       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 you
@@ -437,7 +437,7 @@ Cc: current@FreeBSD.ORG
 
       <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
diff --git a/FAQ/network.sgml b/FAQ/network.sgml
index 32ca45156c..74da70bc10 100644
--- a/FAQ/network.sgml
+++ b/FAQ/network.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: network.sgml,v 1.17 1998-11-18 21:39:43 dwhite Exp $ -->
+<!-- $Id: network.sgml,v 1.18 1998-11-22 14:03:32 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
   <sect>
@@ -839,7 +839,7 @@ default            10.0.0.2           UGSc        0        0      tun0
         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 @@ default            10.0.0.2           UGSc        0        0      tun0
 
         <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"
diff --git a/FAQ/troubleshoot.sgml b/FAQ/troubleshoot.sgml
index 97877760be..5db8d37e65 100644
--- a/FAQ/troubleshoot.sgml
+++ b/FAQ/troubleshoot.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: troubleshoot.sgml,v 1.6 1998-11-18 21:40:32 dwhite Exp $ -->
+<!-- $Id: troubleshoot.sgml,v 1.7 1998-11-22 14:03:32 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
   <sect>
@@ -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.