a bunch of spelling errors

17 files changed, 49 insertions, 49 deletions

diff --git a/share/doc/handbook/bibliography.sgml b/share/doc/handbook/bibliography.sgml
index 3558eca165d3..c408f762d704 100644
--- a/share/doc/handbook/bibliography.sgml
+++ b/share/doc/handbook/bibliography.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: bibliography.sgml,v 1.12 1996/09/09 01:56:55 jkh Exp $ -->
+<!-- $Id: bibliography.sgml,v 1.13 1996/09/09 03:43:29 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
     <chapt>
@@ -110,7 +110,7 @@
 		<newline>ISBN 0-13-131509-9</item>
 
 	    <item>Stevens, W. Richard. <em>Advanced
-		Programming in the UNIX Enviroment</em>.
+		Programming in the UNIX Environment</em>.
 		Reading, Mass. : Addison-Wesley, 1992
 		<newline>ISBN 0-201-56317-7</item>
 
diff --git a/share/doc/handbook/development.sgml b/share/doc/handbook/development.sgml
index cbf4dd57406e..5b498fc96065 100644
--- a/share/doc/handbook/development.sgml
+++ b/share/doc/handbook/development.sgml
@@ -12,8 +12,8 @@ name="list of contributors">. We are constantly on the lookout for
 new developers and ideas, and those interested in becoming more
 closely involved with the project need simply contact us at our
 <htmlurl url="mailto:hackers@freebsd.org" name="hackers@freebsd.org">
-mailing list.  Those who prefer to work more independantly are also
-accomodated, and they are free to use our FTP facilities at <htmlurl
+mailing list.  Those who prefer to work more independently are also
+accommodated, and they are free to use our FTP facilities at <htmlurl
 url="ftp://ftp.freebsd.org/pub/FreeBSD/incoming"
 name="ftp.freebsd.org"> to distribute their own patches or work-in-progress
 sources.  Our <htmlurl url="mailto:announce@freebsd.org"
@@ -21,7 +21,7 @@ name="announcements mailing list"> is also available to those wishing
 to make other FreeBSD users aware of major areas of work.
 
 Useful things to know about the FreeBSD project and its development process,
-whether working independantly or in close cooperation:
+whether working independently or in close cooperation:
 
 <descrip>
 <itemize>
diff --git a/share/doc/handbook/firewalls.sgml b/share/doc/handbook/firewalls.sgml
index 44caa65e638d..bc65850d0b9f 100644
--- a/share/doc/handbook/firewalls.sgml
+++ b/share/doc/handbook/firewalls.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: firewalls.sgml,v 1.12 1996/09/14 17:18:10 alex Exp $ -->
+<!-- $Id: firewalls.sgml,v 1.13 1996/09/15 00:15:33 alex Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Firewalls<label id="firewalls"></heading>
@@ -141,7 +141,7 @@ will happen.
 packets logged through <tt>syslogd(8)</tt> on a per entry basis.
 You may wish to use this option in hostile environments in which
 you want to log firewall activity, but do not want to be open to
-a denial of serivce attack via syslog flooding.
+a denial of service attack via syslog flooding.
 
 <p>When a chain entry reaches the packet limit specified, logging
 is turned off for that particular entry.  To resume logging, you
diff --git a/share/doc/handbook/handbook.sgml b/share/doc/handbook/handbook.sgml
index 2fbe8c1446ca..aa557faf3bef 100644
--- a/share/doc/handbook/handbook.sgml
+++ b/share/doc/handbook/handbook.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: handbook.sgml,v 1.56 1996/09/08 21:12:54 jfieber Exp $ -->
+<!-- $Id: handbook.sgml,v 1.57 1996/09/09 01:56:57 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
@@ -19,7 +19,7 @@
 <!ENTITY % sections SYSTEM "sections.sgml">
 %sections;
 
-<!-- The curerntly released version of FreeBSD -->
+<!-- The currently released version of FreeBSD -->
 <!ENTITY rel.current CDATA "2.1.5">
 
 ]>
diff --git a/share/doc/handbook/hw.sgml b/share/doc/handbook/hw.sgml
index 33972f06a551..bf8e8a79d083 100644
--- a/share/doc/handbook/hw.sgml
+++ b/share/doc/handbook/hw.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: hw.sgml,v 1.42 1996/09/22 15:40:16 wosch Exp $ -->
+<!-- $Id: hw.sgml,v 1.43 1996/10/01 05:28:20 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -297,7 +297,7 @@ Slippery when wet.  Beware of dog.
 		problems.
 
 	      <tag>Orion:</tag> Early versions of this chipset suffered from
-	 	a PCI write-posting bug which can cause noticable performance
+	 	a PCI write-posting bug which can cause noticeable performance
 		degradation in applications where large amounts of PCI bus
 		traffic is involved.  B0 stepping or later revisions of the
 		chipset fixed this problem.
@@ -961,7 +961,7 @@ tape drive and media around.  QIC tape drives are the least
 expensive "serious" backup drives.  The downside is the cost of
 media.  QIC tapes are expensive compared to 8mm or 4mm tapes, up
 to 5 times the price per GB data storage.  But, if your needs can
-be satisified with a half-dozen tapes, QIC may be the correct
+be satisfied with a half-dozen tapes, QIC may be the correct
 choice.  QIC is the <em>most</em> common tape drive.  Every site
 has a QIC drive of some density or another.  Therein lies the
 rub, QIC has a large number of densities on physically similar
@@ -1072,7 +1072,7 @@ overridden on the command line to utilize the capacity of current
 tape drives.
 
 	<p><tt>rdump(8)</tt> and <tt>rrestore(8)</tt> backup data
-aross the network to a tape drive attached to another computer.
+across the network to a tape drive attached to another computer.
 Both programs rely upon <tt>rcmd(3)</tt> and <tt>ruserok(3)</tt>
 to access the remote tape drive.  Therefore, the user performing
 the backup must have <tt>rhosts</tt> access to the remote
diff --git a/share/doc/handbook/install.sgml b/share/doc/handbook/install.sgml
index 42d340d9da43..43820f3c0a4a 100644
--- a/share/doc/handbook/install.sgml
+++ b/share/doc/handbook/install.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: install.sgml,v 1.35 1996/09/09 03:57:46 jkh Exp $ -->
+<!-- $Id: install.sgml,v 1.36 1996/09/21 17:51:46 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -375,7 +375,7 @@ Boot:
 	  other types of installation media should be required.
 
 	  After your system is fully installed and you have rebooted
-	  from the hard disk, you can mount the cdrom at any time by
+	  from the hard disk, you can mount the CDROM at any time by
 	  typing: <tt>mount /cdrom</tt>
 
 	  Before removing the CD again, also note that it is necessary to first
diff --git a/share/doc/handbook/isdn.sgml b/share/doc/handbook/isdn.sgml
index 66087c3ccc97..5a2870965a61 100644
--- a/share/doc/handbook/isdn.sgml
+++ b/share/doc/handbook/isdn.sgml
@@ -1,4 +1,4 @@
-<!-- $Id$-->
+<!-- $Id: isdn.sgml,v 1.4 1996/09/29 16:52:40 jfieber Exp $-->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>ISDN<label id="isdn"></heading>
@@ -203,7 +203,7 @@ Network is Twisted Pair ethernet.
 </verb> 
 
 One large advantage of most routers/bridges is that they allow you to
-have 2 SEPERATE INDEPENDANT PPP connections to 2 seperate sites at the
+have 2 SEPERATE INDEPENDANT PPP connections to 2 separate sites at the
 SAME time.  This is not supported on most TA's, except for
 specific(expensive) models that have two serial ports.  Do not confuse
 this with channel bonding.
diff --git a/share/doc/handbook/linuxemu.sgml b/share/doc/handbook/linuxemu.sgml
index c564dba36825..560ec272b2b6 100644
--- a/share/doc/handbook/linuxemu.sgml
+++ b/share/doc/handbook/linuxemu.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: linuxemu.sgml,v 1.10 1996/08/21 07:28:52 asami Exp $ -->
+<!-- $Id: linuxemu.sgml,v 1.11 1996/08/28 00:43:59 asami Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Linux Emulation<label id="linuxemu"></heading>
@@ -368,7 +368,7 @@ to recreate this file whenever you install additional shared
 libraries.
 
 On FreeBSD-stable do not install /compat/linux/etc/ld.so.cache or run
-ldconfig becuase in FreeBSD-stable the syscalls are implemented
+ldconfig because in FreeBSD-stable the syscalls are implemented
 differently and ldconfig is not needed or used.
 
 <p>You should now be set up for Linux binaries which only need a
diff --git a/share/doc/handbook/lists.sgml b/share/doc/handbook/lists.sgml
index 4f086056a3fa..f8352c777a94 100644
--- a/share/doc/handbook/lists.sgml
+++ b/share/doc/handbook/lists.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: lists.sgml,v 1.4 1996/07/29 00:26:32 asami Exp $ -->
+<!-- $Id: lists.sgml,v 1.5 1996/09/22 15:40:20 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!-- 
@@ -9,7 +9,7 @@ note the use of single
 and double quotes.  
 -->
 
-<!ENTITY a.announce "FreeBSD announcments mailing list
+<!ENTITY a.announce "FreeBSD announcements mailing list
   <tt><htmlurl url='mailto:freebsd-announce@FreeBSD.ORG'
   name='&lt;freebsd-announce@FreeBSD.ORG&gt;'></tt>">
 
diff --git a/share/doc/handbook/porting.sgml b/share/doc/handbook/porting.sgml
index ba20343335ff..56bf0b79b32d 100644
--- a/share/doc/handbook/porting.sgml
+++ b/share/doc/handbook/porting.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.28 1996/08/28 06:40:49 asami Exp $ -->
+<!-- $Id: porting.sgml,v 1.29 1996/09/12 05:00:53 asami Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@@ -157,7 +157,7 @@ The pattern is the year followed by the month.
  # Date created:	5 December 1994
  # Whom:		asami
  #
- # $Id: porting.sgml,v 1.28 1996/08/28 06:40:49 asami Exp $
+ # $Id: porting.sgml,v 1.29 1996/09/12 05:00:53 asami Exp $
  #
  
  DISTNAME=	oneko-1.1b
@@ -174,7 +174,7 @@ The pattern is the year followed by the month.
       <p>See if you can figure it out.  Do not worry about the contents
 	of the <tt>&dollar;Id&dollar;</tt> line, it will be filled in
 	automatically by CVS when the port is imported to our main
-	ports tree.  You can find a more detalied example in the <ref
+	ports tree.  You can find a more detailed example in the <ref
 	id="porting:samplem" name="sample Makefile"> section.
 
       <sect3>
@@ -773,7 +773,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 	<enum>
 	  <item>If the port refers to the Motif library as
 	    `<tt>-lXm</tt>' in its Makefile or Imakefile, simply
-	    substitite `<tt>&dollar;{MOTIFLIB}</tt>' for it.
+	    substitute `<tt>&dollar;{MOTIFLIB}</tt>' for it.
 
 	  <item>If the port uses `<tt>XmClientLibs</tt>' in its
 	    Imakefile, change it to `<tt>&dollar;{MOTIFLIB}
@@ -1098,7 +1098,7 @@ lib/libtcl.so.7.3
   person who wrote this Makefile]
  # Whom:			Satoshi Asami <asami@FreeBSD.ORG>
  #
- # $Id: porting.sgml,v 1.28 1996/08/28 06:40:49 asami Exp $
+ # $Id: porting.sgml,v 1.29 1996/09/12 05:00:53 asami Exp $
  [ ^^^^ do not worry about this, I know it says "porting.sgml"...it
   will be automatically filled in by CVS when it is committed to our
   repository]
diff --git a/share/doc/handbook/ports.sgml b/share/doc/handbook/ports.sgml
index 7fb4d6f55f0e..25e2bebc263d 100644
--- a/share/doc/handbook/ports.sgml
+++ b/share/doc/handbook/ports.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: ports.sgml,v 1.12 1996/06/26 03:28:51 jfieber Exp $ -->
+<!-- $Id: ports.sgml,v 1.13 1996/08/13 19:51:36 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>The Ports collection<label id="ports"></heading>
@@ -392,7 +392,7 @@ Skipping over the next few lines for a minute, the line
 <verb>
  .include <bsd.port.mk> 
 </verb>
-says that the other statements and commmands 
+says that the other statements and commands 
 needed for this port are in a standard file called 
 `bsd.port.mk&quot;. As these are the same for all ports, there is
 no point in duplicating them all over the place, so they are kept in a
diff --git a/share/doc/handbook/printing.sgml b/share/doc/handbook/printing.sgml
index 46e93ac5b6dd..941d8ebb68f9 100644
--- a/share/doc/handbook/printing.sgml
+++ b/share/doc/handbook/printing.sgml
@@ -1,7 +1,7 @@
 <!-- This is an SGML document in the linuxdoc DTD describing
      Printing with FreeBSD.  By Sean Kelly, 1995.
 
-     $Id: printing.sgml,v 1.8 1996/08/12 16:07:50 jfieber Exp $
+     $Id: printing.sgml,v 1.9 1996/09/22 15:40:27 wosch Exp $
 
      The FreeBSD Documentation Project
 
@@ -3733,7 +3733,7 @@ total                     337.00  154   $  6.74
 	    To compute the dollar amount due, <tt/pac/ uses the
 	    <tt/pc/ capability in the <tt>/etc/printcap</tt> file
 	    (default of 200, or 2 cents per page).  Specify, in
-	    hundreths of cents, the price per page or per foot you
+	    hundredths of cents, the price per page or per foot you
 	    want to charge for printouts in this capability.  You can
 	    override this value when you run <tt/pac/ with the <tt/-p/
 	    option.  The units for the <tt/-p/ option are in dollars,
diff --git a/share/doc/handbook/scsi.sgml b/share/doc/handbook/scsi.sgml
index 15619f607ba4..41a283c4d9e3 100644
--- a/share/doc/handbook/scsi.sgml
+++ b/share/doc/handbook/scsi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: scsi.sgml,v 1.17 1996/08/12 11:48:48 peter Exp $ -->
+<!-- $Id: scsi.sgml,v 1.18 1996/08/18 17:04:41 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -94,7 +94,7 @@
 	stuff when you get that shiny 2Gb disk: I own a system on which a
 	pre-SCSI-1 disk, a SCSI-2 QIC tape unit, a SCSI-1 helical scan
 	tape unit and 2 SCSI-1 disks work together quite happily. From
-	a performance standpoint you might want to seperate your older
+	a performance standpoint you might want to separate your older
 	and newer (=faster) devices however.
 
     <sect2><heading>Components of SCSI</heading>
@@ -637,7 +637,7 @@ device          cd0     #Only need one of these, the code dynamically grows
           Experience has shown that some devices are slow to respond to INQUIRY 
 	  commands after a SCSI bus reset (which happens at boot time).
 	  An INQUIRY command is sent by the kernel on boot to see what
-	  kind of device (disk, tape, cdrom etc) is connected to a
+	  kind of device (disk, tape, CDROM etc) is connected to a
 	  specific target ID. This process is called device probing by the way.
 
 	  To work around the 'slow response' problem, FreeBSD allows a 
@@ -689,7 +689,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive  Viper 150 is a known rogue
 
 	  This scheme works fine, but keep in mind that it of course only
 	  works for devices that are KNOWN to be weird. If you are the first
-          to connect your bogus Mumbletech SCSI cdrom you might be the one
+          to connect your bogus Mumbletech SCSI CDROM you might be the one
 	  that has to define which workaround is needed.
 
 	  After you got your Mumbletech working, please send the required
@@ -707,7 +707,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive  Viper 150 is a known rogue
 
 	  This means that any devices with LUNs != 0 are not normally
 	  found during device probe on system boot. To work around this
-	  problem you must add an apropriate entry in /sys/scsi/scsiconf.c
+	  problem you must add an appropriate entry in /sys/scsi/scsiconf.c
 	  and rebuild your kernel.
 
 	  Look for a struct that is initialised like below:
diff --git a/share/doc/handbook/stable.sgml b/share/doc/handbook/stable.sgml
index 2a4e8a8ee85d..5df519428a80 100644
--- a/share/doc/handbook/stable.sgml
+++ b/share/doc/handbook/stable.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: stable.sgml,v 1.4 1996/07/09 07:29:14 jkh Exp $ -->
+<!-- $Id: stable.sgml,v 1.5 1996/08/09 05:11:43 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -10,7 +10,7 @@
 
                         THE FREEBSD STABLE POLICY 
 
-Last updated: $Date: 1996/07/09 07:29:14 $
+Last updated: $Date: 1996/08/09 05:11:43 $
 
 This document attempts to explain the rationale behind
 FreeBSD-stable, what you should expect should you decide to run it,
@@ -34,7 +34,7 @@ recent release (<htmlurl url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE"
 name="2.1.5-RELEASE"> at the time of this writing) since the <em>stable</em>
 branch is effectively a bug-fix stream relative to the previous release.
 
-<p>Please note that the <em>stable</em> tree endevors, above all, to
+<p>Please note that the <em>stable</em> tree endeavors, above all, to
 be fully compilable and stable at all times, but we do occasionally
 make mistakes (these are still active sources with quickly-transmitted
 updates, after all).  We also do our best to thoroughly test fixes in
@@ -47,7 +47,7 @@ next section).
 
     <p><enum><item> Join the &a.stable .  This will
     keep you informed of build-dependencies that may appear in
-    <em>stable</em> or any other issues requring special attention.
+    <em>stable</em> or any other issues requiring special attention.
     Developers will also make announcements in this mailing list when
     they are contemplating some contraversal fix or update, giving
     the users a chance to respond if they have any issues to raise concerning
diff --git a/share/doc/handbook/submitters.sgml b/share/doc/handbook/submitters.sgml
index 64f8cd4b324d..a4b6dafe4b0d 100644
--- a/share/doc/handbook/submitters.sgml
+++ b/share/doc/handbook/submitters.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: submitters.sgml,v 1.31 1996/08/03 13:46:00 jkh Exp $ -->
+<!-- $Id: submitters.sgml,v 1.32 1996/09/22 15:40:46 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
@@ -332,7 +332,7 @@ diff -c -r olddir newdir
 <p>In the case of a significant contribution of a large body
    work, or the addition of an important new feature to FreeBSD,
    it becomes almost always necessary to either send changes as
-   uuencoded tar files or upload them to our ftp site <url
+   uuencode'd tar files or upload them to our ftp site <url
    url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming">.
 
    When working with large amounts of code, the touchy subject of
@@ -395,7 +395,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-	$Id: submitters.sgml,v 1.31 1996/08/03 13:46:00 jkh Exp $
+	$Id: submitters.sgml,v 1.32 1996/09/22 15:40:46 wosch Exp $
 </verb></tscreen>
 For your convenience, a copy of this text can be found in
 <tt>/usr/share/examples/etc/bsd-style-copyright</tt>.
diff --git a/share/doc/handbook/synching.sgml b/share/doc/handbook/synching.sgml
index e94ad9a7211d..39c0ce937bfa 100644
--- a/share/doc/handbook/synching.sgml
+++ b/share/doc/handbook/synching.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: synching.sgml,v 1.1 1996/02/11 00:16:20 jkh Exp $ -->
+<!-- $Id: synching.sgml,v 1.2 1996/08/29 04:26:42 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Synchronizing source trees over the Internet<label id="synching"></heading>
@@ -7,7 +7,7 @@
 
 <!--
 
-Last updated: $Date: 1996/02/11 00:16:20 $
+Last updated: $Date: 1996/08/29 04:26:42 $
 
 This document tries to describe the various ways in which a user may
 use the internet to keep development sources in synch.
@@ -22,7 +22,7 @@ services we offer are CTM, SUP and CVSup (<bf>new</bf>).
 true, in fact, because each tool was originally designed to serve a
 different constituency and, although they have both undergone significant
 improvement since first going into service, they take fundamentally
-different approaches in trying to solve the source syncronization problem.
+different approaches in trying to solve the source synchronization problem.
 SUP was originally designed to support those who had dedicated (or at
 least fast) Internet connections whereas CTM was originally aimed at
 supporting those who's access was limited to email only.
@@ -44,7 +44,7 @@ far more efficient than SUP, and places less strain on our server resources
 since it's a <em>push</em> rather than a <em>pull</em> model.
 
 <p>There are other trade-offs, of course.  With SUP, you can also
-inadvertantly wipe out portions of your archive and SUP will detect
+inadvertently wipe out portions of your archive and SUP will detect
 and rebuild the damaged portions for you.  CTM won't do this, and if
 you wipe some portion of your source tree out (and don't have it backed
 up) then you will have to start from scratch (from the most recent CVS
@@ -57,7 +57,7 @@ development from a single CVS repository (which, in turn, can also be
 transferred non-destructively with CVSup - any local developer work on
 independant branches is preserved).  It overcomes many of SUP's shortcomings
 and may be <htmlurl url="ftp://freefall.freebsd.org/pub/CVSup/"
-name="downloaded"> from our development server, where additonal documentation
+name="downloaded"> from our development server, where additional documentation
 is also provided.  Both the CVSup client and server are compatible with
 the sup and supfilesrv distribution file formats.
 
diff --git a/share/doc/handbook/term.sgml b/share/doc/handbook/term.sgml
index 7b23969b2482..e2247f988bee 100644
--- a/share/doc/handbook/term.sgml
+++ b/share/doc/handbook/term.sgml
@@ -1,7 +1,7 @@
 <!-- This is an SGML document in the linuxdoc DTD describing
      hardwired terminals with FreeBSD.  By Sean Kelly, (c) 1996.
 
-     $Id: term.sgml,v 1.1 1996/07/29 07:15:57 jkh Exp $
+     $Id: term.sgml,v 1.2 1996/08/28 00:44:00 asami Exp $
 
      The FreeBSD Documentation Project
 
@@ -239,7 +239,7 @@
 	    <tt>/dev/ttyd1</tt>, and so forth.
 
 	    Note that you may have to configure your kernel to support
-	    each serial port, especially if you have a mutliport
+	    each serial port, especially if you have a multiport
 	    serial card.  See <ref name="Configuring the FreeBSD
 	    Kernel" id="kernelconfig"> for more information.