Avoid the use of contractions. This eliminates the "its"/"it's" problems

pointed out by Rick Robinson.  Found and fixed some grammar problems
at the same time.

Note: the reason for avoiding contractions is two-fold:

1) It makes the text easier to understand for people who speak English
   as a second language.
2) Expanding the contractions often reveals poorly worded passages.

17 files changed, 205 insertions, 205 deletions

diff --git a/share/doc/handbook/ctm.sgml b/share/doc/handbook/ctm.sgml
index c1a66d0..15ff1fc 100644
--- a/share/doc/handbook/ctm.sgml
+++ b/share/doc/handbook/ctm.sgml
@@ -3,7 +3,7 @@
 #
 # Converted by Ollivier Robert <roberto@FreeBSD.ORG>
 #
-# $Id: ctm.sgml,v 1.11 1996/08/17 23:51:44 wosch Exp $
+# $Id: ctm.sgml,v 1.12 1996/09/22 15:40:08 wosch Exp $
 #
 # ----------------------------------------------------------------------------
 # "THE BEER-WARE LICENSE" (Revision 42):
@@ -171,7 +171,7 @@
         If you are a frequent or valuable contributor to FreeBSD, I will be
         willing to arrange special services, one option is delivery via
         <tt/ftp/ or <tt/rcp/ to a machine closer to you.  You need to have
-        earned this, since it takes time to do, but I'll be all the more
+        earned this, since it takes time to do, but I will be all the more
         happy to do it for you then.
 
         There is a sequence of deltas for the <tt/ports/ collection too,
diff --git a/share/doc/handbook/current.sgml b/share/doc/handbook/current.sgml
index 117b586..dfb99d7 100644
--- a/share/doc/handbook/current.sgml
+++ b/share/doc/handbook/current.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: current.sgml,v 1.15 1996/08/15 01:21:57 asami Exp $ -->
+<!-- $Id: current.sgml,v 1.16 1996/09/09 23:21:27 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -10,7 +10,7 @@
 
                         THE FREEBSD CURRENT POLICY 
 
-Last updated: $Date: 1996/08/15 01:21:57 $
+Last updated: $Date: 1996/09/09 23:21:27 $
 
 This document attempts to explain the rationale behind
 FreeBSD-current, what you should expect should you decide to run it,
@@ -60,7 +60,7 @@ ask!  It takes far too much time to do this as a general task.
 <sect><heading>What is FreeBSD-current <em>NOT</em>?</heading>
 
 <p><enum>
-    <item>  A fast-track to getting pre-release bits because you heard there's
+    <item>  A fast-track to getting pre-release bits because you heard there is
         some cool new feature in there and you want to be the first on
         your block to have it.
 
diff --git a/share/doc/handbook/cvsup.sgml b/share/doc/handbook/cvsup.sgml
index 69c9a44..3d21da9 100644
--- a/share/doc/handbook/cvsup.sgml
+++ b/share/doc/handbook/cvsup.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: cvsup.sgml,v 1.1 1996/12/19 20:23:05 jkh Exp $ -->
+<!-- $Id: cvsup.sgml,v 1.2 1996/12/20 00:05:01 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>CVSup<label id="cvsup"></heading>
@@ -186,7 +186,7 @@ different tomorrow than it means today.
 <descrip>
   <tag/tag=./
     The main line of development, also known as FreeBSD-current.
-    Note:  the "." is not punctuation; it's the name of the tag.
+    Note:  the "." is not punctuation; it is the name of the tag.
   <tag/tag=RELENG_2_2/
     The line of development leading up to FreeBSD-2.2.
   <tag/tag=RELENG_2_1_0/
@@ -250,9 +250,9 @@ command line, with "-h hostname".
 <p><item>Where do you want to put them on your own machine?<label id="cvsup:config:dest">
 
 <p>The "prefix=" field tells cvsup where to put the files it receives.
-In this example, we'll put the source files directly into our main
+In this example, we will put the source files directly into our main
 source tree, "/usr/src".  The "src" directory is already implicit in the
-collections we've chosen to receive, so this is the correct
+collections we have chosen to receive, so this is the correct
 specification:
 
 <verb>
@@ -263,7 +263,7 @@ specification:
 
 <p>The cvsup client maintains certain status files in what is called
 the "base" directory.  These files help CVSup to work more
-efficiently, by keeping track of which updates you've already
+efficiently, by keeping track of which updates you have already
 received.  We will use the standard base directory,
 "/usr/local/etc/cvsup":
 
@@ -271,12 +271,12 @@ received.  We will use the standard base directory,
   *default base=/usr/local/etc/cvsup
 </verb>
 
-<p>This setting is used by default if it's not specified in the
-supfile, so we actually don't need the above line.
+<p>This setting is used by default if it is not specified in the
+supfile, so we actually do not need the above line.
 
-<p>If your base directory doesn't already exist, now would be a good
+<p>If your base directory does not already exist, now would be a good
 time to create it.  The cvsup client will refuse to run if the base
-directory doesn't exist.
+directory does not exist.
 
 <p><item>Miscellaneous supfile settings:
 
@@ -300,11 +300,11 @@ alone.
 
 <p>"use-rel-suffix" is ... arcane.  If you really want to know about
 it, see the cvsup(1) manual page.  Otherwise, just specify it and
-don't worry about it.
+do not worry about it.
 
 <p>"compress" enables the use of gzip-style compression on the
 communication channel.  If your network link is T1 speed or faster,
-you probably shouldn't use compression.  Otherwise, it helps
+you probably should not use compression.  Otherwise, it helps
 substantially.
 
 <p><item>Putting it all together:
@@ -332,7 +332,7 @@ quite simple:
   cvsup supfile
 </verb>
 
-<p>where "supfile" is of course the name of the supfile you've just created.
+<p>where "supfile" is of course the name of the supfile you have just created.
 Assuming you are running under X11, cvsup will display a GUI window with
 some buttons to do the usual things.  Press the "go" button, and watch
 it run.
@@ -357,10 +357,10 @@ for all file updates.  CVSup will examine your usual files in
 updates will instead land in "/var/tmp/dest/usr/src".  CVSup will also
 leave its base directory status files untouched when run this way.
 The new versions of those files will be written into the specified
-directory.  As long as you have read access to "/usr/src", you don't
+directory.  As long as you have read access to "/usr/src", you do not
 even need to be root to perform this kind of trial run.
 
-<p>If you are not running X11 or if you just don't like GUIs, you
+<p>If you are not running X11 or if you just do not like GUIs, you
 should add a couple of options to the command line when you run cvsup:
 
 <verb>
@@ -378,7 +378,7 @@ The default is 0, which means total silence except for error messages.
 type "cvsup -H".  For more detailed descriptions, see the manual page.
 
 <p>Once you are satisfied with the way updates are working, you can arrange
-for regular runs of cvsup using cron(8).  Obviously, you shouldn't let
+for regular runs of cvsup using cron(8).  Obviously, you should not let
 cvsup use its GUI when running it from cron.
 
 <sect1><heading>Announcements, Questions, and Bug Reports</heading>
diff --git a/share/doc/handbook/dialup.sgml b/share/doc/handbook/dialup.sgml
index 4f6381c..698aedb 100644
--- a/share/doc/handbook/dialup.sgml
+++ b/share/doc/handbook/dialup.sgml
@@ -1,6 +1,6 @@
 <!-- This is an SGML document in the linuxdoc DTD of the Tutorial for
      Configuring a FreeBSD for Dialup Services by Guy Helmer.
-     $Id: dialup.sgml,v 1.13 1996/08/15 20:52:18 mpp Exp $
+     $Id: dialup.sgml,v 1.14 1996/11/28 18:09:26 jfieber Exp $
 
 <!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
 
@@ -34,7 +34,7 @@ suggestions here.
 To begin with, the author assumes you have some basic knowledge of
 FreeBSD.  You need to have FreeBSD installed, know how to edit files
 in a UNIX-like environment, and how to look up manual pages on the
-system.  As discussed below, you'll need certain versions of FreeBSD,
+system.  As discussed below, you will need certain versions of FreeBSD,
 and knowledge of some terminology &amp; modem and cabling.
 
 <sect2><heading>FreeBSD Version</heading>
@@ -140,7 +140,7 @@ modem's reference book or user's guide handy.  Sample commands for USR
 Sportster 14,400 external modems will be given, which you may be able
 to use as a reference for your own modem's commands.
 
-Lastly, you'll need to know how to setup your modem so that it will
+Lastly, you will need to know how to setup your modem so that it will
 work well with FreeBSD.  Like other UNIX-like operating systems,
 FreeBSD uses the hardware signals to find out when a call has been
 answered or a line has been hung up and to hangup and reset the modem
@@ -590,7 +590,7 @@ stty -f /dev/ttyd3 crtscts
 
 Since there is no initialization device special file on FreeBSD
 1.1, one has to just set the flags on the sole device special file and
-hope the flags aren't cleared by a miscreant.
+hope the flags are not cleared by a miscreant.
 
 <sect1><heading>Modem Settings</heading>
 <p>
diff --git a/share/doc/handbook/firewalls.sgml b/share/doc/handbook/firewalls.sgml
index bc65850..58a70c1 100644
--- a/share/doc/handbook/firewalls.sgml
+++ b/share/doc/handbook/firewalls.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: firewalls.sgml,v 1.13 1996/09/15 00:15:33 alex Exp $ -->
+<!-- $Id: firewalls.sgml,v 1.14 1996/10/04 22:54:01 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Firewalls<label id="firewalls"></heading>
@@ -513,7 +513,7 @@ machine. The upper limit as defined by RFC 1700 (Assigned Numbers) is
 6063.
 
  <item>Check what ports any internal servers use (e.g. SQL servers,
-etc). It's probably a good idea to block those as well, as they
+etc). It is probably a good idea to block those as well, as they
 normally fall outside the 1-1024 range specified above.
 
 </itemize>
diff --git a/share/doc/handbook/hw.sgml b/share/doc/handbook/hw.sgml
index 85bd554..19444dc 100644
--- a/share/doc/handbook/hw.sgml
+++ b/share/doc/handbook/hw.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: hw.sgml,v 1.56 1996/12/27 08:09:52 obrien Exp $ -->
+<!-- $Id: hw.sgml,v 1.57 1996/12/27 08:48:17 obrien Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -33,7 +33,7 @@
 
 <sect><heading>Resources on the Internet</heading>
 <p>The following links have proven useful in selecting hardware.
-Though some of what you see won't necessarily be specific (or even
+Though some of what you see will not necessarily be specific (or even
 applicable) to FreeBSD, most of the hardware information out there
 is OS independent.  Please check with the FreeBSD hardware guide
 to make sure that your chosen configuration is supported before
@@ -55,7 +55,7 @@ Slippery when wet.  Beware of dog.
 
  <sect1><heading>Jordan's Picks</heading>
     <p>I have had fairly good luck building workstation and server
-    configurations with the following components.  I can't guarantee that
+    configurations with the following components.  I can not guarantee that
     you will too, nor that any of the companies here will remain "best buys"
     forever.  I will try, when I can, to keep this list up-to-date but
     cannot obviously guarantee that it will be at any given time.
@@ -69,7 +69,7 @@ Slippery when wet.  Beware of dog.
     below) have largely supplanted them.  If you buy one of these boards,
     be also sure to get it with the
     <htmlurl url="http://asustek.asus.com.tw/Products/TB/mem-0002.html"
-    name="pipelined burst cache module">.  If you're looking for a 486 class
+    name="pipelined burst cache module">.  If you are looking for a 486 class
     motherboard, you might also investigate ASUS's
     <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pvi-486sp3.txt"
     name="486SP3G"> offering (Note:  These have become increasingly hard to
@@ -81,11 +81,11 @@ Slippery when wet.  Beware of dog.
     parity logic, making it almost impossible to detect when a memory error
     has occurred.  Those wishing to build more fault-tolerant systems should
     therefore buy one of the newer Triton II based motherboards, which offer
-    both better performance, parity checking and ECC.  I'm also told that
+    both better performance, parity checking and ECC.  I am also told that
     if you are using ECC memory, be sure to get a motherboard with uses the
-    A2 or later steppings of the 82439HX Triton-II chipset.  Don't get this
+    A2 or later steppings of the 82439HX Triton-II chipset.  Do not get this
     confused with the 82371SB stepping - you have an A2 stepping if the
-    82439HX chip has a marking of "SU102."  You have an A1 stepping if it's
+    82439HX chip has a marking of "SU102."  You have an A1 stepping if it is
     not marked with an S-number or if the number is "SU087."
 
     <p>At the even higher end, the Intel/Venus Pro (<ref id="hw:mb:pci"
@@ -98,9 +98,9 @@ Slippery when wet.  Beware of dog.
 
     NOTE: The Intel motherboards are designed to a different form-factor
     and hence require <em>an entirely different PC case</em>, the so-called
-    "ATX" case design.  Consider this fact carefully if you're thinking of
+    "ATX" case design.  Consider this fact carefully if you are thinking of
     upgrading an existing system - all the commonly available ATX cases
-    I've seen so far have been in the "midi-tower" class, with limited space
+    I have seen so far have been in the "mid-tower" class, with limited space
     for drives or other internal peripherals available.  On the plus side,
     most ATX cases appear to be of much higher quality than their typical PC
     counterparts.
@@ -118,7 +118,7 @@ Slippery when wet.  Beware of dog.
     controllers (and internal busses) in a single slot.
 
   <sect2><heading>Disk drives</heading>
-    <p>In this particular game of Russian roulette, I'll make few specific
+    <p>In this particular game of Russian roulette, I will make few specific
     recommendations except to say "SCSI over IDE whenever you can afford it."
     Even in small desktop configurations, SCSI often makes more sense since it
     allows you to easily migrate drives from server to desktop as falling drive
@@ -127,18 +127,18 @@ Slippery when wet.  Beware of dog.
     food chain!
 
     <p>I do not currently see SCSI WIDE drives as a necessary expense unless
-    you're putting together an NFS or NEWS server that will be doing a lot
+    you are putting together an NFS or NEWS server that will be doing a lot
     of multiuser disk I/O.  
 
   <sect2><heading>CDROM drives</heading>
     <p>My SCSI preferences extend to SCSI CDROM drives as well, and while
     the <htmlurl url="http://www.toshiba.com" name="Toshiba"> XM-3501B (also
     released in a caddy-less model called the XM-5401B) drive has always
-    performed well for me, I'm now a great fan of the <htmlurl
-    url="http://www.plextor.com" name="Plextor"> PX-12CS drive.  It's
+    performed well for me, I am now a great fan of the <htmlurl
+    url="http://www.plextor.com" name="Plextor"> PX-12CS drive.  It is
     a 12 speed drive with excellent performance and reliability.
 
-    <p>Generally speaking, most SCSI CDROM drives I've seen have been of
+    <p>Generally speaking, most SCSI CDROM drives I have seen have been of
     pretty solid construction and you probably won't go wrong with an HP or
     NEC SCSI CDROM drive either.  SCSI CDROM prices also appear to have
     dropped considerably in the last few months and are now quite competitive
@@ -160,14 +160,14 @@ Slippery when wet.  Beware of dog.
     HP4020i CDR.
 
   <sect2><heading>Tape drives</heading>
-   <p>I've had pretty good luck with both
+   <p>I have had pretty good luck with both
    <htmlurl url="http://www.Exabyte.COM:80/Products/8mm/8505XL/Rfeatures.html"
    name="8mm drives"> from <htmlurl url="http://www.exabyte.com"
    name="Exabyte"> and 
    <htmlurl url="http://www-dmo.external.hp.com:80/tape/_cpb0001.htm" 
    name="4mm (DAT)"> drives from <htmlurl url="http://www.hp.com" name="HP">.
    
-   <p>For backup purposes, I'd have to give the higher recommendation to the
+   <p>For backup purposes, I would have to give the higher recommendation to the
    Exabyte due to the more robust nature (and higher storage capacity) of
    8mm tape.
 
@@ -177,7 +177,7 @@ Slippery when wet.  Beware of dog.
     can heartily recommend the <htmlurl url="http://www.matrox.com/"
     name="Matrox"> <htmlurl url="http://www.matrox.com/mgaweb/brochure.htm"
     name="Millenium"> card,  If free X servers are more to your
-    liking, you certainly can't go wrong with one of <htmlurl url="http://www.nine.com/" name="Number 9's"> cards - their S3 Vision 868 and 968 based cards 
+    liking, you certainly ca not go wrong with one of <htmlurl url="http://www.nine.com/" name="Number 9's"> cards - their S3 Vision 868 and 968 based cards 
     (the 9FX series) are pretty fast cards as well, and are supported by
     <htmlurl url="http://www.xfree86.org" name="XFree86">'s S3 server.
 
@@ -186,7 +186,7 @@ Slippery when wet.  Beware of dog.
     name="Sony Multiscan 17SE monitors">, as have I with 
     the Viewsonic offering in the same (trinitron) tube.  For larger than
     17", all I can recommend at the time of this writing is to not spend
-    any less than U.S. &dollar;2,500 for a 21" monitor if that's what you really
+    any less than U.S. &dollar;2,500 for a 21" monitor if that is what you really
     need.  There are good monitors available in the >=20" range and there
     are also cheap monitors in the >=20" range.  Unfortunately, none are
     both cheap and good!
@@ -201,13 +201,13 @@ Slippery when wet.  Beware of dog.
     SMC SMC9332DST 10/100MB or Intel EtherExpress Pro/100B cards will do
     a fine job.
 
-    If what you're looking for is, on the other hand, the cheapest possible
+    If what you are looking for is, on the other hand, the cheapest possible
     solution which will still work reasonably well, then almost any NE2000
     clone is a good choice.
 
 
    <sect2><heading>Serial</heading>
-    <p>If you're looking for high-speed serial networking solutions, then
+    <p>If you are looking for high-speed serial networking solutions, then
     <htmlurl url="http://www.dgii.com/" name="Digi International">
     makes the <htmlurl url="http://www.dgii.com/prodprofiles/profiles-prices/digiprofiles/digispecs/sync570.html" name="SYNC/570"> series, with drivers now in
     FreeBSD-current. <htmlurl url="http://www.etinc.com"
@@ -218,9 +218,9 @@ Slippery when wet.  Beware of dog.
     said that FreeBSD's support for <htmlurl url="http://www.cyclades.com/"
     name="Cyclades">'s products is probably the tightest, primarily as a result
     of that company's commitment to making sure that we are adequately supplied
-    with evaluation boards and technical specs.  I've heard that the Cyclom-16Ye
-    offers the best price/performance, though I've not checked the prices lately.
-    Other multiport cards I've heard good things about are the BOCA and AST
+    with evaluation boards and technical specs.  I have heard that the Cyclom-16Ye
+    offers the best price/performance, though I have not checked the prices lately.
+    Other multiport cards I have heard good things about are the BOCA and AST
     cards, and <htmlurl url="http://www.stallion.com/" name="Stallion
     Technologies"> apparently offers an unofficial driver for their 
     cards at <htmlurl url="ftp://ftp.stallion.com/drivers/unsupported/freebsd/stalbsd-0.0.4.tar.gz" name="this"> location.
@@ -229,12 +229,12 @@ Slippery when wet.  Beware of dog.
     <p>I currently use the <htmlurl url="http://www.gravis.com/" name="Gravis">
     Ultrasound MAX due to its high sound quality and full-duplex audio
     capabilities (dual DMA channels).  Support for Windows NT and OS/2 is
-    fairly anemic, however, so I'm not sure that I can recommend it as an
+    fairly anemic, however, so I am not sure that I can recommend it as an
     all-around card for a machine that will be running both FreeBSD and NT
     or OS/2.  In such a scenario, I might recommend the <htmlurl url="http://www.creaf.com/" name="Creative Labs"> AWE32 instead.
 
    <sect2><heading>Video</heading>
-   <p>For video capture, there's really only once choice - the
+   <p>For video capture, there is really only once choice - the
    <htmlurl url="http://www.matrox.com/" name="Matrox">
    <htmlurl url="http://www.matrox.com/imgweb/meteor.htm" name="Meteor">
    card.  FreeBSD also supports the older video spigot card from
@@ -301,9 +301,9 @@ Slippery when wet.  Beware of dog.
 		this chipset have been favorable so far.  Although, some
 		have said that if you are using ECC memory, be sure to get a
 		motherboard with the A2 or later steppings of the 82439HX
-		Triton-II chipset.  Don't get this confused with the 82371SB
+		Triton-II chipset.  Do not get this confused with the 82371SB
 		stepping - you have an A2 stepping if the 82439HX chip has a
-		marking of "SU102".  You have an A1 stepping if it's not
+		marking of "SU102".  You have an A1 stepping if it is not
 		marked with an S-number or if the number is "SU087".
 
 	      <tag>430VX <em>(often mistakenly called Triton-III)</em>:</tag>
@@ -363,7 +363,7 @@ Slippery when wet.  Beware of dog.
 
 	 *  The Pentium 100 can be run at either 50MHz external clock with
 	    a multiplier of 2 or at 66MHz and a multiplier of 1.5.
-	 ** 66 Mhz may actually be 66.667 MHz, but don't assume so.
+	 ** 66 Mhz may actually be 66.667 MHz, but do not assume so.
        </verb></tscreen>
        <p>As can be seen the best parts to be using are the 100, 133, 166
          and 200, with the exception that at a mulitplier of 3 the CPU
@@ -847,7 +847,7 @@ drive supports hardware data compression
 <htmlurl url="http://www.dmo.hp.com/tape/sst5000.htm" name=
 "5000eU"> and <htmlurl
 url="http://www.dmo.hp.com/tape/sst5000.htm" name="5000i"> tape
-drives and C35480A DDS format DAT drive..
+drives and C35480A DDS format DAT drive.
 	<p>This drive will occasionally hang during a tape eject
 operation (<tt>mt offline</tt>).  Pressing the front panel button
 will eject the tape and bring the tape drive back to life.
diff --git a/share/doc/handbook/install.sgml b/share/doc/handbook/install.sgml
index fb887b0..ee6fcde 100644
--- a/share/doc/handbook/install.sgml
+++ b/share/doc/handbook/install.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: install.sgml,v 1.43 1996/12/19 21:39:07 jkh Exp $ -->
+<!-- $Id: install.sgml,v 1.44 1996/12/21 15:01:07 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -66,8 +66,8 @@ C:\> rawrite
 	    will only successfully support rawrite.exe in DOS mode
 	    and that Windows NT prevents it from working at all.  You
 	    will have to make your floppy images on a different machine
-	    if you're running Windows NT and boot first into DOS mode if
-	    you're running Windows95.</p></item>
+	    if you are running Windows NT and boot first into DOS mode if
+	    you are running Windows95.</p></item>
 
 	  <item>If you are using a UNIX system:
 <tscreen>
@@ -729,7 +729,7 @@ ftp://foo.bar.com:1234/pub/FreeBSD
 	    you through a typical installation, give you a high degree of
 	    control over each step of the installation or simply whizz
 	    through it (using reasonable defaults when possible) as fast
-	    as possible.  If you've never used FreeBSD before then the
+	    as possible.  If you have never used FreeBSD before then the
 	    Novice installation method is most recommended.
 
 	  <item>The final configuration menu choice allows you to
diff --git a/share/doc/handbook/isdn.sgml b/share/doc/handbook/isdn.sgml
index 6d53fe3..9f73139 100644
--- a/share/doc/handbook/isdn.sgml
+++ b/share/doc/handbook/isdn.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: isdn.sgml,v 1.7 1996/12/08 22:24:10 wosch Exp $-->
+<!-- $Id: isdn.sgml,v 1.8 1996/12/16 22:50:31 mpp Exp $-->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>ISDN<label id="isdn"></heading>
@@ -152,7 +152,7 @@ interchangeably.
 <p>As the cost of low end ISDN routers/bridges comes down, it will
 likely become a more and more popular choice.  An ISDN router is a small
 box that plugs directly into your local Ethernet network(or card), and
-manages it's own connection to the other bridge/router.  It has all the
+manages its own connection to the other bridge/router.  It has all the
 software to do PPP and other protocols built in.
 
 A router will allow you much faster throughput that a standard TA, since
@@ -181,7 +181,7 @@ AUI/10BT transceiver, if necessary.
 |
 ---FreeBSD box
 |
----Windows 95 (Don't admit to owning it)
+---Windows 95 (Do not admit to owning it)
 |
 Standalone router
    |
diff --git a/share/doc/handbook/kernelconfig.sgml b/share/doc/handbook/kernelconfig.sgml
index 72b46c9..625acf8 100644
--- a/share/doc/handbook/kernelconfig.sgml
+++ b/share/doc/handbook/kernelconfig.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kernelconfig.sgml,v 1.22 1996/12/16 22:33:35 mpp Exp $ -->
+<!-- $Id: kernelconfig.sgml,v 1.23 1996/12/23 12:20:03 joerg Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
   <chapt><heading>Configuring the FreeBSD Kernel<label id="kernelconfig"></heading>
@@ -86,7 +86,7 @@
 	``permission denied'' errors.</quote>
 
 	Now, edit MYKERNEL with your favorite text editor.  If
-	you're just starting out, the only editor available will
+	you are just starting out, the only editor available will
 	probably be <tt>vi</tt>, which is too complex to explain
 	here, but is covered well in many books in the <ref
 	id="bibliography" name="bibliography">.  Feel free to change the
diff --git a/share/doc/handbook/kernelopts.sgml b/share/doc/handbook/kernelopts.sgml
index 88faf63..2255082 100644
--- a/share/doc/handbook/kernelopts.sgml
+++ b/share/doc/handbook/kernelopts.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kernelopts.sgml,v 1.1 1996/12/23 12:20:04 joerg Exp $ -->
+<!-- $Id: kernelopts.sgml,v 1.2 1996/12/26 22:08:11 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
 
@@ -20,7 +20,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   after running <tt/config(8)/, the build process will automatically
   pick up modified options, and only recompile those files where it is
   necessary.  Wiping out the old compile directory on each run of
-  <tt/config(8)/ as it's still done now can then be eliminated again.
+  <tt/config(8)/ as it is still done now can then be eliminated again.
 
   <p>Basically, a kernel option is nothing else than the definition of
   a C preprocessor macro for the kernel compilation process.  To make
@@ -41,7 +41,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   must be a valid C expression in whatever context the default value
   would have been used.
 
-  <p>It's also possible to create value-less options that simply
+  <p>It is also possible to create value-less options that simply
   enable or disable a particular piece of code by embracing it in
 
 <verb>
@@ -57,7 +57,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
 
   <p>People familiar with the C language will immediately recognize
   that everything could be counted as a ``config option'' where
-  there's at least a single <tt/#ifdef/ referencing it...  Now only
+  there is at least a single <tt/#ifdef/ referencing it...  Now only
   few people probably would try to say
 
 <verb>
@@ -67,7 +67,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   fall over. :-)
 
   <p>Apparently, using arbitrary names for the options makes it very
-  hard to track their usage throughout the kernel source tree.  That's
+  hard to track their usage throughout the kernel source tree.  That is
   the rationale behind the <em/new-style/ option scheme, where each
   option goes into a separate <tt/.h/ file in the kernel compile
   directory, which is by convention named <tt>opt_<em>foo</em>.h</tt>.
@@ -77,9 +77,9 @@ id="kernelconfig" name="kernel configuration"> before reading here.
 
   <p>The old-style option mechanism still has one advantage for local
   options or maybe experimental options that have a short anticipated
-  lifetime: since it's easy to add a new <tt/#ifdef/ to the kernel
-  source, this already made it a kernel config option, so that's
-  already all about it.  In this case, the administrator using such an
+  lifetime: since it is easy to add a new <tt/#ifdef/ to the kernel
+  source, this has already made it a kernel config option.
+  In this case, the administrator using such an
   option is responsible himself for knowing about its implications
   (and maybe manually forcing the recompilation of parts of his
   kernel).  Once the transition of all supported options has been
@@ -96,7 +96,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   <tt>opt_<em>foo</em>.h</tt> file where your new option would best go
   into.
 
-  <p>If there's already something that comes close to the purpose of
+  <p>If there is already something that comes close to the purpose of
   the new option, pick this.  For example, options modifying the
   overall behaviour of the SCSI subsystem can go into <tt/opt_scsi.h/.
   By default, simply mentioning an option in the appropriate option
@@ -104,7 +104,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   corresponding file <tt/opt_foo.h/.  This can be overridden on the
   right-hand side of a rule by specifying another filename.
 
-  <p>If there's no <tt>opt_<em>foo</em>.h</tt> already available for
+  <p>If there is no <tt>opt_<em>foo</em>.h</tt> already available for
   the intended new option, invent a new name.  Make it meaningful, and
   comment the new section in the
   <tt>options[<em>.&lt;arch&gt;</em>]</tt> file.  <tt/config(8)/ will
@@ -116,7 +116,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   rebuilt when one of the options has been changed in the config file.
 
   <p>Finally, find out which kernel files depend on the new option.
-  Unless you've just invented your option, so it doesn't exist
+  Unless you have just invented your option, and it dos not exist
   anywhere yet,
 
 <verb>
@@ -144,6 +144,6 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   (i. e., a file sitting in <tt>/usr/include/sys/</tt>) is almost
   always a mistake.  <tt>opt_<em>foo</em>.h</tt> cannot be included
   into those files since it would break the headers more seriously,
-  but if it isn't included, then places that include it may get an
+  but if it is not included, then places that include it may get an
   inconsistent value for the option.  Yes, there are precedents for
-  this right now, but that doesn't make them more correct.
+  this right now, but that does not make them more correct.
diff --git a/share/doc/handbook/linuxemu.sgml b/share/doc/handbook/linuxemu.sgml
index 3ce539b..074d455b 100644
--- a/share/doc/handbook/linuxemu.sgml
+++ b/share/doc/handbook/linuxemu.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: linuxemu.sgml,v 1.12 1996/10/04 22:54:07 wosch Exp $ -->
+<!-- $Id: linuxemu.sgml,v 1.13 1996/10/05 18:36:18 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Linux Emulation<label id="linuxemu"></heading>
@@ -195,7 +195,7 @@ general this does not seem to be a problem.
 
 <sect2><heading>Installing libraries manually</heading>
 
-<p>If you don't have the ``ports'' distribution, you can install the
+<p>If you do not have the ``ports'' distribution, you can install the
 libraries by hand instead.  You will need the Linux shared libraries
 that the program depends on and the runtime linker.  Also, you will
 need to create a "shadow root" directory, /compat/linux, for Linux
@@ -521,7 +521,7 @@ slakware/x9/xf_lib.tgz
 
 <p>Extract the files from these gzipped tarfiles in your
 /compat/linux directory (possibly omitting or afterwards
-removing files you don't need), and you are done.
+removing files you do not need), and you are done.
 
 <p><bf>See also:</bf>
 <verb>
@@ -582,12 +582,12 @@ richc.isdn.bcm.tmc.edu   9845-03452-90255
 </tscreen>
 So, for example, the `machine ID' of `richc' is `9845-03452-90255'.
 You can ignore the message about the ioctl that is not
-implemented.  It won't prevent Mathematica from running
+implemented.  It will not prevent Mathematica from running
 in any way and you can safely ignore it, though you
 will see the message every time you run Mathematica.
 
 <p>When you register with Wolfram, either by email, phone
-or fax, you'll give them the 'machine ID' and they will
+or fax, you will give them the 'machine ID' and they will
 respond with a corresponding password consisting of
 groups of numbers.  You need to add them both along
 with the machine name and license number in your
@@ -602,7 +602,7 @@ You can do this by invoking:
 </tscreen>
 It will ask you to enter your license number and the
 Wolfram supplied password.  If you get them mixed up or
-for some reason the math.install fails, That's OK,
+for some reason the math.install fails, That is OK,
 because you can simply edit the file 'mathpass' in this
 same directory to correct the info manually.
 
@@ -612,7 +612,7 @@ you want to use your own.  If you are like us and
 distrust all install programs, you probably want to
 specify the actual directories.  Beware.  Although the
 math.install program asks you to specify directories,
-it won't create them for you, so you should perhaps
+it will not create them for you, so you should perhaps
 have a second window open with another shell so that
 you can create them before you give them to the install
 program.  Or, if it fails, you
@@ -636,8 +636,8 @@ go.
 as the X Front End, and you have to install it separately.
 To get the X Front End stuff correctly installed, cd
 into the /usr/local/Mathematica/FrontEnd directory and
-executed the ./xfe.install shell script.  You'll have
-to tell it where to put things, but you don't have to
+executed the ./xfe.install shell script.  You will have
+to tell it where to put things, but you do not have to
 create any directories because it uses all the same
 directories that had been created for math.install.
 When it finished, there should be a new shell script in
@@ -651,7 +651,7 @@ Mathematica has installed.  At the beginning of every shell script in
 XKEYSYMDB=/usr/local/Mathematica/lib/X11/XKeysymDB; export XKEYSYMDB
 </verb>
 </tscreen>
-This tells Mathematica were to find it's own version of the key
+This tells Mathematica were to find its own version of the key
 mapping file XKeysymDB.  Without this you will get pages of error
 messages about missing key mappings.
 
@@ -662,7 +662,7 @@ RESOLV_HOST_CONF=/compat/linux/etc/host.conf; export RESOLV_HOST_CONF
 </verb>
 </tscreen>
 This tells Mathematica to use the linux version of host.conf.  This
-file has a different syntax from FreeBSD's host.conf, so you'll get an
+file has a different syntax from FreeBSD's host.conf, so you will get an
 error message about /etc/host.conf if you leave this out.
 
 <p>You might want to also modify your /etc/manpath.config file
@@ -670,11 +670,11 @@ to read the new man directory, and you may need to edit your
 ~/.cshrc file to add /usr/local/Mathematica/bin
 to your path.
 
-<p>That's about all it takes, With this you should be able
+<p>That is about all it takes, With this you should be able
 to type "mathematica" and get a really slick looking
 Mathematica Notebook screen up.  Mathematica has included
-the Motif user interfaces, but it's compiled in statically,
-so you don't need the Motif libraries.  Good luck doing this
+the Motif user interfaces, but it is compiled in statically,
+so you do not need the Motif libraries.  Good luck doing this
 yourself!
 
 <sect1><heading>Bugs</heading>
@@ -687,7 +687,7 @@ File .../Untitled-1.mb appears to be broken for OMPR.257.0
 </verb>
 </tscreen>
 
-We haven't found the cause for this, but it only affects the
+We have not found the cause for this, but it only affects the
 Notebook's X Window front end, not the mathematica engine itself.  So
 the command line interface invoked by 'math' is unaffected by this
 bug.
diff --git a/share/doc/handbook/mail.sgml b/share/doc/handbook/mail.sgml
index 7e26587..bac06b1 100644
--- a/share/doc/handbook/mail.sgml
+++ b/share/doc/handbook/mail.sgml
@@ -1,4 +1,4 @@
-<!--  $Id: mail.sgml,v 1.2 1996/11/30 23:35:43 mpp Exp $
+<!--  $Id: mail.sgml,v 1.3 1996/12/16 22:13:10 max Exp $
       The FreeBSD Documentation Project
 
 <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
@@ -130,7 +130,7 @@ domain foo.bar.edu
 	<p>
 	  This is answered in the sendmail FAQ as follows:-
 	  <verb>
-          * I'm getting "Local configuration error" messages, such as:
+          * I am getting "Local configuration error" messages, such as:
 
           553 relay.domain.net config error: mail loops back to myself
           554 <user@domain.net>... Local configuration error
@@ -139,7 +139,7 @@ domain foo.bar.edu
 
           You have asked mail to the domain (e.g., domain.net) to be
           forwarded to a specific host (in this case, relay.domain.net)
-          by using an MX record, but the relay machine doesn't recognize
+          by using an MX record, but the relay machine does not recognize
           itself as domain.net.  Add domain.net to /etc/sendmail.cw
           (if you are using FEATURE(use_cw_file)) or add "Cw domain.net"
           to /etc/sendmail.cf.
diff --git a/share/doc/handbook/policies.sgml b/share/doc/handbook/policies.sgml
index 1c3197d..2069a0b 100644
--- a/share/doc/handbook/policies.sgml
+++ b/share/doc/handbook/policies.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: policies.sgml,v 1.7 1996/12/10 05:54:31 asami Exp $ -->
+<!-- $Id: policies.sgml,v 1.8 1996/12/10 10:02:48 obrien Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Source Tree Guidelines and Policies
@@ -124,7 +124,7 @@ remaining files shall <em>not</em> be removed.
 dist tree automatically by some utility, something which would
 hopefully make it even easier to upgrade to a new version.  If this
 is done, be sure to check in such utilities (as necessary) in the
-src/tools directory along with the port itself so that it's available
+src/tools directory along with the port itself so that it is available
 to future maintainers.
 
 <p>In the src/contrib/tcl level directory, a file called README.FreeBSD
diff --git a/share/doc/handbook/ports.sgml b/share/doc/handbook/ports.sgml
index dd1d0b2..7131b7e 100644
--- a/share/doc/handbook/ports.sgml
+++ b/share/doc/handbook/ports.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: ports.sgml,v 1.17 1996/11/11 06:50:45 asami Exp $ -->
+<!-- $Id: ports.sgml,v 1.18 1996/12/21 11:51:33 max Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>The Ports collection<label id="ports"></heading>
@@ -10,7 +10,7 @@ wide range of applications with a minimum of effort.
 
 <p> For all the hype about open standards, getting a program to work
 on different versions of Unix in the real world can be a tedious and
-tricky business, as anyone who's tried it will know. You may be lucky
+tricky business, as anyone who has tried it will know. You may be lucky
 enough to find that the program you want will compile cleanly on your
 system, install itself in all the right places and run flawlessly
 ``out of the box'', but this is unfortunately rather rare. With most
@@ -21,7 +21,7 @@ greying, or even chronic alopecia...
 <p> Some software distributions have attacked this problem by
 providing configuration scripts. Some of these are very clever, but
 they have an unfortunate tendency to triumphantly announce that your
-system is something you've never heard of and then ask you lots of
+system is something you have never heard of and then ask you lots of
 questions that sound like a final exam in system-level Unix
 programming (``Does your system's gethitlist function return a const
 pointer to a fromboz or a pointer to a const fromboz? Do you have
@@ -34,23 +34,23 @@ working program.
 <sect1><heading>Why have a Ports Collection?</heading>
 
 <p>The base FreeBSD system comes with a very wide range of tools and
-system utilities, but a lot of popular programs aren't in the base
+system utilities, but a lot of popular programs are not in the base
 system, for good reasons:-
 
 <enum>
-<item>``I can't live without x y and z on my system'' type programs
+<item>``I can not  live without x y and z on my system'' type programs
 (eg a certain Lisp-based editor, or the mtools set of programs for
-dealing with DOS floppy disks), because it's too subjective (many
-people can't stand Emacs and/or never use DOS floppies and seem none
+dealing with DOS floppy disks), because it is too subjective (many
+people can not stand Emacs and/or never use DOS floppies and seem none
 the worse for it).
 
 <item>Too specialised to put in the base system (CAD, databases).
 
-<item>Programs which fall into the ``I wouldn't mind having a look at
+<item>Programs which fall into the ``I wouldn not mind having a look at
 that when I get a spare minute'' category, rather than system-critical
 ones (some languages, perhaps).
 
-<item>``Wow fab this is way cool'' fun type programs that couldn't
+<item>``Wow fab this is way cool'' fun type programs that could not
 possibly be supplied with a serious operating system like FreeBSD ;-)
 
 <item>However many programs you put in the base system, people will
@@ -94,17 +94,17 @@ url="ftp://www.freebsd.org/pub/FreeBSD/ports/shells/bash" name="the
 FTP site">) and expect to find all sorts of pointy-headed rocket
 science lurking there, you may be disappointed by the one or two
 rather unexciting-looking files and directories you find there.
-(We'll discuss in a minute how to go about <ref id="ports:getting"
+(We will discuss in a minute how to go about <ref id="ports:getting"
 name="Getting a port">).
 
 <p>``How on earth can this do anything?'' I hear you cry. ``There
-isn't even any source code there!''
+is not even any source code there!''
 
 <p> Fear not, gentle reader, all will become clear (hopefully). Let's
-see what happens if we try and install a port. I've chose `bash', also
+see what happens if we try and install a port. I have chosen `bash', also
 known as the Bourne-Again Shell, as that seems fairly typical.
 
-<em>Note</em> if you're trying this at home, you'll need to be root.
+<em>Note</em> if you are trying this at home, you will need to be root.
 
 <verb>
  # cd /usr/ports/shells/bash
@@ -133,30 +133,30 @@ known as the Bourne-Again Shell, as that seems fairly typical.
  ===>  Registering installation for bash-1.14.5
 </verb>
 
-<p> To avoid confusing the issue, I've slightly pruned the install
+<p> To avoid confusing the issue, I have slightly pruned the install
 output, as well as completely removing the build output. If you tried
 this yourself, you may well have got something like this at the start:-
 
 <label id="ports:fetch">
 <verb>
- >> bash-1.14.5.tar.gz doesn't seem to exist on this system.
+ >> bash-1.14.5.tar.gz does not seem to exist on this system.
  >> Attempting to fetch from ftp://slc2.ins.cwru.edu/pub/dist/.
 </verb>
 
-<p> The `make' program has noticed that you didn't have a local copy
+<p> The `make' program has noticed that you did not have a local copy
 of the source code and tried to FTP it down so it could get the job
 done (are you starting to feel impressed? 8-)). I already had the
-source handy in my example, so it didn't need to fetch it.
+source handy in my example, so it did not need to fetch it.
 
 <p> Let's go through this and see what the `make' program was doing.
 
 <enum>
 <item> Locate the source code <ref id="ports:tarball"
-name="tarball."> If it's not available locally, try to grab it from an
+name="tarball."> If it is not available locally, try to grab it from an
 FTP site.
 
 <item> Run a <ref id="ports:checksum" name="checksum"> test on the
-tarball to make sure it hasn't been tampered with, accidentally
+tarball to make sure it has not been tampered with, accidentally
 truncated, struck by neutrinos while in transit, etc.
 
 <item> Extract the tarball into a temporary work directory.
@@ -170,19 +170,19 @@ correctly answer any questions it asks.
 <item> (Finally!) Compile the code.
 
 <item> Install the program executable and other supporting files, man
-pages, etc. under the /usr/local hierarchy, where they won't get mixed
+pages, etc. under the /usr/local hierarchy, where they will not get mixed
 up with system programs. This also makes sure that all the ports you
 install will go in the same place, instead of being flung all over
 your system.
 
 <item> Register the installation in a database. This means
-that, if you don't like the program, you can cleanly <ref
+that, if you do not like the program, you can cleanly <ref
 id="ports:remove" name="remove"> all traces of it from your system.
 
 </enum>
 
 <p> See if you can match these steps to the make output. And if you
-weren't impressed before, you should be by now!
+were not impressed before, you should be by now!
 
 <sect1><heading>Getting a FreeBSD Port<label id="ports:getting"></heading>
 <p>
@@ -211,7 +211,7 @@ find them in /usr/ports/distfiles, which is why we sym-linked the
 CDROM's tarball directory to there).
 <p>
 Now, suppose you want to install the gnats program from the databases
-directory. Here's how to do it:-
+directory. Here is how to do it:-
 
 <verb>
  # cd /usr/ports
@@ -221,7 +221,7 @@ directory. Here's how to do it:-
  # make install
 </verb>
 
-Or if you're a serious database user and you want to compare all the
+Or if you are a serious database user and you want to compare all the
 ones available in the Ports collection, do
 
 <verb>
@@ -232,12 +232,12 @@ ones available in the Ports collection, do
 </verb>
 
 (yes, that really is a dot on its own after the cp command and not a
-mistake. It's Unix-ese for ``the current directory'')
+mistake. It is Unix-ese for ``the current directory'')
 <p>
 and the ports make mechanism will automatically compile and install
 all the ports in the databases directory for you!
 <p>
-If you don't like this method, here's a completely different way of
+If you do not like this method, here is a completely different way of
 doing it:-
 <p>
 Create a "link tree" to it using the <tt>lndir(1)</tt> command that
@@ -258,17 +258,17 @@ name="Compiling ports using an Internet connection.">
 <sect2><heading>Compiling ports from the Internet<label
 id="ports:inet"></heading>
 <p>
-If you don't have a CDROM, or you want to make sure you get the very
-latest version of the port you want, you'll need to download the
+If you do not have a CDROM, or you want to make sure you get the very
+latest version of the port you want, you will need to download the
 <ref id="ports:skeleton" name="skeleton"> for the port. Now this 
 might sound like rather a fiddly job
 full of pitfalls, like downloading the patches into the pkg
-sub-directory by mistake, but it's actually very easy. 
+sub-directory by mistake, but it is actually very easy. 
 <p>
 The key to it is that the FreeBSD FTP server can create on-the-fly
-<ref id="ports:tarball" name="tarballs"> for you. Here's how it works,
+<ref id="ports:tarball" name="tarballs"> for you. Here is how it works,
 with the gnats program in the databases directory as an example (the
-bits in square brackets are comments, don't type them in if you're
+bits in square brackets are comments, do not type them in if you are
 trying this yourself!):-
 
 <verb>
@@ -295,7 +295,7 @@ on it a little quicker.
 <p>
 We then extracted the gnats skeleton and went into the gnats directory
 to build the port. As we explained <ref id="ports:fetch"
-name="earlier">, the make process noticed we didn't have a copy of the
+name="earlier">, the make process noticed we did not have a copy of the
 source locally, so it fetched one before extracting, patching and
 building it.
 <p>
@@ -322,16 +322,16 @@ different from getting a single port skeleton and building it was that
 we got a whole directory at once, and compiled everything in it at
 once. Pretty impressive, no?
 <p>
-If you expect to be installing more than one or two ports, it's
+If you expect to be installing more than one or two ports, it is
 probably worth downloading all the ports directories - this involves
-downloading 2 or 3MB, when they're compressed. However, don't get
-carried away and type 'get ports.tar.gz' unless you're prepared to
+downloading 2 or 3MB, when they are compressed. However, don't get
+carried away and type 'get ports.tar.gz' unless you are prepared to
 download the distfiles directory as well - this contains the source
 code for every single port and will take a very long time to download!
 
 <sect1><heading>Skeletons<label id="ports:skeleton"></heading>
 <p>
-A team of compulsive hackers who've forgotten to eat in a frantic
+A team of compulsive hackers who have forgotten to eat in a frantic
 attempt to make a deadline? Something unpleasant lurking in the FreeBSD 
 attic? No, a skeleton here is a minimal framework that supplies everything
 needed to make the ports magic work.
@@ -340,7 +340,7 @@ needed to make the ports magic work.
 <p>
 The most important component of a skeleton is the Makefile. This contains
 various statements that specify how the port should be compiled and
-installed. Here's the Makefile for bash:-
+installed. Here is the Makefile for bash:-
 
 <verb>
  # New ports collection makefile for:	bash
@@ -412,7 +412,7 @@ used for ports checksums. It lives in a directory with the slightly
 confusing name of &quot;files&quot;.
 <p>
 This directory can also contain other miscellaneous files that are required
-by the port and don't belong anywhere else.
+by the port and do not belong anywhere else.
 
 <sect2><heading>The patches directory</heading>
 <p>
@@ -473,7 +473,7 @@ dddprogram to install them to your system.
 
 </enum>
 
-<sect1><heading>I've got this program I'd like to make into a port...</heading>
+<sect1><heading>I have this program that I would like to make into a port...</heading>
 
 <p>Great! Please see the <ref id="porting:starting" name="guidelines">
 for detailed instructions on how to do this.
@@ -485,8 +485,8 @@ for detailed instructions on how to do this.
 Q. I thought this was going to be a discussion about modems??!
 <p>
 A. Ah. You must be thinking of the serial ports on the back of your
-computer. We're using `port' here to mean the result of `porting' a
-program from one version of Unix to another. (It's an unfortunate bad
+computer. We are using `port' here to mean the result of `porting' a
+program from one version of Unix to another. (It is an unfortunate bad
 habit of computer people to use the same word to refer to several
 completely different things).
 
@@ -494,7 +494,7 @@ completely different things).
 Q. I thought you were supposed to use packages to install extra
 programs?
 <p>
-A. Yes, that's usually the quickest and easiest way of doing it.
+A. Yes, that is usually the quickest and easiest way of doing it.
 
 <item>
 Q. So why bother with ports then?
@@ -505,11 +505,11 @@ A. Several reasons:-
 <item> The licensing conditions on some software distributions
 require that they be distributed as source code, not binaries.
 
-<item> Some people don't trust binary distributions. At least with
+<item> Some people do not trust binary distributions. At least with
 source code you can (in theory) read through it and look for potential
 problems yourself.
 
-<item> If you've got some local patches, you'll need the source to add
+<item> If you have some local patches, you will need the source to add
 them yourself.
 
 <item> You might have opinions on how a program should be compiled
@@ -525,23 +525,23 @@ permitting, of course!) and so on.
 </enum>
 
 <item><label id="ports:patch">
-Q. What's a patch?
+Q. What is a patch?
 <p>
 A. A patch is a small (usually) file that specifies how to go from one
 version of a file to another. It contains text that says, in effect,
 things like ``delete line 23'', ``add these two lines after line 468''
-or ``change line 197 to this''. Also known as a `diff', since it's
+or ``change line 197 to this''. Also known as a `diff', since it is
 generated by a program of that name.
 
 <item><label id="ports:tarball">
-Q. What's all this about tarballs?
+Q. What is all this about tarballs?
 <p>
-A. It's a file ending in .tar.gz (with variations like .tar.Z, or
-even .tgz if you're trying to squeeze the names into a DOS filesystem).
+A. It is a file ending in .tar.gz (with variations like .tar.Z, or
+even .tgz if you are trying to squeeze the names into a DOS filesystem).
 <p>
-Basically, it's a directory tree that's been archived into a single
+Basically, it is a directory tree that has been archived into a single
 file (.tar) and then compressed (.gz). This technique was originally
-used for <em /T/ape <em /AR/chives (hence the name `tar'), but it's a
+used for <em /T/ape <em /AR/chives (hence the name `tar'), but it is a
 widely used way of distributing program source code around the
 Internet.
 <p>
@@ -557,11 +557,11 @@ system, like this:-
 <item><label id="ports:checksum">
 Q. And a checksum?
 <p>
-A. It's a number generated by adding up all the data in the file you
+A. It is a number generated by adding up all the data in the file you
 want to check. If any of the characters change, the checksum will no
 longer be equal to the total, so a simple comparison will allow you to
-spot the difference. (In practice, it's done in a more complicated way
-to spot problems like position-swapping, which won't show up with a
+spot the difference. (In practice, it is done in a more complicated way
+to spot problems like position-swapping, which will not show up with a
 simplistic addition).
 
 <item>
@@ -575,12 +575,12 @@ port:-
  >> Attempting to fetch from ftp://kermit.columbia.edu/kermit/archives/.
 </verb>
 
-Why can't it find it? Have I got a dud CDROM?
+Why can it not be found? Have I got a dud CDROM?
 <p>
-A. The licensing terms for kermit don't allow us to put the tarball
-for it on the CDROM, so you'll have to fetch it by hand - sorry!
+A. The licensing terms for kermit do not allow us to put the tarball
+for it on the CDROM, so you will have to fetch it by hand - sorry!
 The reason why you got all those error messages was because you
-weren't connected to the Internet at the time. Once you've downloaded
+were not connected to the Internet at the time. Once you have downloaded
 it from any of the sites above, you can re-start the process (try and
 choose the nearest site to you, though, to save your time and the
 Internet's bandwidth).
@@ -590,7 +590,7 @@ Q. I did that, but when I tried to put it into /usr/ports/distfiles I
 got some error about not having permission.
 <p>
 A. The ports mechanism looks for the tarball in /usr/ports/distfiles,
-but you won't be able to copy anything there because it's sym-linked
+but you will not be able to copy anything there because it is sym-linked
 to the CDROM, which is read-only. You can tell it to look somewhere
 else by doing
 
@@ -601,7 +601,7 @@ else by doing
 <item>
 Q. Does the ports scheme only work if you have everything in
 /usr/ports? My system administrator says I must put everything under
-/u/people/guests/wurzburger, but it doesn't seem to work.
+/u/people/guests/wurzburger, but it does not seem to work.
 <p>
 A. You can use the PORTSDIR and PREFIX variables to tell the ports
 mechanism to use different directories. For instance,
@@ -626,16 +626,16 @@ And of course
  PORTSDIR=.../ports PREFIX=.../local make install
 </verb>
 
-will combine the two (it's too long to fit on the page if I write it
-in full, but I'm sure you get the idea).
+will combine the two (it is too long to fit on the page if I write it
+in full, but I am sure you get the idea).
 <p>
-If you don't fancy typing all that in every time you install a port
-(and to be honest, who would?), it's a good idea to put these variables
+If you do not fancy typing all that in every time you install a port
+(and to be honest, who would?), it is a good idea to put these variables
 into your environment.
 
 <item>
-Q. I don't have a FreeBSD CDROM, but I'd like to have all the tarballs
-handy on my system so I don't have to wait for a download every time I
+Q. I do not have a FreeBSD CDROM, but I would like to have all the tarballs
+handy on my system so I do not have to wait for a download every time I
 install a port. Is there an easy way to get them all at once?
 <p>
 A. To get every single tarball for the ports collection, do
@@ -652,10 +652,10 @@ For all the tarballs for a single ports directory, do
  # make fetch
 </verb>
 
-and for just one port - well, I think you've guessed already.
+and for just one port - well, I think you have guessed already.
 
 <item>
-Q. I know it's probably faster to fetch the tarballs from one of the
+Q. I know it is probably faster to fetch the tarballs from one of the
 FreeBSD mirror sites close by. Is there any way to tell the port to
 fetch them from servers other than ones listed in the MASTER_SITES?
 <p>
@@ -674,22 +674,22 @@ A. 'make fetch-list' will display a list of the files needed for a port.
 
 <item>
 Q. Is there any way to stop the port from compiling? I want to do some
-hacking on the source before I install it, but it's a bit tiresome having 
+hacking on the source before I install it, but it is a bit tiresome having 
 to watch it and hit control-C every time.
 <p>
 A. Doing 'make extract' will stop it after it has fetched and
 extracted the source code.
 
 <item>
-Q. I'm trying to make my own port and I want to be able to stop it
-compiling until I've had a chance to see if my patches worked properly. 
+Q. I am trying to make my own port and I want to be able to stop it
+compiling until I have had a chance to see if my patches worked properly. 
 Is there something like 'make extract', but for patches?
 <p>
 A. Yep, 'make patch' is what you want. And by the way, thank you for
 your efforts!
 
 <item>
-Q. I've heard that some compiler options can cause bugs. Is this true?
+Q. I have heard that some compiler options can cause bugs. Is this true?
 How can I make sure that I compile ports with the right settings?
 <p>
 A. Yes, with version 2.6.3 of gcc (the version shipped with FreeBSD
@@ -702,14 +702,14 @@ used by something like
  # CFLAGS='-O2 -fno-strength-reduce' make install
 </verb>
 
-or by editing /etc/make.conf, but this doesn't always seem to get
+or by editing /etc/make.conf, but this does not always seem to get
 picked up. The surest way is to do 'make configure', then go into the
 source directory and inspect the Makefiles by hand, but this can get
 tedious if the source has lots of sub-directories, each with their own
 Makefiles.
 
 <item>
-Q. There's so many ports it's hard to find the one I want. Is there a
+Q. There are so many ports it is hard to find the one I want. Is there a
 list anywhere of what ports are available?
 <p>
 A. Look in the INDEX file in /usr/ports.
@@ -718,14 +718,14 @@ A. Look in the INDEX file in /usr/ports.
 Q. I went to install the 'foo' port but the system suddenly stopped
 and starting compiling the 'bar' port. What's going on?
 <p>
-A. The 'foo' port needs something that's supplied with 'bar' - for
+A. The 'foo' port needs something that is supplied with 'bar' - for
 instance, if 'foo' uses graphics, 'bar' might have a library with
-useful graphics processing routines. Or 'bar' might be a tool that's
+useful graphics processing routines. Or 'bar' might be a tool that is
 needed to compile the 'foo' port.
 
 <item><label id="ports:remove"> 
-Q. I installed the grizzle program from the ports and frankly it's a
-complete waste of disk space. I want to delete it but I don't know
+Q. I installed the grizzle program from the ports and frankly it is a
+complete waste of disk space. I want to delete it but I do not know
 where it put all the files. Any clues?
 <p>
 A. No problem, just do
@@ -736,7 +736,7 @@ A. No problem, just do
 <item>
 
 Q. Hang on a minute, you have to know the version number to use that
-command. You don't seriously expect me to remember that, do you??
+command. You do not seriously expect me to remember that, do you??
 <p>
 A. Not at all, you can find it out by doing
 
@@ -744,7 +744,7 @@ A. Not at all, you can find it out by doing
  pkg_info -a | grep grizzle
 </verb>
 
-And it'll tell you:-
+And it will tell you:-
 
 <verb>
  Information for grizzle-6.5:
@@ -755,8 +755,8 @@ And it'll tell you:-
 Q. Talking of disk space, the ports directory seems to be taking up
 an awful lot of room. Is it safe to go in there and delete things?
 <p>
-A. Yes, if you've installed the program and are fairly certain you
-won't need the source again, there's no point in keeping it hanging
+A. Yes, if you have installed the program and are fairly certain you
+will not need the source again, there is no point in keeping it hanging
 around. The best way to do this is
 
 <verb>
@@ -770,7 +770,7 @@ everything except the skeletons for each port.
 Q. I tried that and it still left all those tarballs or whatever you
 called them in the distfiles directory. Can I delete those as well?
 <p>
-A. Yes, if you're sure you've finished with them, those can go as
+A. Yes, if you are sure you have finished with them, those can go as
 well.
 
 <item>
@@ -791,12 +791,12 @@ computer this morning, it had only done three and a half ports. Did
 something go wrong?
 <p>
 A. No, the problem is that some of the ports need to ask you questions
-that we can't answer for you (eg ``Do you want to print on A4 or US
+that we can not for you (eg ``Do you want to print on A4 or US
 letter sized paper?'') and they need to have someone on hand to answer
 them.
 
 <item>
-Q. I really don't want to spend all day staring at the monitor. Any
+Q. I really do nott want to spend all day staring at the monitor. Any
 better ideas?
 <p>
 A. OK, do this before you go to bed/work/the local park:-
@@ -817,8 +817,8 @@ input. Then, when you come back, do
 to finish the job.
 
 <item>
-Q. At work, we're using frobble, which is in your ports collection,
-but we've altered it quite a bit to get it to do what we need. Is
+Q. At work, we are using frobble, which is in your ports collection,
+but we have altered it quite a bit to get it to do what we need. Is
 there any way of making our own packages, so we can distribute it more
 easily around our sites?
 <p>
@@ -834,8 +834,8 @@ A. No problem, assuming you know how to make patches for your changes:-
 </verb>
 
 <item>
-Q. This ports stuff is really clever. I'm desperate to find out how
-you did it. What's the secret?
+Q. This ports stuff is really clever. I am desperate to find out how
+you did it. What is the secret?
 <p>
 A. Nothing secret about it at all, just look at the bsd.ports.mk and
 bsd.ports.subdir.mk files in your <htmlurl
diff --git a/share/doc/handbook/printing.sgml b/share/doc/handbook/printing.sgml
index bac8ae4..74e4b43 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.12 1996/12/02 13:11:42 max Exp $
+     $Id: printing.sgml,v 1.13 1996/12/28 20:38:42 wosch Exp $
 
      The FreeBSD Documentation Project
 
@@ -79,12 +79,12 @@
 
 	<p> If you are the sole user of your system, you may be
 	  wondering why you should bother with the spooler when you
-	  don't need access control, header pages, or printer
-	  accounting.  While it's possible to enable direct access to
+	  do not need access control, header pages, or printer
+	  accounting.  While it is possible to enable direct access to
 	  a printer, you should use the spooler anyway since
 
 	  <itemize>
-	    <item>LPD prints jobs in the background; you don't have
+	    <item>LPD prints jobs in the background; you do not have
 	      to wait for data to be copied to the printer.
 
 	    <item>LPD can conveniently run a job to be printed
@@ -541,7 +541,7 @@ showpage
 		</enum>
 
 		You should see something print.  Do not worry if the
-		text doesn't look right; we'll fix such things later.
+		text does not look right; we will fix such things later.
 
 	    <sect4><heading>Checking a Serial Printer<label
 		  id="printing:checking:serial"></heading>
@@ -1298,7 +1298,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
     <sect><heading>Using Printers<label id="printing:using"></heading>
 
       <p> This section tells you how to use printers you have setup with
-	FreeBSD.  Here's an overview of the user-level commands:
+	FreeBSD.  Here is an overview of the user-level commands:
 	<descrip>
 	  <tag/<tt/lpr//
 	    Print jobs
diff --git a/share/doc/handbook/scsi.sgml b/share/doc/handbook/scsi.sgml
index 41a283c..e88c66f 100644
--- a/share/doc/handbook/scsi.sgml
+++ b/share/doc/handbook/scsi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: scsi.sgml,v 1.18 1996/08/18 17:04:41 jkh Exp $ -->
+<!-- $Id: scsi.sgml,v 1.19 1996/10/04 22:54:14 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -188,7 +188,7 @@
 	    on a 8 bit bus, 40 Mbytes/second on a 16 bit bus etc.
 	    For F20 the max bus length is 1.5 meters, for F40 it
 	    becomes 0.75 meters. Be aware that F20 is pushing 
-	    the limits quite a bit, so you'll quickly find out if your
+	    the limits quite a bit, so you will quickly find out if your
 	    SCSI bus is electrically sound.
 
 	    Please note that this means that
@@ -212,7 +212,7 @@
 	    The reduction of the number of ground wires they used
 	    is a bad idea, you better stick to 50 pins cabling 
 	    in accordance with the SCSI standard. For Fast-20 and 40
-	    don't even think about buses like this..
+	    do not even think about buses like this.
 
         <sect3><heading>Differential buses</heading>
           <p>
@@ -224,7 +224,7 @@
             difference between these two wires determines whether the
             signal is asserted or de-asserted. To a certain extent the
             voltage difference between ground and the signal wire pair is
-            not relevant (do not try 10 kVolts though..).
+            not relevant (do not try 10 kVolts though).
             
             It is beyond the scope of this document to explain why this
             differential idea is so much better. Just accept that
@@ -280,7 +280,7 @@
 
             OK, and now where should you install your terminators?  This is
             by far the most misunderstood part of SCSI. And it is by far
-            the simplest..  The rule is: <bf>every SCSI bus has 2 (two)
+            the simplest.  The rule is: <bf>every SCSI bus has 2 (two)
             terminators, one at each end of the bus.</bf> So, two and not
             one or three or whatever. Do yourself a favor and stick to
             this rule. It will save you endless grief, because wrong
@@ -382,7 +382,7 @@
             invent.
 
             You might notice that the terminator issue discussed earlier
-            becomes rather hairy if your bus is not linear..
+            becomes rather hairy if your bus is not linear.
 
             The electrical characteristics, its noise margins and
             ultimately the reliability of it all are tightly related to
@@ -429,7 +429,7 @@
           megabytes. The division by 2 is to get from disk blocks that are
           normally 512 bytes in size to Kbytes.
 
-          Right.. All is well now?! No, it is not. The system BIOS has
+          Right. All is well now?! No, it is not. The system BIOS has
           another quirk you might run into. The number of cylinders of a
           bootable hard disk cannot be greater than 1024. Using the
           translation above, this is a show-stopper for disks greater than
@@ -462,7 +462,7 @@
 	aha0 targ 0 lun 0: <MICROP  1588-15MB1057404HSP4>
 	sd0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512
           </verb>
-          Newer kernels usually do not report this information.. e.g.
+          Newer kernels usually do not report this information. e.g.
 	  <verb>
 	 (bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2
 	 sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)
@@ -739,8 +739,8 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive  Viper 150 is a known rogue
 
 	  In a nutshell, TCQ allows the device to have multiple I/O
 	  requests outstanding at the same time. Because the device
-	  is intelligent, it can optimise it's operations (like
-  	  head positioning) based on it's own request queue. On 
+	  is intelligent, it can optimise its operations (like
+  	  head positioning) based on its own request queue. On 
 	  SCSI devices like RAID (Redundant Array of Independent
 	  Disks) arrays the TCQ function is indispensable to take
 	  advantage of the device's inherent parallelism.
diff --git a/share/doc/handbook/synching.sgml b/share/doc/handbook/synching.sgml
index 8e34128..41586a2 100644
--- a/share/doc/handbook/synching.sgml
+++ b/share/doc/handbook/synching.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: synching.sgml,v 1.5 1996/12/19 20:24:37 jkh Exp $ -->
+<!-- $Id: synching.sgml,v 1.6 1996/12/19 23:49:14 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/12/19 20:24:37 $
+Last updated: $Date: 1996/12/19 23:49:14 $
 
 This document tries to describe the various ways in which a user may
 use the internet to keep development sources in synch.
@@ -33,7 +33,7 @@ stamped with a sequence-number and encoded for transmission over email
 handed to the ctm_rmail(1) utility which will automatically decode, verify
 and apply the changes to the user's copy of the sources.  This process is
 far more efficient than CVSup, and places less strain on our server resources
-since it's a <em>push</em> rather than a <em>pull</em> model.
+since it is a <em>push</em> rather than a <em>pull</em> model.
 
 <p>There are other trade-offs, of course.  With CVSup, you can also
 inadvertently wipe out portions of your archive and CVSup will detect