38 files changed, 772 insertions, 765 deletions

diff --git a/share/doc/handbook/authors.sgml b/share/doc/handbook/authors.sgml
index d66e5f20346a..b8733ff5e78f 100644
--- a/share/doc/handbook/authors.sgml
+++ b/share/doc/handbook/authors.sgml
@@ -1,58 +1,12 @@
-<!-- $Id: authors.sgml,v 1.21 1996/05/14 20:31:50 rich Exp $ -->
+<!-- $Id: authors.sgml,v 1.22 1996/05/16 20:20:54 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!-- 
-Names and email address of contributing authors and CVS committers
-and some of the common FreeBSD mailing lists.  Use these
-entities when referencing people or mailing lists.  Please 
-note the use of single
+Names and email address of contributing authors and CVS committers.
+Use these entities when referencing people.  Please note the use of single
 and double quotes.  
 -->
 
-<!ENTITY a.announce "FreeBSD announcments mailing list
-  <tt><htmlurl url='mailto:freebsd-announce@FreeBSD.ORG'
-  name='&lt;freebsd-announce@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.doc "FreeBSD documentation project mailing list
-  <tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
-  name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.bugs "FreeBSD problem reports mailing list
-  <tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
-  name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.current "FreeBSD-current mailing list
-  <tt><htmlurl url='mailto:freebsd-current@FreeBSD.ORG'
-  name='&lt;freebsd-current@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.emulation "FreeBSD-emulation mailing list
-  <tt><htmlurl url='mailto:freebsd-emulation@FreeBSD.ORG'
-  name='&lt;freebsd-emulation@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.fs "FreeBSD filesystem project mailing list
-  <tt><htmlurl url='mailto:freebsd-fs@FreeBSD.ORG'
-  name='&lt;freebsd-fs@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.hackers "FreeBSD technical discussions mailing list
-  <tt><htmlurl url='mailto:freebsd-hackers@FreeBSD.ORG'
-  name='&lt;freebsd-hackers@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.ports "FreeBSD ports mailing list
-  <tt><htmlurl url='mailto:freebsd-ports@FreeBSD.ORG'
-  name='&lt;freebsd-ports@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.questions "FreeBSD general questions mailing list
-  <tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
-  name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.scsi "FreeBSD SCSI subsystem mailing list
-  <tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
-  name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
-
-<!ENTITY a.stable "FreeBSD-stable mailing list
-  <tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
-  name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
-
 <!ENTITY a.asami "Satoshi Asami 
   <tt><htmlurl url='mailto:asami@FreeBSD.ORG'
   name='&lt;asami@FreeBSD.ORG&gt;'></tt>">
diff --git a/share/doc/handbook/basics.sgml b/share/doc/handbook/basics.sgml
index 732a2693a456..70fb65dfb8ff 100644
--- a/share/doc/handbook/basics.sgml
+++ b/share/doc/handbook/basics.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: basics.sgml,v 1.5 1995/12/11 15:09:02 jkh Exp $ -->
+<!-- $Id: basics.sgml,v 1.6 1995/12/14 19:42:34 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Unix Basics<label id="basics"></heading>
@@ -66,7 +66,7 @@
 	  using the <tt><bf>apropos</bf></tt> command.
 
 	<p>So, you are looking at all those fancy commands in <tt>
-	  /usr/bin</tt> but don't even have the faintest idea
+	  /usr/bin</tt> but do not even have the faintest idea
 	  what most of them actually do?  Simply do a
 	  <tscreen>
 	    % <bf>cd /usr/bin; man -f *</bf>
diff --git a/share/doc/handbook/booting.sgml b/share/doc/handbook/booting.sgml
index 8c258c316cb8..8145a74a16a7 100644
--- a/share/doc/handbook/booting.sgml
+++ b/share/doc/handbook/booting.sgml
@@ -3,7 +3,7 @@
      
      This conversion has been made by Ollivier Robert.
 
-     $Id: booting.sgml,v 1.9 1996/01/31 14:25:57 mpp Exp $
+     $Id: booting.sgml,v 1.10 1996/01/31 19:02:55 mpp Exp $
 
 
 <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
@@ -51,7 +51,7 @@
 
           Dosboot was written by DI. Christian Gusenbauer, and is
           unfortunately at this time one of the few pieces of code that
-          isn't compilable under FreeBSD itself because it is written for
+          will not compile under FreeBSD itself because it is written for
           Microsoft compilers.
 
           Dosboot will boot the kernel from a MS-DOS file or from a FreeBSD
@@ -83,7 +83,7 @@
 
       <tag>MSDOS</tag>
 
-          While this is technically possible, it isn't particular useful,
+          While this is technically possible, it is not particular useful,
           because of ``FAT'' filesystems inability to make links, device
           nodes and such ``UNIXisms''.
 
@@ -147,7 +147,7 @@
             <tt>/nfs</tt>, chroots to <tt>/nfs</tt> and executes
             <tt>/sbin/init</tt> there
 
-            Now you run FreeBSD diskless, even though you don't control
+            Now you run FreeBSD diskless, even though you do not control
             the NFS server...
 
           <tag/C -- Start an X-server/
diff --git a/share/doc/handbook/contrib.sgml b/share/doc/handbook/contrib.sgml
index 1bf0ad37b078..104cac3d7e8e 100644
--- a/share/doc/handbook/contrib.sgml
+++ b/share/doc/handbook/contrib.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: contrib.sgml,v 1.83 1996/05/13 09:31:34 asami Exp $ -->
+<!-- $Id: contrib.sgml,v 1.84 1996/05/15 17:32:46 joerg Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>FreeBSD contributor list<label id="contrib"></heading>
@@ -36,7 +36,7 @@
       couple of FreeBSD hackers alive and busy.  Thanks!
 
       Thanks also to Dermot McDonnell for his donation of a
-      Toshiba XM3401B CDROM drive.  It's been most useful!
+      Toshiba XM3401B CDROM drive.  It has been most useful!
 
       Thanks to Chuck Robey &lt;chuckr@eng.umd.edu&gt; who
       contributed his floppy tape streamer for experimental
diff --git a/share/doc/handbook/ctm.sgml b/share/doc/handbook/ctm.sgml
index 116789a1d076..1f73410647bd 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.7 1996/02/02 05:27:24 wosch Exp $
+# $Id: ctm.sgml,v 1.8 1996/05/09 23:04:32 mpp Exp $
 #
 # ----------------------------------------------------------------------------
 # "THE BEER-WARE LICENSE" (Revision 42):
@@ -66,7 +66,7 @@
         If you only have access to electronic mail or are otherwise blocked
         from using FTP then you may wish to get your deltas via email:
 
-        Send email to <tt/&lt;majordomo@FreeBSD.ORG&gt;/ to subscribe to
+        Send email to &a.majordomo to subscribe to
         the list ``ctm-src-cur''.  (If you do not know how to subscribe
         yourself using majordomo, send a message first containing the
         word ``help'' - it will send you back usage instructions.)
@@ -82,7 +82,7 @@
         deltas, you should subscribe to the <tt/ctm-announce@FreeBSD.ORG/
         mailing list.  In the future, this will be the only place where
         announcements concerning the operations of the <tt/CTM/ system will be
-        posted.  Send an email to <tt/majordomo@FreeBSD.ORG/ with a single
+        posted.  Send an email to &a.majordomo with a single
         line of ``<tt/subscribe ctm-announce/'' to get added to the list.
 
     <sect1><heading>Starting off with <tt/CTM/ for the first time</heading>
@@ -97,7 +97,7 @@
         Megabytes of <tt/gzip/'ed data is common for a base delta.
 
         If you do have the 2.0-RELEASE <tt/srcdist/, you can instead
-        retrieve the <tt/src-cur.0372R20.gz/ file, it's only 4Mb and it
+        retrieve the <tt/src-cur.0372R20.gz/ file, it is only 4Mb and it
         will take you to current from the 2.0-RELEASE sources.
 
         Once you've picked a base delta to start from, you will also need
@@ -110,11 +110,11 @@
           ctm -v -v /where/you/store/your/deltas/src-cur.*
         </verb>
         <tt/CTM/ understands deltas which have been put through <tt/gzip/,
-        so you don't need to gunzip them first, this saves disk space.
+        so you do not need to gunzip them first, this saves disk space.
 
         Unless it feels very secure about the entire process, <tt/CTM/ will
         not touch your tree.  To verify a delta you can also use the
-        ``<tt/-c/'' flag and <tt/CTM/ won't actually touch your tree; it will
+        ``<tt/-c/'' flag and <tt/CTM/ will not actually touch your tree; it will
 	merely verify the integrity of the delta and see if it would apply
         cleanly to your current tree.
 
@@ -122,13 +122,13 @@
         for more details.
 
         I would also be very happy if somebody could help with the ``user
-        interface'' portions, as I have realized that I can't make up my
+        interface'' portions, as I have realized that I cannot make up my
         mind on what options should do what, how and when...
 
         That's really all there is to it.  Every time you get a new delta,
         just run it through <tt/CTM/ to keep your sources up to date.
 
-        Don't remove the deltas if they are hard to download again.  You
+        Do not remove the deltas if they are hard to download again.  You
         just might want to keep them around in case something bad happens.
         Even if you only have floppy disks, consider using <tt/fdwrite/ to
         make a copy.
@@ -157,7 +157,7 @@
         </itemize>
 
         The bad news is that I am very busy, so any help in doing this will
-        be most welcome.  And don't forget to tell me what you want also...
+        be most welcome.  And do not forget to tell me what you want also...
 
     <sect1><heading>Miscellaneous stuff</heading>
       <p>
@@ -174,7 +174,7 @@
 
         There is a sequence of deltas for the <tt/ports/ collection too,
         but interest has not been all that high yet.  Tell me if you want
-        an email list for that too and we'll consider setting it up.
+        an email list for that too and we will consider setting it up.
 
         If you have commit privileges or are similarly authorized by the
         FreeBSD core team, you can also get access to the CVS repository
diff --git a/share/doc/handbook/current.sgml b/share/doc/handbook/current.sgml
index 60b54d0f384d..a12388a990ec 100644
--- a/share/doc/handbook/current.sgml
+++ b/share/doc/handbook/current.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: current.sgml,v 1.9 1996/02/11 00:16:12 jkh Exp $ -->
+<!-- $Id: current.sgml,v 1.10 1996/05/09 23:04:33 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -10,7 +10,7 @@
 
                         THE FREEBSD CURRENT POLICY 
 
-Last updated: $Date: 1996/02/11 00:16:12 $
+Last updated: $Date: 1996/05/09 23:04:33 $
 
 This document attempts to explain the rationale behind
 FreeBSD-current, what you should expect should you decide to run it,
@@ -32,9 +32,9 @@ desired functionality can literally be a matter of which part of any
 given 24 hour period you grabbed them in!
 
 Under certain circumstances we will sometimes make binaries for parts
-of FreeBSD-current available, but only because we're interested in
-getting something tested, not because we're in the business of
-providing binary releases of current.  If we don't offer, please don't
+of FreeBSD-current available, but only because we are interested in
+getting something tested, not because we are in the business of
+providing binary releases of current.  If we do not offer, please do not
 ask!  It takes far too much time to do this as a general task.
 
 <sect><heading>Who needs FreeBSD-current?</heading>
@@ -72,10 +72,10 @@ ask!  It takes far too much time to do this as a general task.
         ``legitimate'' FreeBSD-current categories, but we simply <em>do not
         have the time</em> to help every person who jumps into FreeBSD-current
         with more enthusiasm than knowledge of how to deal with
-        experimental system software.  This is not because we're mean and
-        nasty people who don't like helping people out (we wouldn't even be
-        doing FreeBSD if we were), it's literally because we can't answer
-        400 messages a day <em>and</em> actually work on FreeBSD!  I'm sure
+        experimental system software.  This is not because we are mean and
+        nasty people who do not like helping people out (we would not even be
+        doing FreeBSD if we were),  it is literally because we cannot answer
+        400 messages a day <em>and</em> actually work on FreeBSD!  I am sure
         that, if given the choice between having us answer lots of questions or
         continuing to improve FreeBSD, most of you would vote for us
         improving it.
@@ -84,9 +84,9 @@ ask!  It takes far too much time to do this as a general task.
 <sect><heading>Using FreeBSD-current</heading>
 
 <p><enum> <item> Join the freebsd-current and cvs-all
-    mailing lists.  This is not just a good idea, it's
-    <em>essential</em>.  If you aren't on the &a.current, you
-    won't see the comments that people are making about the
+    mailing lists.  This is not just a good idea, it is
+    <em>essential</em>.  If you are not on the &a.current, you
+    will not see the comments that people are making about the
     current state of the system and thus will probably end up stumbling
     over a lot of problems that others have already found and
     solved.  Even more importantly, you will miss out on
@@ -95,12 +95,10 @@ ask!  It takes far too much time to do this as a general task.
     rebuild the kernel or your system will crash horribly!").
 
     The cvs-all mailing list will allow you to see the commit log
-    entry for each change as it's made along with any pertinent
+    entry for each change as it is made along with any pertinent
     information on possible side-effects.
 
-        To join these lists, send mail to
-        <htmlurl url="mailto:majordomo@FreeBSD.ORG"
-        name="majordomo@FreeBSD.ORG"> and say:
+        To join these lists, send mail to &a.majordomo and specify:
 <verb>
             subscribe current
             subscribe cvs-all
@@ -120,7 +118,7 @@ ask!  It takes far too much time to do this as a general task.
         <item>  Use the CMU `sup' program (Software Update
 	     Protocol), also described below.
             This is the second most recommended method, since it allows 
-	    you to grab the entire collection once and then only what's
+	    you to grab the entire collection once and then only what has
             changed from then on.  Many people run sup from cron
             and keep their sources up-to-date automatically.
 
@@ -146,7 +144,7 @@ ask!  It takes far too much time to do this as a general task.
     communications bandwidth is not a consideration, use sup or ftp.
     Otherwise, use CTM.
 
-    <item>  If you're grabbing the sources to run, and not just look at,
+    <item>  If you are grabbing the sources to run, and not just look at,
     then grab <em>all</em> of current, not just selected portions.  The
     reason for this is that various parts of the source depend on
     updates elsewhere, and trying to compile just a subset is almost
@@ -159,7 +157,7 @@ ask!  It takes far too much time to do this as a general task.
         bootstrapping procedures that sometimes become necessary as we move
         towards	the next release.
 
-    <item>  Be active!  If you're running FreeBSD-current, we want to know
+    <item>  Be active!  If you are  running FreeBSD-current, we want to know
 	what you have to say about it, especially if you have suggestions
 	for enhancements or bug fixes.  Suggestions with accompanying code
 	are received most enthusiastically! 
diff --git a/share/doc/handbook/dialup.sgml b/share/doc/handbook/dialup.sgml
index c2bfcca390f8..7c7490314605 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.7 1996/03/31 18:01:53 joerg Exp $
+     $Id: dialup.sgml,v 1.8 1996/05/09 23:04:35 mpp Exp $
 
 <!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
 
@@ -68,10 +68,10 @@ If you need more information about these terms and data communications
 in general, the author remembers reading that <em/The RS-232 Bible/
 (anybody have an ISBN?) is a good reference.
 
-When talking about communications data rates, the author doesn't use
+When talking about communications data rates, the author does notuse
 the term <bf/baud/.  Baud refers to the number of electrical state
 transitions that may be made in a period of time, while <bf/bps/ (bits
-per second) is the ``correct'' term to use (at least it doesn't seem
+per second) is the ``correct'' term to use (at least it does not seem
 to bother the curmudgeons quite a much).
 
 <sect2><heading>External vs. Internal Modems</heading>
@@ -97,7 +97,7 @@ A background knowledge of these items is assumed
 <itemize>
 
 <item> You know how to connect your modem to your computer so that the
-two can communicate (unless you have an internal modem, which doesn't
+two can communicate (unless you have an internal modem, which does not
 need such a cable)
 
 <item> You are familiar with your modem's command set, or know where
@@ -134,7 +134,7 @@ without all of the needed signals, so if you have problems, such as
 a login session not going away when the line hangs up, you may have a
 problem with your cable.
 
-The second prerequisite depends on the modem(s) you use.  If you don't
+The second prerequisite depends on the modem(s) you use.  If you do not
 know your modem's command set by heart, you will need to have the
 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
@@ -228,7 +228,7 @@ sio3 at 0x2e8-0x2ef irq 9 on isa
 sio3: type 16550A
 </verb></tscreen>
 
-If your kernel doesn't recognize all of your serial ports, you'll
+If your kernel does not recognize all of your serial ports, you will
 probably need to configure a custom FreeBSD kernel for your system.
 
 Please see the BSD System Manager's Manual chapter on ``Building
@@ -238,13 +238,13 @@ Options'' &lsqb;in <tt>/sys/conf/options</tt> and in
 <tt>/sys/<em>arch</em>/conf/options.<em>arch</em></tt>, with
 <em>arch</em> for example being <tt>i386</tt>&rsqb; for more
 information on configuring and building kernels.  You may have to
-unpack the kernel source distribution if haven't installed the system
+unpack the kernel source distribution if have not installed the system
 sources already (<tt>srcdist/srcsys.??</tt> in FreeBSD 1.1,
 <tt>srcdist/sys.??</tt> in FreeBSD 1.1.5.1, or the entire source
 distribution in FreeBSD 2.0) to be able to configure and build
 kernels.
 
-Create a kernel configuration file for your system (if you haven't
+Create a kernel configuration file for your system (if you have not
 already) by <tt/cd/ing to <tt>/sys/i386/conf</tt>.  Then, if you are
 creating a new custom configuration file, copy the file GENERICAH (or
 GENERICBT, if you have a BusTek SCSI controller on FreeBSD 1.x) to
@@ -258,7 +258,7 @@ device		sio2	at isa? port "IO_COM3" tty irq 5 vector siointr
 device		sio3	at isa? port "IO_COM4" tty irq 9 vector siointr
 </verb></tscreen>
 
-You can comment-out or completely remove lines for devices you don't
+You can comment-out or completely remove lines for devices you do not
 have.  If you have a multiport serial board, such as the Boca Board
 BB2016, please see the <tt/sio(4)/ man page for complete information
 on how to write configuration lines for multiport boards.  Be careful
@@ -271,7 +271,7 @@ Note that <tt/port "IO_COM1"/ is a substitution for <tt/port 0x3f8/,
 <tt/IO_COM4/ is <tt/0x2e8/, which are fairly common port addresses for
 their respective serial ports; interrupts 4, 3, 5, and 9 are fairly
 common interrupt request lines.  Also note that regular serial ports
-<bf>can't</bf> share interrupts on ISA-bus PCs (multiport boards have
+<bf>cannot</bf> share interrupts on ISA-bus PCs (multiport boards have
 on-board electronics that allow all the 16550A's on the board to share
 one or two interrupt request lines).
 
@@ -319,7 +319,7 @@ exists.
 After making new device special files, be sure to check the
 permissions on the files (especially the <tt>/dev/cua*</tt> files) to
 make sure that only users who should have access to those device
-special files can read &amp; write on them - you probably don't want
+special files can read &amp; write on them - you probably do not want
 to allow your average user to use your modems to dialout.  The default
 permissions on the <tt>/dev/cua*</tt> files should be sufficient:
 
@@ -336,7 +336,7 @@ These permissions allow the user <tt/uucp/ and users in the group
 <p>
 
 There are three system configuration files in the <tt>/etc</tt>
-directory that you'll probably need to edit to allow dialup access to
+directory that yo will probably need to edit to allow dialup access to
 your FreeBSD system.  The first, <tt>/etc/gettytab</tt>, contains
 configuration information for the <tt>/usr/libexec/getty</tt> daemon.
 Second, <tt>/etc/ttys</tt> holds information that tells
@@ -351,8 +351,8 @@ group likes to configure their modems and system so that no matter at
 what speed a remote user dials in, the local computer-to-modem RS-232
 interface runs at a locked speed.  The benefit of this configuration
 is that the remote user always sees a system login prompt immediately.
-The downside is that the system doesn't know what a user's true data
-rate is, so full-screen programs like Emacs won't adjust their
+The downside is that the system does not know what a user's true data
+rate is, so full-screen programs like Emacs will not adjust their
 screen-painting methods to make their response better for slower
 connections.
 
@@ -360,17 +360,17 @@ The other school configures their modems' RS-232 interface to vary its
 speed based on the remote user's connection speed.  For example,
 V.32bis (14.4 Kbps) connections to the modem might make the modem run
 its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the
-modem's RS-232 interface run at 2400 bps.  Because <tt/getty/ doesn't
+modem's RS-232 interface run at 2400 bps.  Because <tt/getty/ does not
 understand any particular modem's connection speed reporting,
 <tt/getty/ gives a <tt/login:/ message at an initial speed and watches
 the characters that come back in response.  If the user sees junk,
-it's assumed that they know they should press the
+it is assumed that they know they should press the
 <tt>&lt;Enter&gt;</tt> key until they see a recognizable prompt.  If
-the data rates don't match, <tt/getty/ sees anything the user types as
+the data rates do not match, <tt/getty/ sees anything the user types as
 ``junk'', tries going to the next speed and gives the <tt/login:/
 prompt again.  This procedure can continue ad nauseum, but normally
 only takes a keystroke or two before the user sees a good prompt.
-Obviously, this login sequence doesn't look as clean as the former
+Obviously, this login sequence does not look as clean as the former
 ``locked-speed'' method, but a user on a low-speed connection should
 receive better interactive response from full-screen programs.
 
@@ -390,17 +390,17 @@ the file and the list of capabilities.
 <p>
 
 If you are locking your modem's data communications rate at a
-particular speed, you probably won't need to make any changes to
+particular speed, you probably will not need to make any changes to
 <tt>/etc/gettytab</tt>.
 
 <sect3><heading>Matching-Speed Config</heading>
 <p>
 
-You'll need to setup an entry in <tt>/etc/gettytab</tt> to give
+You will need to setup an entry in <tt>/etc/gettytab</tt> to give
 <tt/getty/ information about the speeds you wish to use for your
 modem.  If you have a 2400 bps modem, you can probably use the
 existing <tt/D2400/ entry.  This entry already exists in the FreeBSD
-1.1.5.1 <tt/gettytab/ file, so you don't need to add it unless it is
+1.1.5.1 <tt/gettytab/ file, so you do not need to add it unless it is
 missing under your version of FreeBSD:
 
 <tscreen><verb>
@@ -415,8 +415,8 @@ D2400|d2400|Fast-Dial-2400:\
         :nx=D2400:tc=300-baud:
 </verb></tscreen>
 
-If you have a higher speed modem, you'll probably need to add an entry
-in <tt>/etc/gettytab</tt>; here's an entry you could use for a 14.4
+If you have a higher speed modem, you will probably need to add an entry
+in <tt>/etc/gettytab</tt>; here is an entry you could use for a 14.4
 Kbps modem with a top interface speed of 19.2 Kpbs:
 
 <tscreen><verb>
@@ -450,7 +450,7 @@ rate.
 
 If you have a 28.8 Kbps modem and/or you want to take advantage of
 compression on a 14.4 Kbps modem, you need to use a higher
-communications rate than 19.2 Kbps.  Here's an example of a
+communications rate than 19.2 Kbps.  Here is an example of a
 <tt/gettytab/ entry starting a 57.6 Kpbs:
 
 <tscreen><verb>
@@ -470,7 +470,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
         :nx=VH9600:tc=std.57600:
 </verb></tscreen>
 
-If you have a slow CPU or a heavily loaded system and you don't have
+If you have a slow CPU or a heavily loaded system and you dobnot have
 16550A-based serial ports, you may receive sio ``silo'' errors at 57.6
 Kbps.
 
@@ -482,7 +482,7 @@ Kbps.
 (user <tt/root/ may only login on ttys marked <tt/secure/).  See the
 manual page for <tt/ttys(5)/ for more information.
 
-You'll need to either modify existing lines in <tt>/etc/ttys</tt> or
+You will need to either modify existing lines in <tt>/etc/ttys</tt> or
 add new lines to make <tt/init/ run <tt/getty/ processes automatically
 on your new dialup ports.  The general format of the line will be the
 same, whether you are using a locked-speed or matching-speed
@@ -588,7 +588,7 @@ stty -f /dev/ttyd2 crtscts
 stty -f /dev/ttyd3 crtscts
 </verb></tscreen>
 
-Since there isn't an initialization device special file on FreeBSD
+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.
 
@@ -596,7 +596,7 @@ hope the flags aren't cleared by a miscreant.
 <p>
 
 If you have a modem whose parameters may be permanently set in
-non-volatile RAM, you'll need to use a terminal program (such as Telix
+non-volatile RAM, you will need to use a terminal program (such as Telix
 under PC-DOS or <tt/tip/ under FreeBSD) to set the parameters.
 Connect to the modem using the same communications speed as the
 initial speed <tt/getty/ will use and configure the modem's
@@ -644,7 +644,7 @@ settings as an example:
 
 <item> Switch 1: UP - DTR Normal
 
-<item> Switch 2: Don't care (Verbal Result Codes/Numeric Result Codes)
+<item> Switch 2: Do not care (Verbal Result Codes/Numeric Result Codes)
 
 <item> Switch 3: UP - Suppress Result Codes
 
@@ -656,20 +656,20 @@ settings as an example:
 
 <item> Switch 7: UP - Load NVRAM Defaults
 
-<item> Switch 8: Don't care (Smart Mode/Dumb Mode)
+<item> Switch 8: Do not care (Smart Mode/Dumb Mode)
 
 </itemize>
 
 Result codes should be disabled/suppressed for dialup modems to avoid
 problems that can occur if <tt/getty/ mistakenly gives a <tt/login:/
 prompt to a modem that is in command mode and the modem echoes the
-command or returns a result code.  I've heard this sequence can result
+command or returns a result code.  I have heard this sequence can result
 in a extended, silly conversation between <tt/getty/ and the modem.
 
 <sect2><heading>Locked-speed Config</heading>
 <p>
 
-For a locked-speed configuration, you'll need to configure the modem
+For a locked-speed configuration, you will need to configure the modem
 to maintain a constant modem-to-computer data rate independent of the
 communications rate.  On a USR Sportster 14,400 external modem, these
 commands will lock the modem-to-computer data rate at the speed used
@@ -683,7 +683,7 @@ AT&amp;B1&amp;W
 <sect2><heading>Matching-speed Config</heading>
 <p>
 
-For a variable-speed configuration, you'll need to configure your
+For a variable-speed configuration, you will need to configure your
 modem to adjust its serial port data rate to match the incoming call
 rate.  On a USR Sportster 14,400 external modem, these commands will
 lock the modem's error-corrected data rate to the speed used to issue
@@ -741,13 +741,13 @@ If you see something different, like this:
       ^^
 </verb></tscreen>
 
-and the modem hasn't accepted a call yet, this means that <tt/getty/
+and the modem has not accepted a call yet, this means that <tt/getty/
 has completed its open on the communications port.  This could
 indicate a problem with the cabling or a mis-configured modem, because
 <tt/getty/ should not be able to open the communications port until
 <tt/CD/ (carrier detect) has been asserted by the modem.
 
-If you don't see any <tt/getty/ processes waiting to open the desired
+If you do not see any <tt/getty/ processes waiting to open the desired
 <tt/ttyd?/ port, double-check your entries in <tt>/etc/ttys</tt> to
 see if there are any mistakes there.  Also, check the log file
 <tt>/var/log/messages</tt> to see if there are any log messages from
@@ -761,15 +761,15 @@ missing device special files.
 <p>
 
 Try dialing into the system; be sure to use 8 bits, no parity, 1 stop
-bit on the remote system.  If you don't get a prompt right away, or
+bit on the remote system.  If you do not get a prompt right away, or
 get garbage, try pressing <tt>&lt;Enter&gt;</tt> about once per
-second.  If you still don't see a <tt/login:/ prompt after a while,
+second.  If you still do not see a <tt/login:/ prompt after a while,
 try sending a <tt>BREAK</tt>.  If you are using a high-speed modem to
 do the dialing, try dialing again after locking the dialing modem's
 interface speed (via <tt>AT&amp;B1</tt> on a USR Sportster, for
 example).
 
-If you still can't get a <tt/login:/ prompt, check
+If you still cannot get a <tt/login:/ prompt, check
 <tt>/etc/gettytab</tt> again and double-check that
 
 <itemize>
@@ -784,14 +784,14 @@ name
 
 </itemize>
 
-If you dial but the modem on the FreeBSD system won't answer, make
+If you dial but the modem on the FreeBSD system will not answer, make
 sure that the modem is configured to answer the phone when <tt/DTR/ is
 asserted.  If the modem seems to be configured correctly, verify that
 the <tt/DTR/ line is asserted by checking the modem's indicator lights
 (if it has any).
 
-If you've gone over everything several times and it still doesn't work,
-take a break and come back to it later.  If it still doesn't work,
+If you have gone over everything several times and it still does not work,
+take a break and come back to it later.  If it still does not work,
 perhaps you can send an electronic mail message to the &a.questions
 describing your modem and youer problem, and the good folks on the list will
 try to help.
diff --git a/share/doc/handbook/diskless.sgml b/share/doc/handbook/diskless.sgml
index f26eedd541f6..a033fefebecc 100644
--- a/share/doc/handbook/diskless.sgml
+++ b/share/doc/handbook/diskless.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: diskless.sgml,v 1.2 1995/06/30 17:37:35 jfieber Exp $ -->
+<!-- $Id: diskless.sgml,v 1.3 1996/01/31 14:26:03 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Diskless operation<label id="diskless"></heading>
@@ -117,7 +117,7 @@ hostname myclient.mydomain
 
 	      <item> On HP-UX systems: The server should be
 		running HP-UX 9.04 or later for HP9000/800 series
-		machines.  Prior versions don't allow the
+		machines.  Prior versions do not allow the
 		creation of device files over NFS.
 
 	      <item> When extracting <tt>/dev</tt> in
diff --git a/share/doc/handbook/dma.sgml b/share/doc/handbook/dma.sgml
index 249217e34fe6..2c2b20a7dfd6 100644
--- a/share/doc/handbook/dma.sgml
+++ b/share/doc/handbook/dma.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: dma.sgml,v 1.2 1995/11/20 01:10:12 jfieber Exp $ -->
+<!-- $Id: dma.sgml,v 1.3 1996/01/31 14:26:03 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -156,7 +156,7 @@
 	If a peripheral wants to generate an interrupt when the
 	transfer of a buffer is complete, it can test for its
 	-DACK signal and the EOP signal both being asserted at
-	the same time.  When that happens, it means the DMA won't
+	the same time.  When that happens, it means the DMA will not
 	transfer any more information for that peripheral without
 	intervention by the CPU.  The peripheral can then assert
 	one of the interrupt signals to get the processors'
@@ -223,7 +223,7 @@
 	PC-compatible DMA cannot access locations above 16Meg.
 
 	To get around this restriction, operating systems will
-	reserve a buffer in an area below 16Meg that also doesn't
+	reserve a buffer in an area below 16Meg that also does not
 	span a physical 64K boundary.  Then the DMA will be
 	programmed to read data to that buffer.  Once the DMA has
 	moved the data into this buffer, the operating system
diff --git a/share/doc/handbook/eresources.sgml b/share/doc/handbook/eresources.sgml
index a37c84f45594..a00be0009e9b 100644
--- a/share/doc/handbook/eresources.sgml
+++ b/share/doc/handbook/eresources.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: eresources.sgml,v 1.21 1996/05/09 23:04:37 mpp Exp $ -->
+<!-- $Id: eresources.sgml,v 1.22 1996/05/11 09:24:45 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt>
@@ -23,7 +23,7 @@
         <heading>Mailing lists<label id="eresources:mail"></heading>
 
 <p>Though many of the FreeBSD development members read USENET, we cannot
-always guarantee that we'll get to your questions in a timely fashion
+always guarantee that we will get to your questions in a timely fashion
 (or at all) if you post them only to one of the comp.unix.bsd.freebsd.*
 groups.  By addressing your questions to the appropriate mailing list
 you will reach both us and a concentrated FreeBSD audience, invariably
@@ -118,11 +118,7 @@ cvs-usrsbin     /usr/src/usr.sbin    System binaries
 given list you simply mail to <em>listname</em><tt>@FreeBSD.ORG</tt>.  It
 will then be redistributed to mailing list members world-wide.
 
-To subscribe to a list, send mail to:
-<tscreen><verb>
-majordomo@FreeBSD.ORG
-</verb></tscreen>
-And include the keyword
+To subscribe to a list, send mail to &a.majordomo and include
 <tscreen><verb>
 subscribe <listname> [<optional address>]
 </verb></tscreen>
@@ -151,9 +147,9 @@ list of available commands, do this:
 help
 ^D
 </verb></tscreen>
-Again, we'd like to request that you keep discussion in the technical mailing
-lists on a technical track.  If you're only interested in the "high points"
-then it's suggested that you join freebsd-announce, which is intended only
+Again, we would like to request that you keep discussion in the technical mailing
+lists on a technical track.  If you are only interested in the "high points"
+then it is suggested that you join freebsd-announce, which is intended only
 for infrequent traffic.
 
 <sect1><heading>List charters</heading>
diff --git a/share/doc/handbook/esdi.sgml b/share/doc/handbook/esdi.sgml
index 5d784dfc72ff..858020bc2321 100644
--- a/share/doc/handbook/esdi.sgml
+++ b/share/doc/handbook/esdi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: esdi.sgml,v 1.5 1996/01/31 14:26:05 mpp Exp $ -->
+<!-- $Id: esdi.sgml,v 1.6 1996/01/31 19:02:56 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -40,7 +40,7 @@
 
 	Capacities of the drives are boosted by putting more sectors
 	on each track. Typical is 35 sectors per track, high capacity
-	drives I've seen were up to 54 sectors/track.
+	drives I have seen were up to 54 sectors/track.
 
 	Although ESDI has been largely obsoleted by IDE and SCSI interfaces,
 	the availability of free or cheap surplus drives makes them 
@@ -232,7 +232,7 @@
 	keep in mind that if you have multiple operating systems on the
 	same disk, all must use the same translation</em>
 
-	While on the subject of translations, I've seen one controller
+	While on the subject of translations, I have seen one controller
 	type (but there are probably more like this) offer the option
 	to logically split a drive in multiple partitions as a BIOS
 	option. I had select 1 drive == 1 partition because this
@@ -352,7 +352,7 @@ disk            wd3     at wdc1 drive 1
 
 	Before using NEFMT.EXE I tried to format the disk using the
 	ACB-2320 BIOS builtin formatter. This proved to be a show stopper,
-	because it didn't give me an option to disable spare sectoring.
+	because it did not give me an option to disable spare sectoring.
 	With spare sectoring enabled the FreeBSD installation
 	process broke down on the bad144 run.
 
diff --git a/share/doc/handbook/handbook.sgml b/share/doc/handbook/handbook.sgml
index 89c5f9f56141..17b0008b095d 100644
--- a/share/doc/handbook/handbook.sgml
+++ b/share/doc/handbook/handbook.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: handbook.sgml,v 1.46 1996/05/14 20:31:51 rich Exp $ -->
+<!-- $Id: handbook.sgml,v 1.47 1996/05/15 15:17:25 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
@@ -11,6 +11,10 @@
 <!ENTITY % authors SYSTEM "authors.sgml">
 %authors;
 
+<!-- Entity shorthand for mailing list email addresses -->
+<!ENTITY % lists SYSTEM "lists.sgml">
+%lists;
+
 <!-- Entity definitions for all the parts -->
 <!ENTITY % sections SYSTEM "sections.sgml">
 %sections;
diff --git a/share/doc/handbook/history.sgml b/share/doc/handbook/history.sgml
index 7b250b4d9074..b93bf044354a 100644
--- a/share/doc/handbook/history.sgml
+++ b/share/doc/handbook/history.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: history.sgml,v 1.12 1995/12/29 01:27:38 jkh Exp $ -->
+<!-- $Id: history.sgml,v 1.13 1996/01/31 14:26:07 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>A brief history of FreeBSD<label id="history"></heading>
@@ -9,11 +9,11 @@ The FreeBSD project had its genesis in the early part of 1993,
 partially as an outgrowth of the "Unofficial 386BSD Patchkit" by the
 patchkit's last 3 coordinators: Nate Williams, Rod Grimes and myself.
 David Greenman and Julian Elischer were also lurking in the background
-around this time, though they didn't come fully into the project until
+around this time, though they did not come fully into the project until
 a month or two after it was more or less officially launched.  Our
 original goal was to produce an intermediate snapshot of 386BSD in
 order to fix a number of problems with it that the patchkit mechanism
-just wasn't capable of solving.  Some of you may remember the early
+just was not capable of solving.  Some of you may remember the early
 working title for the project being "386BSD 0.5" or "386BSD Interim"
 in reference to that fact.
 
@@ -26,7 +26,7 @@ snapshot.  Those plans came to a rude halt when Bill Jolitz suddenly
 decided to withdraw his sanction from the project and without any
 clear indication of what would be done instead.
 
-It didn't take us long to decide that the goal remained worthwhile
+It did not take us long to decide that the goal remained worthwhile
 even without Bill's support, and so we adopted the name "FreeBSD",
 which was coined by David Greenman.  Our initial objectives were set
 after consulting with the system's current users, and once it became
@@ -79,7 +79,7 @@ easier to install FreeBSD 2.0.5 release in June of 1995.
 <em>Where to from here?</em>
 
 We just released FreeBSD 2.1.0 on November 19th, 1995 and, by all
-accounts, people are pretty happy with it.  We'll therefore continue
+accounts, people are pretty happy with it.  We will therefore continue
 with the 2.1-STABLE branch of FreeBSD (which actually began with 2.0.5)
 well into Q1 of 1996 with at least one additional release:
 FreeBSD 2.1.1.
@@ -90,7 +90,7 @@ where long term projects for everything from NFS v3 to PCCARD support
 are currently taking place.  Preliminary timelines suggest that development
 in 2.2 will begin slowing down and early release engineering simulations
 (2.2 SNAPshots) started in Q1 of 1996.  Given a favorable prognosis for 2.2's
-general health, a migration to 2.2 will then begin in early Q2 of '96 and
+general health, a migration to 2.2 will then begin in early Q2 of 1996 and
 a new 2.3 branch created for next-generation development.  Around the
 time that 2.2-RELEASE is produced (late Q2 1996), the 2.1.x lineage will
 also be phased out.
@@ -108,7 +108,7 @@ changes can propagate automatically to other users of FreeBSD.  Our
 centralized development model is designed for the convenience of the
 <em>users</em> of FreeBSD, who are thereby provided with an easy way of
 tracking one central code base, not to keep potential contributors out!
-Individuals who've shown a consistent and significant dedication to the project
+Individuals who hae shown a consistent and significant dedication to the project
 are even often asked to join the FreeBSD core team to help in setting
 the project's overall directions and goals, so truly no part of the project
 is closed to additional members.  All we ask of those wishing for closer
diff --git a/share/doc/handbook/hw.sgml b/share/doc/handbook/hw.sgml
index c095e78dc0ce..05011fd1e4d4 100644
--- a/share/doc/handbook/hw.sgml
+++ b/share/doc/handbook/hw.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: hw.sgml,v 1.19 1996/04/08 15:01:04 jfieber Exp $ -->
+<!-- $Id: hw.sgml,v 1.20 1996/05/09 23:04:43 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!-- 
@@ -42,7 +42,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 cannot 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.
@@ -52,9 +52,9 @@ Slippery when wet.  Beware of dog.
     <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pi-p55tp4xe.txt"
      name="P55TP4XE">
     motherboard appears to be a good choice for mid-to-high range Pentium
-    server and workstation systems.  If you're really looking for performance,
-    be also sure to get the <htmlurl url="http://asustek.asus.com.tw/Products/TB/mem-0002.html" name="pipelined burst cache module">.  I feel that it's worth
-    the extra cost.  If you're looking for a 486 class motherboard, you might
+    server and workstation systems.  If you are really looking for performance,
+    be also sure to get the <htmlurl url="http://asustek.asus.com.tw/Products/TB/mem-0002.html" name="pipelined burst cache module">.  I feel that it is worth
+    the extra cost.  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:  The Intel <htmlurl url="http://asustek.asus.com.tw/Products/TB/triton-intro.html" name="Triton"> chipset based motherboards do not offer memory
@@ -63,8 +63,8 @@ Slippery when wet.  Beware of dog.
     therefore want to wait for Intel's newest generation of motherboards
     based on the Orion chipset or investigate ASUS's SiS chipset based
     motherboard, the <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pi-p55sp4.txt" name="P55SP4">.  I have no personal experience with this
-    motherboard and have heard mixed reports - some say it's a fine MB, others
-    say that it's measurably slower than the Triton.  The only undisputed
+    motherboard and have heard mixed reports - some say it is a fine MB, others
+    say that it is measurably slower than the Triton.  The only undisputed
     advantage it offers is being available <em>now</em>. 
 
   <sect2><heading>Disk Controllers</heading>
@@ -75,7 +75,7 @@ Slippery when wet.  Beware of dog.
     1542CF for ISA, Buslogic Bt747c for EISA and Adaptec 2940 for PCI.
 
   <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
@@ -84,17 +84,17 @@ 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 the
     <htmlurl url="http://www.toshiba.com" name="Toshiba"> XM-3501B (now
     released in a caddy-less model called the XM-5401B) drive has always
-    performed well for me.  Generally speaking, most SCSI CDROM drives I've 
-    seen have been of pretty solid construction (probably because they don't 
+    performed well for me.  Generally speaking, most SCSI CDROM drives I have 
+    seen have been of pretty solid construction (probably because they do not
     occupy the lower end of the market, due to their higher price) and you
-    probably won't go wrong with an HP or NEC SCSI CDROM drive either.
+    probably will not go wrong with an HP or NEC SCSI CDROM drive either.
 
   <sect2><heading>Tape drives</heading>
    <p>I've had pretty good luck with both
@@ -104,7 +104,7 @@ Slippery when wet.  Beware of dog.
    <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.
 
@@ -114,7 +114,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 cannot 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.
 
@@ -123,7 +123,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!
@@ -137,7 +137,7 @@ Slippery when wet.  Beware of dog.
     will generally work as well.
 
    <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"
@@ -148,9 +148,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 committment 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.
@@ -159,12 +159,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
diff --git a/share/doc/handbook/install.sgml b/share/doc/handbook/install.sgml
index e32e279910a0..15b57c968728 100644
--- a/share/doc/handbook/install.sgml
+++ b/share/doc/handbook/install.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: install.sgml,v 1.27 1996/05/16 20:01:26 jkh Exp $ -->
+<!-- $Id: install.sgml,v 1.28 1996/05/16 20:20:57 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -351,10 +351,10 @@ Boot:
 	  There is not a lot of preparatory work that needs to be done to
 	  successfully install from one of Walnut Creek's FreeBSD CDROMs (other
 	  CDROM distributions may work as well, though we cannot say for certain
-	  as we have no hand or say in how they're created).  You can either
+	  as we have no hand or say in how they are created).  You can either
 	  boot into the CD installation directly from DOS using Walnut Creek's
 	  supplied ``install.bat'' batch file or you can make a boot floppy with
-	  the ``makeflp.bat'' command.  [NOTE:  If you're running
+	  the ``makeflp.bat'' command.  [NOTE:  If you are running
 	  FreeBSD 2.1-RELEASE and have an IDE CDROM, use the
 	  inst&lowbar;ide.bat or atapiflp.bat batch files instead].
 
@@ -375,8 +375,8 @@ Boot:
 	  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's necessary to first
-	  type: <tt>umount /cdrom</tt>.  Don't just remove it from the drive!
+	  Before removing the CD again, also note that it is necessary to first
+	  type: <tt>umount /cdrom</tt>.  Do not just remove it from the drive!
 
 	  <quote><bf>Special note:</bf> Before invoking the
 	    installation, be sure that the CDROM is in the drive
@@ -413,29 +413,29 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent
 
 	  The first floppy that you will need in addition to the boot.flp 
 	  image is ``floppies/root.flp'', which is somewhat special in that 
-	  it's not a DOS filesystem floppy at all, but rather a floppy "image" 
+	  it is not a DOS filesystem floppy at all, but rather a floppy "image" 
 	  (it's actually a gzip'd cpio file).  You can create this floppy in 
 	  the same way that you created the boot floppy <ref id="install"
 	    name="the beginning of this guide">.  Once this floppy is
 	  made, you can go on to make the distribution set floppies
-	  using ordinary DOS or UFS (if you're preparing the floppies on
+	  using ordinary DOS or UFS (if you are preparing the floppies on
 	  another FreeBSD machine) formatted diskettes.
 
 	  You will need, at minimum, as many 1.44MB or 1.2MB floppies as
 	  it takes to hold all files in the bin (binary distribution)
-	  directory.  If you're preparing these floppies under DOS, then
+	  directory.  If you are preparing these floppies under DOS, then
 	  THESE floppies *must* be formatted using the MS-DOS FORMAT
-	  command.  If you're using Windows, use the Windows File
+	  command.  If you are using Windows, use the Windows File
 	  Manager format command.
 
 	  Do <em>not</em> trust Factory Preformatted floppies!  Format
 	  them again yourself, just to make sure.  Many problems
 	  reported by our users in the past have resulted from the use
-	  of improperly formatted media, which is why I'm taking such
+	  of improperly formatted media, which is why I am taking such
 	  special care to mention it here!
 
-	  If you're creating the floppies from another FreeBSD machine,
-	  a format is still not a bad idea though you don't need to put
+	  If you are creating the floppies from another FreeBSD machine,
+	  a format is still not a bad idea though you do nott need to put
 	  a DOS filesystem on each floppy.  You can use the `disklabel'
 	  and `newfs' commands to put a UFS filesystem on them instead,
 	  as the following sequence of commands (for a 3.5" 1.44MB floppy
diff --git a/share/doc/handbook/kerberos.sgml b/share/doc/handbook/kerberos.sgml
index 1afa83259756..3807007bec7b 100644
--- a/share/doc/handbook/kerberos.sgml
+++ b/share/doc/handbook/kerberos.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kerberos.sgml,v 1.5 1995/09/27 00:46:21 jmz Exp $ -->
+<!-- $Id: kerberos.sgml,v 1.6 1996/01/03 13:13:16 gclarkii Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Kerberos<label id="kerberos"></heading>
@@ -30,7 +30,7 @@
  <heading>Creating the initial database</heading>
 
  <p>This is done on the Kerberos server only. First make sure that your
-    don't have any old Kerberos databases around. You should change to the
+    do not have any old Kerberos databases around. You should change to the
     directory <tt>/etc/kerberosIV</tt> and check that only the following
     files are present:
 
@@ -98,7 +98,7 @@ ARC.NASA.GOV trident.arc.nasa.gov
     realm. The rest of the lines show how to default systems of a
     particular subdomain to a named realm.
 
-    Now we're ready to create the database. This only needs to run on
+    Now we are ready to create the database. This only needs to run on
     the Kerberos server (or Key Distribution Centre). Issue the
     <tt>kdb_init</tt> command to do this:
 
diff --git a/share/doc/handbook/kernelconfig.sgml b/share/doc/handbook/kernelconfig.sgml
index 04d44906e3a4..06bc8c660d50 100644
--- a/share/doc/handbook/kernelconfig.sgml
+++ b/share/doc/handbook/kernelconfig.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kernelconfig.sgml,v 1.10 1996/05/09 23:04:46 mpp Exp $ -->
+<!-- $Id: kernelconfig.sgml,v 1.11 1996/05/15 15:17:26 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
   <chapt><heading>Configuring the FreeBSD Kernel<label id="kernelconfig"></heading>
@@ -77,7 +77,7 @@
 </verb></tscreen>
 	Traditionally, this name is in all capital letters and,
 	if you are maintaining multiple FreeBSD machines with
-	different hardware, it's a good idea to name it after
+	different hardware, it is a good idea to name it after
 	your machine's hostname.  We will call it MYKERNEL for
 	the purpose of this example.
 	
@@ -91,11 +91,11 @@
 	here, but is covered well in many books in the <ref
 	id="bibliography" name="bibliography">.  Feel free to change the
 	comment	lines at the top to reflect your configuration or the
-	changes you've made to differentiate it from GENERIC.
+	changes you have made to differentiate it from GENERIC.
 
-	If you've build a kernel under SunOS or some other BSD
+	If you have build a kernel under SunOS or some other BSD
 	operating system, much of this file will be very familiar
-	to you.  If you're coming from some other operating
+	to you.  If you are coming from some other operating
 	system such as DOS, on the other hand, the GENERIC
 	configuration file might seem overwhelming to you, so
 	follow the descriptions in the <ref
@@ -106,10 +106,10 @@
 	older version of FreeBSD, you will probably have to get a new
 	version of <tt>config(8)</tt> from the same place you got the new
 	kernel sources.  It is located in <tt>/usr/src/usr.sbin</tt>, so
-	you'll need to download those sources as well.  Re-build and install
+	you will need to download those sources as well.  Re-build and install
 	it before running the next commands.</quote>
 
-	When you're finished, type the following to compile and
+	When you are finished, type the following to compile and
 	install your kernel:
 <tscreen><verb>
 # /usr/sbin/config MYKERNEL
@@ -128,7 +128,7 @@
 	to recover in case your new kernel <ref
 	id="kernelconfig:noboot" name="does not boot">.
 
-	<quote><em/Note:/ If you've added any new devices (such
+	<quote><em/Note:/ If you have added any new devices (such
 	as sound cards) you may have to add some <ref
 	id="kernelconfig:nodes" name="device nodes"> to your
 	<tt>/dev</tt> directory before you can use them.</quote>
@@ -160,7 +160,7 @@
 	be dependant upon an option gets this option out of an
 	<tt>opt_<em>foo</em>.h</tt> declaration file created in the
 	compile directory by <tt>config</tt>.  The list of valid options
-	for <tt>config</tt> lives in two files: options that don't
+	for <tt>config</tt> lives in two files: options that do nott
 	depend on the architecture are listed in
 	<tt>/sys/conf/options</tt>, architecture-dependant ones
 	in <tt>/sys/<em>arch</em>/conf/options.<em>arch</em></tt>,
@@ -210,7 +210,7 @@
 	      this from GENERIC to whatever you named your
 	      kernel, in this example, MYKERNEL.  The value you
 	      put in <tt>ident</tt> will print when you boot up
-	      the kernel, so it's useful to give a kernel a
+	      the kernel, so it is useful to give a kernel a
 	      different name if you want to keep it separate from
 	      your usual kernel (if you want to build an
 	      experimental kernel, for example).  Note that, as
@@ -219,7 +219,7 @@
 	      contains any numbers.
 
 	      Since this name is passed to the C compiler as a
-	      <tt>-D</tt> switch, don't use names like <tt>
+	      <tt>-D</tt> switch, do not use names like <tt>
 	      DEBUG</tt>, or something that could be confused
 	      with another machine or CPU name, like <tt>vax</tt>.
 
@@ -231,7 +231,7 @@
 	      you expect to have on your machine.  However, under
 	      normal circumstances, you will want to set
 	      <tt>maxusers</tt> to at least four, especially if
-	      you're using X Windows or compiling software.  The
+	      you are using X Windows or compiling software.  The
 	      reason is that the most important table set by
 	      <tt>maxusers</tt> is the maximum number of
 	      processes, which is set to <bf><tt>20 + 16 *
@@ -336,7 +336,7 @@
 	      Windows, which many graphics-intensive programs
 	      (such as the movie player XAnim, and Linux DOOM)
 	      will automatically take advantage of for extra
-	      speed.  If you use X Windows, you'll definitely
+	      speed.  If you use X Windows, you will definitely
 	      want to include this.
 
 	    <tag>options SYSVSEM</tag> 
@@ -505,7 +505,7 @@
 	      <tt>wdc1</tt> is a secondary IDE controller where
 	      you might have a third or fourth hard drive, or an
 	      IDE CD-ROM.  Comment out the lines which do not
-	      apply (if you have a SCSI hard drive, you'll
+	      apply (if you have a SCSI hard drive, you will
 	      probably want to comment out all six lines, for
 	      example).
 
@@ -625,11 +625,11 @@
 	    <p>This causes the
 	      kernel to pause 15 seconds before probing each SCSI
 	      device in your system.  If you only have IDE hard
-	      drives, you can ignore this, otherwise you'll
+	      drives, you can ignore this, otherwise you will
 	      probably want to lower this number, perhaps to 5
 	      seconds, to speed up booting.  Of course if you do
 	      this, and FreeBSD has trouble recognizing your SCSI
-	      devices, you'll have to raise it back up.
+	      devices, you will have to raise it back up.
 
 	    <tag>controller scbus0</tag> 
 
@@ -797,7 +797,7 @@
 
 	    <p>The next lines enable support for various Ethernet
 	      cards.  If you do not have a network card, you can
-	      comment out all of these lines.  Otherwise, you'll
+	      comment out all of these lines.  Otherwise, you will
 	      want to leave in support for your particular
 	      Ethernet card(s):
 
@@ -869,7 +869,7 @@
 	      </descrip>
 
 	      <quote><em/Note:/ With certain cards (notably the
-		NE2000) you'll have to change the port and/or IRQ
+		NE2000) you will have to change the port and/or IRQ
 		since there is no ``standard'' location for these
 		cards.</quote>
 
@@ -946,7 +946,7 @@
 
 	<p>This is the first section containing lines that are
 	  not in the GENERIC kernel.  To include sound card
-	  support, you'll have to copy the appropriate lines from
+	  support, you will have to copy the appropriate lines from
 	  the LINT kernel (which contains support for
 	  <em>every</em> device) as follows:
 
@@ -1054,7 +1054,7 @@
 	    <tag>pseudo-device pty <em>number</em><label id="kernelconfig:ptys"></tag>
 
 	    <p><tt>pty</tt> is a ``pseudo-terminal'' or simulated
-	      login port.  It's used by incoming <bf>telnet</bf>
+	      login port.  It is used by incoming <bf>telnet</bf>
 	      and <bf>rlogin</bf> sessions, xterm, and some other
 	      applications such as emacs.  The <em>number</em>
 	      indicates the number of <tt>pty</tt>s to create.
@@ -1088,7 +1088,7 @@
 
 	<p>This section describes some miscellaneous hardware
 	  devices supported by FreeBSD.  Note that none of these
-	  lines are included in the GENERIC kernel, you'll have
+	  lines are included in the GENERIC kernel, you will have
 	  to copy them from this handbook or the LINT kernel
 	  (which contains support for <em>every</em> device):
 
@@ -1106,7 +1106,7 @@
 	      script that plays some simple songs, and
 	      <tt>/usr/games/piano</tt> which lets you play songs
 	      using the keyboard as a simple piano (this file
-	      only exists if you've installed the <em>games</em>
+	      only exists if you have installed the <em>games</em>
 	      package).  Also, the excellent text role-playing
 	      game NetHack (in the ports collection) can be
 	      configured to use this device to play songs when
@@ -1174,7 +1174,7 @@ controller wcd0
 
 	  <p>If the <tt>config</tt>
 	    command fails when you give it your kernel
-	    description, you've probably made a simple error
+	    description, you have probably made a simple error
 	    somewhere.  Fortunately, <tt>config</tt> will print
 	    the line number that it had trouble with, so you can
 	    quickly skip to it with <tt>vi</tt>.  For example, if
@@ -1244,7 +1244,7 @@ config: line 17: syntax error
 
 	  <tag>Kernel works, but <tt>ps</tt> does not work any more!</tag>
 
-	  <p>If you've installed a different version
+	  <p>If you have installed a different version
 	    of the kernel from the one that the system utilities
 	    have been built with, for example, an experimental
 	    ``2.2.0'' kernel on a 2.1.0-RELEASE system, many
diff --git a/share/doc/handbook/kerneldebug.sgml b/share/doc/handbook/kerneldebug.sgml
index 7476cdc97024..b3b46946ad8e 100644
--- a/share/doc/handbook/kerneldebug.sgml
+++ b/share/doc/handbook/kerneldebug.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kerneldebug.sgml,v 1.8 1996/01/31 19:02:59 mpp Exp $ -->
+<!-- $Id: kerneldebug.sgml,v 1.9 1996/03/14 02:52:06 adam Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
@@ -70,10 +70,10 @@
   and voila, you can debug the crash dump using the kernel sources
   just like you can for any other program.
 
-  Here's a script log of a <tt>kgdb</tt> session illustrating the
+  Here is a script log of a <tt>kgdb</tt> session illustrating the
   procedure.  Long
   lines have been folded to improve readability, and the lines are
-  numbered for reference.  Despite this, it's a real-world error
+  numbered for reference.  Despite this, it is a real-world error
   trace taken during the development of the pcvt console driver.
 <tscreen><verb>
    1:Script started on Fri Dec 30 23:15:22 1994
@@ -169,10 +169,10 @@
 <tag/line 36:/  Force usage of a new stack frame; this is no longer
             necessary now.  The stack frames are supposed to point to
             the right locations now, even in case of a trap.
-            (I don't have a new core dump handy &lt;g&gt;, my kernel
-            didn't panic for rather long.)
+            (I do not have a new core dump handy &lt;g&gt;, my kernel
+            did not panic for ia rather long time.)
             From looking at the code in source line 403,
-            there's a high probability that either the pointer
+            there is a high probability that either the pointer
             access for ``tp'' was messed up, or the array access was
             out of bounds.
 <tag/line 52:/  The pointer looks suspicious, but happens to be a valid
@@ -188,23 +188,23 @@
 <sect><heading>Post-mortem analysis of a dump</heading>
 
 <p>What do you do if a kernel dumped core but you did not expect
-  it, and it's therefore not compiled using <tt>config -g</tt>?
-  Not everything is lost here.  Don't panic!
+  it, and it is therefore not compiled using <tt>config -g</tt>?
+  Not everything is lost here.  Do not panic!
 
   Of course, you still need to enable crash dumps.  See above
-  on the options you've got in order to do this.
+  on the options you have to specify in order to do this.
 
   Go to your kernel compile directory, and edit the line
   containing <tt>COPTFLAGS?=-O</tt>.  Add the <tt>-g</tt> option
-  there (but <em>don't</em> change anything on the level of
+  there (but <em>do not</em> change anything on the level of
   optimization).  If you do already know roughly the probable
   location of the failing piece of code (e.g., the <tt>pcvt</tt>
   driver in the example above), remove all the object files for
   this code.  Rebuild the kernel. Due to the time stamp change on
   the Makefile, there will be some other object files rebuild,
   for example <tt>trap.o</tt>.  With a bit of luck, the added
-  <tt>-g</tt> option won't change anything for the generated
-  code, so you'll finally get a new kernel with similar code to
+  <tt>-g</tt> option will not change anything for the generated
+  code, so you will finally get a new kernel with similar code to
   the faulting one but some debugging symbols.  You should at
   least verify the old and new sizes with the <tt>size(1)</tt> command. If
   there is a mismatch, you probably need to give up here.
@@ -226,8 +226,8 @@
   The most important ones being breakpointing and single-stepping
   kernel code.
 
-  If you need to do low-level debugging on your kernel, there's
-  an on- line debugger available called DDB.  It allows to
+  If you need to do low-level debugging on your kernel, there is
+  an on-line debugger available called DDB.  It allows to
   setting breakpoints, single-steping kernel functions, examining
   and changing kernel variables, etc.  However, it cannot not
   access kernel source files, and only has access to the global
@@ -255,7 +255,7 @@
   The second scenario is a hot-key on the keyboard, usually
   Ctrl-Alt-ESC.  For syscons, this can be remapped, and some of
   the distributed maps do this, so watch out.
-  There's an option
+  There is an option
   available for serial consoles
   that allows the use of a serial line BREAK on the console line to
   enter DDB (``<tt>options BREAK_TO_DEBUGGER</tt>''
@@ -314,7 +314,7 @@
 <tscreen><verb>
   n
 </verb></tscreen>
-  <bf>Note:</bf> this is different from <tt>gdb</tt>'s `next' statement, it's like
+  <bf>Note:</bf> this is different from <tt>gdb</tt>'s `next' statement, it is like
   <tt>gdb</tt>'s `finish'.
 
   To examine data from memory, use (for example):
@@ -405,9 +405,9 @@
 <tscreen><verb>
   help
 </verb></tscreen>
-  However, it's highly recommended to have a printed copy of the
+  However, it is highly recommended to have a printed copy of the
   <tt>ddb(4)</tt> manual page ready for a debugging session.
-  Remember that it's hard to read the on-line manual while
+  Remember that it is hard to read the on-line manual while
   single-stepping the kernel.
 
 
diff --git a/share/doc/handbook/linuxemu.sgml b/share/doc/handbook/linuxemu.sgml
index b6cdda899ef0..26581272321c 100644
--- a/share/doc/handbook/linuxemu.sgml
+++ b/share/doc/handbook/linuxemu.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: linuxemu.sgml,v 1.2 1996/05/15 15:17:28 jfieber Exp $ -->
+<!-- $Id: linuxemu.sgml,v 1.3 1996/05/16 22:50:29 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Linux Emulation<label id="linuxemu"></heading>
@@ -7,7 +7,7 @@
 
 <sect><heading>How to install the Linux emulator</heading>
 
-<p>Linux emulation in FreeBSD has reached a point where it's possible
+<p>Linux emulation in FreeBSD has reached a point where it is possible
 to run a large fraction of Linux binaries in both a.out and ELF
 format.  The linux emulation in the -STABLE branch is capable of
 running Linux DOOM and Mathematica; the version present in
@@ -126,7 +126,7 @@ linux
 <p>In -current it is no longer necessary to specify options "LINUX" 
 or options "COMPAT_LINUX".  Linux emulation is done with an LKM 
 (``Loadable Kernel Module'') so it can be installed on the fly without
-having to reboot.  You'll need the following things in your startup files, 
+having to reboot.  You will need the following things in your startup files, 
 however:
 <enum>
 <item> In <tt>/etc/sysconfig</tt>, you need the following line:
@@ -143,7 +143,7 @@ fi
 </verb>
 </enum>
 
-<p>If you want to verify it's running, <tt>modstat</tt> will do that:
+<p>If you want to verify it is running, <tt>modstat</tt> will do that:
 <tscreen>
 <verb>
 % modstat
@@ -168,9 +168,9 @@ and Installing a Custom Kernel">.
 
 <sect2><heading>Installing using the linux_lib port</heading>
 
-<p>Most linux applications use shared libraries, so you're still not
-done untill you install the shared libraries.  It's possible to do
-this by hand, however, it's vastly simpler to just grab the
+<p>Most linux applications use shared libraries, so you are still not
+done untill you install the shared libraries.  It is possible to do
+this by hand, however, it is vastly simpler to just grab the
 <tt>linux_lib</tt> port:
 <tscreen>
 <verb>
@@ -186,12 +186,12 @@ linux binaries linked against the ZMAGIC libraries; QMAGIC libraries
 Linuxulator heartburn.  As of this writing (March 1996) ELF emulation
 is still in the formulative stages but seems to work pretty well.  Also, 
 expect some programs to complain about incorrect minor versions.  In 
-general this doesn't seem to be a problem.
+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
-libraries by hand instead.  You'll need the Linux shared libraries
+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
 libraries on your FreeBSD system.  Any shared libraries opened by
@@ -250,7 +250,7 @@ these files on your FreeBSD system:
 
 <p>Note that if you already have a Linux shared library with a
 matching major revision number to the first column of the 'ldd'
-output, you won't need to copy the file named in the last column to
+output, you will not need to copy the file named in the last column to
 your system, the one you already have should work. It is advisable to
 copy the shared library anyway if it is a newer version, though. You
 can remove the old one, as long as you make the symbolic link point to
@@ -266,8 +266,8 @@ according to the output of ldd:
 libc.so.4 (DLL Jump 4.5pl26) -> libc.so.4.6.29
 </verb>
 
-If it's only one or two versions out of date in the in the trailing
-digit then don't worry about copying /lib/libc.so.4.6.29 too, because
+If it is only one or two versions out of date in the in the trailing
+digit then do not worry about copying /lib/libc.so.4.6.29 too, because
 the program should work fine with the slightly older version.
 However, if you like you can decide to replace the libc.so anyway, and
 that should leave you with:
@@ -278,7 +278,7 @@ that should leave you with:
 
 <p>Please note that the symbolic link mechanism is <em>only</em>
 needed for Linux binaries, the FreeBSD runtime linker takes care of
-looking for matching major revision numbers itself, you don't need to
+looking for matching major revision numbers itself, you do not need to
 worry about that.
 
 <sect2><heading>Configuring the ld.so -- for FreeBSD-current
@@ -296,9 +296,9 @@ place on your FreeBSD system (to the /compat/linux tree):
 /compat/linux/etc/ld.so.config
 </verb>
 
-<p>If you don't have access to a Linux system, you should get the
+<p>If you do nott have access to a Linux system, you should get the
 extra files you need from various ftp sites.  Information on where to
-look for the various files is appended below. For now, let's assume
+look for the various files is appended below. For now, let us assume
 you know where to get the files.
 
 <p>
@@ -312,9 +312,9 @@ version mismatches), and install them under /compat/linux
 /lib/ld.so
 </verb>
 
-<p>ldconfig and ldd don't necessarily need to be under /compat/linux,
+<p>ldconfig and ldd do not necessarily need to be under /compat/linux,
 you can install them elsewhere in the system too. Just make sure they
-don't conflict with their FreeBSD counterparts. A good idea would be
+do not conflict with their FreeBSD counterparts. A good idea would be
 to install them in /usr/local/bin as ldconfig-linux and ldd-linux.
 <p>
 Create the file /compat/linux/etc/ld.so.conf, containing the
@@ -339,7 +339,7 @@ in order for the emulator to find them.
 % /compat/linux/sbin/ldconfig 
 </verb>
 
-<p>Ldconfig is statically linked, so it doesn't need any shared
+<p>Ldconfig is statically linked, so it does not need any shared
 libraries to run.  It creates the file /compat/linux/etc/ld.so.cache
 which contains the names of all the shared libraries. It should rerun
 to recreate this file whenever you install additional shared
@@ -347,7 +347,7 @@ libraries.
 
 On FreeBSD-stable do not install /compat/linux/etc/ld.so.cache or run
 ldconfig becuase in FreeBSD-stable the syscalls are implemented
-differently and ldconfig isn't needed or used.
+differently and ldconfig is not needed or used.
 
 <p>You should now be set up for Linux binaries which only need a
 shared libc. You can test this by running the Linux ldd on
@@ -394,7 +394,7 @@ multi on
 </tscreen>
 
 where the order here specifies that /etc/hosts is searched first and
-DNS is searched second.  When /compat/linux/etc/host.conf isn't
+DNS is searched second.  When /compat/linux/etc/host.conf is not
 installed linux applications find FreeBSD's /etc/host.conf and
 complain about the incompatible FreeBSD syntax.  You should remove
 `bind,' if you have not configured a name-server using the
@@ -441,9 +441,9 @@ ftp.demon.co.uk:/pub/linux/distributions
 src.doc.ic.ac.uk:/packages/linux/distributions
 </verb>
 
-<p>For simplicity, let's concentrate on Slackware here. This
+<p>For simplicity, let us concentrate on Slackware here. This
 distribution consists of a number of subdirectories, containing
-separate packages.  Normally, they're controlled by an install
+separate packages.  Normally, they are controlled by an install
 program, but you can retrieve files "by hand" too. First of all, you
 will need to look in the "contents" subdir of the distribution. You
 will find a lot of small text files here describing the contents of the
diff --git a/share/doc/handbook/lists.sgml b/share/doc/handbook/lists.sgml
new file mode 100644
index 000000000000..5181df966ca3
--- /dev/null
+++ b/share/doc/handbook/lists.sgml
@@ -0,0 +1,57 @@
+<!-- $Id: authors.sgml,v 1.20 1996/05/09 23:04:30 mpp Exp $ -->
+<!-- The FreeBSD Documentation Project -->
+
+<!-- 
+Names and email address of contributing authors and CVS committers
+and some of the common FreeBSD mailing lists.  Use these
+entities when referencing people or mailing lists.  Please 
+note the use of single
+and double quotes.  
+-->
+
+<!ENTITY a.announce "FreeBSD announcments mailing list
+  <tt><htmlurl url='mailto:freebsd-announce@FreeBSD.ORG'
+  name='&lt;freebsd-announce@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.doc "FreeBSD documentation project mailing list
+  <tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
+  name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.bugs "FreeBSD problem reports mailing list
+  <tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
+  name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.current "FreeBSD-current mailing list
+  <tt><htmlurl url='mailto:freebsd-current@FreeBSD.ORG'
+  name='&lt;freebsd-current@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.emulation "FreeBSD-emulation mailing list
+  <tt><htmlurl url='mailto:freebsd-emulation@FreeBSD.ORG'
+  name='&lt;freebsd-emulation@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.fs "FreeBSD filesystem project mailing list
+  <tt><htmlurl url='mailto:freebsd-fs@FreeBSD.ORG'
+  name='&lt;freebsd-fs@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.hackers "FreeBSD technical discussions mailing list
+  <tt><htmlurl url='mailto:freebsd-hackers@FreeBSD.ORG'
+  name='&lt;freebsd-hackers@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.ports "FreeBSD ports mailing list
+  <tt><htmlurl url='mailto:freebsd-ports@FreeBSD.ORG'
+  name='&lt;freebsd-ports@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.questions "FreeBSD general questions mailing list
+  <tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
+  name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.scsi "FreeBSD SCSI subsystem mailing list
+  <tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
+  name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.stable "FreeBSD-stable mailing list
+  <tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
+  name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
+
+<!ENTITY a.majordomo "<tt><htmlurl url='mailto:majordomo@FreeBSD.ORG'
+  name='&lt;majordomo@FreeBSD.ORG&gt;'></tt>">
diff --git a/share/doc/handbook/memoryuse.sgml b/share/doc/handbook/memoryuse.sgml
index 2cec37d4b213..5a4d9f4a88a9 100644
--- a/share/doc/handbook/memoryuse.sgml
+++ b/share/doc/handbook/memoryuse.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: memoryuse.sgml,v 1.5 1995/12/19 10:21:07 gclarkii Exp $ -->
+<!-- $Id: memoryuse.sgml,v 1.6 1996/01/31 19:02:59 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>PC memory utilization<label id="memoryuse"></heading>
@@ -16,7 +16,7 @@ for the <tt>%cs</tt> selector, done by an <tt>ljmp</tt>.)
 It then loads the first 15 sectors at <tt>0x10000</tt> (segment BOOTSEG in the
 biosboot Makefile), and sets up the stack to work below <tt>0x1fff0</tt>.
 After this, it jumps to the entry of boot2 within that code.  I.e., it
-jumps over itself and the (dummy) partition table, and it's going to
+jumps over itself and the (dummy) partition table, and it is going to
 adjust the %cs selector---we are still in 16-bit mode there.
 
 boot2 asks for the boot file, and examines the <tt>a.out</tt> header.  It masks
diff --git a/share/doc/handbook/nfs.sgml b/share/doc/handbook/nfs.sgml
index d79c6cee9085..c83047f913b2 100644
--- a/share/doc/handbook/nfs.sgml
+++ b/share/doc/handbook/nfs.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: nfs.sgml,v 1.4 1995/12/04 17:58:42 jfieber Exp $ -->
+<!-- $Id: nfs.sgml,v 1.5 1996/01/22 17:44:30 roberto Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>NFS<label id="nfs"></heading>
@@ -34,7 +34,7 @@ It should be noted that there is a different problem,
 sometimes mistaken for this one,
 when the NFS servers and clients are on different networks.
 If that is the case, make CERTAIN that your routers are routing the
-necessary UDP information, or you won't get anywhere, no matter
+necessary UDP information, or you will not get anywhere, no matter
 what else you are doing.
 
 In the following examples, "fastws" is the host (interface) name of a
diff --git a/share/doc/handbook/nutshell.sgml b/share/doc/handbook/nutshell.sgml
index 63b59563e268..e9ff625e3d65 100644
--- a/share/doc/handbook/nutshell.sgml
+++ b/share/doc/handbook/nutshell.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: nutshell.sgml,v 1.7 1995/12/19 09:22:23 gclarkii Exp $ -->
+<!-- $Id: nutshell.sgml,v 1.8 1996/01/31 14:26:12 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>FreeBSD in a nutshell<label id="nutshell"></heading>
@@ -77,7 +77,7 @@
       limited only by your own imagination.  From software
       development to factory automation, inventory control to
       azimuth correction of remote satellite antennae; if it can
-      be done with a commercial UNIX product then it's more than
+      be done with a commercial UNIX product then it is more than
       likely that you can do it with FreeBSD, too!  FreeBSD also
       benefits significantly from the literally thousands of high
       quality applications developed by research centers and
diff --git a/share/doc/handbook/porting.sgml b/share/doc/handbook/porting.sgml
index 9870e49a65ca..1e31fb8b268e 100644
--- a/share/doc/handbook/porting.sgml
+++ b/share/doc/handbook/porting.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.18 1996/04/10 06:32:42 asami Exp $ -->
+<!-- $Id: porting.sgml,v 1.19 1996/05/09 23:04:48 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@@ -8,11 +8,11 @@
 
 <p>The porting of freely available software, while perhaps not as
 gratifying as developing your own from scratch, is still a vital part
-of FreeBSD's growth and of great usefulness to those who wouldn't
+of FreeBSD's growth and of great usefulness to those who would not
 otherwise know where to turn for it.  All ported software is organized
 into a carefully organized hierarchy know as ``the ports collection''.
 The collection enables a new user to get a quick and complete overview
-of what's available for FreeBSD in an easy-to-compile form.  It also
+of what is available for FreeBSD in an easy-to-compile form.  It also
 saves considerable space by not actually containing the the majority
 of the sources being ported, but merely those differences required for
 running under FreeBSD. 
@@ -37,7 +37,7 @@ the ports collection.
 	once the file has been loaded.
 
       <p>You may come across code that needs modifications or
-	conditional compilation based upon what version of UNIX it's
+	conditional compilation based upon what version of UNIX it is
 	running under.  If you need to make such changes to the code
 	for conditional compilation, make sure you make the changes as
 	general as possible so that we can back-port code to FreeBSD
@@ -89,13 +89,13 @@ the ports collection.
 	  Berkeleyisms, not FreeBSD changes.
 
 	<item>In FreeBSD 2.x, <tt>__FreeBSD__</tt> is defined to be
-	  <tt>2</tt>.  In earlier versions, it's <tt>1</tt>.
+	  <tt>2</tt>.  In earlier versions, it is <tt>1</tt>.
 
 	<item>If you need to tell the difference between a FreeBSD 1.x
 	  system and a FreeBSD 2.x system, usually the right answer is
 	  to use the <tt>BSD</tt> macros described above.  If there
 	  actually is a FreeBSD specific change (such as special
-	  shared library options when using `<tt>ld</tt>') then it's
+	  shared library options when using `<tt>ld</tt>') then it is
 	  OK to use <tt>__FreeBSD__</tt> and `<tt>#if __FreeBSD__ &gt;
 	  1</tt>' to detect a FreeBSD 2.x system.
 
@@ -126,14 +126,14 @@ The pattern is the year followed by the month.
       <p>In the dozens of ports that have been done, there have
 	only been one or two cases where <tt>__FreeBSD__</tt>
 	should have been used.  Just because an earlier port
-	screwed up and used it in the wrong place doesn't mean
+	screwed up and used it in the wrong place does not mean
 	you should do so too.
 
     <sect2>
       <heading>Quick Porting</heading>
 
       <p>This section tells you how to do a quick port.  In many
-	cases, it is not enough, but we'll see.
+	cases, it is not enough, but we will see.
 
       <p>First, get the original tarball and put it into
 	<tt>&dollar;{DISTDIR}</tt>, which defaults to
@@ -142,7 +142,7 @@ The pattern is the year followed by the month.
       <p>Note: The following assumes that the software compiled
 	out-of-the-box, i.e., there was absolutely no change required
 	for the port to work on your FreeBSD box.  If you needed to
-	change something, you'll have to refer to the next section
+	change something, you will have to refer to the next section
 	too.
 
       <sect3>
@@ -156,7 +156,7 @@ The pattern is the year followed by the month.
  # Date created:		5 December 1994
  # Whom:			asami
  #
- # $Id: porting.sgml,v 1.18 1996/04/10 06:32:42 asami Exp $
+ # $Id: porting.sgml,v 1.19 1996/05/09 23:04:48 mpp Exp $
  #
  
  DISTNAME=	oneko-1.1b
@@ -170,7 +170,7 @@ The pattern is the year followed by the month.
  .include <bsd.port.mk>
 </verb></tscreen>
 
-      <p>See if you can figure it out.  Don't worry about the contents
+      <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.
@@ -201,7 +201,7 @@ A cat chasing a mouse all over the screen
 	    sufficient.  Note: This is <em>not</em> a manual nor an
 	    in-depth description on how to use or compile the port.
 	    In particular, please do not just copy the <tt>README</tt>
-	    file here, unless, of course, it's a concise description
+	    file here, unless, of course, it is a concise description
 	    of the port.
 
 	  <p>It is recommended that you sign the name at the end of
@@ -257,7 +257,7 @@ lib/X11/oneko/mouse.xpm
       <sect3>
 	<heading>Submitting the port</heading>
 
-	<p>Now that you're happy with your port, the only thing
+	<p>Now that you are happy with your port, the only thing
 	  remaining is to put it in the main FreeBSD ports tree and
 	  make everybody else happy about it too.  To accomplish this,
 	  pack the necessary files (everything described in this
@@ -276,8 +276,8 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
     <sect2>
       <heading>Slow Porting</heading>
 
-      <p>Ok, so it wasn't that simple, and the port required some
-	modifications to get it to work.  In this section, we'll
+      <p>Ok, so it was not that simple, and the port required some
+	modifications to get it to work.  In this section, we will
 	explain, step by step, how to modify it to get it to work with 
 	the ports paradigm.
 
@@ -289,7 +289,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
 	  and you may find that having <tt>bsd.port.mk</tt> in another
 	  window while you read this really helps to understand it.
 
-	<p>But don't worry if you don't really understand what
+	<p>But do not worry if you do not really understand what
 	  <tt>bsd.port.mk</tt> is doing, not many people
 	  do... <tt>:&gt;</tt>
 
@@ -364,7 +364,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
 	  targets `<tt>do-&lt;something&gt;</tt>'.  For example, the
 	  commands to extract a port are in the target
 	  `<tt>do-extract</tt>'.  If you are not happy with the
-	  default target, and you can't fix it by redefining the
+	  default target, and you cannot fix it by redefining the
 	  `<tt>do-&lt;something&gt;</tt>' target in your Makefile.
 
 	<p>Note that the `main' targets (e.g., <tt>extract</tt>,
@@ -375,7 +375,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
 	  <tt>do-extract</tt>, but never ever touch <tt>extract</tt>!
 
 	<p>Now that you understand what goes on when the user types
-	  `<tt>make</tt>', let's go through the recommended steps to
+	  `<tt>make</tt>', let us go through the recommended steps to
 	  create the perfect port.
 
       <sect3>
@@ -386,7 +386,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
 	  and copy it into <tt>&dollar;{DISTDIR}</tt>.  Always use
 	  <em>mainstream</em> sources when and where you can.
 
-	<p>If you can't find a ftp site that is well-connected to the
+	<p>If you cannot find a ftp site that is well-connected to the
 	  net, or can only find sites that have irritatingly
 	  non-standard formats, we can `house' it ourselves by putting
 	  it on
@@ -398,7 +398,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
 
 	<p>If your port requires some additional `patches' that are
 	  available on the Internet, fetch them too and put them in
-	  <tt>&dollar;{DISTDIR}</tt>.  Don't worry if they come from
+	  <tt>&dollar;{DISTDIR}</tt>.  Do not worry if they come from
 	  site other than where you got the the main source tarball,
 	  we have a way to handle these situations (see the
 	  description of <tt>&dollar;{PATCHFILES}</tt> below).
@@ -429,7 +429,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
 	<p>In the preparation of the port, files that have been added
 	  or changed can be picked up with a recursive diff for later
 	  feeding to patch.  This is the easiest kind of change to
-	  make as it doesn't involve any mucking around with
+	  make as it does not involve any mucking around with
 	  configuration files.  Each set of patches you wish to apply
 	  should be collected into a file named
 	  `<tt>patch-&lt;xx&gt;</tt>' where <tt>&lt;xx&gt;</tt>
@@ -499,7 +499,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
 	  distribution file list (<tt>&dollar;{DISTFILES}</tt>) to be
 	  named
 	  <tt>&dollar;{DISTNAME}&dollar;{EXTRACT_SUFX}</tt>
-	  by default which, if it's a normal tarball, is going to be
+	  by default which, if it is a normal tarball, is going to be
 	  something like:
 <tscreen><verb>	
 foozolix-1.0.tar.gz
@@ -544,11 +544,11 @@ work/foozolix-1.0/
 	  record the directory containing the tarball in
 	  <tt>&dollar;{MASTER_SITES}</tt>.  This will provide a backup
 	  site, as well as a direct pointer to the original source
-	  location.  Don't forget the trailing slash (<tt>/</tt>)!
+	  location.  Do not forget the trailing slash (<tt>/</tt>)!
 
  	<p>The make macros will try to use this specification for
 	  grabbing the distribution file with <tt>&dollar;{NCFTP}</tt>
-	  if they can't find it already on the system.
+	  if they cannot find it already on the system.
 
 	<p>It is recommended that you put multiple sites on this list,
 	  preferably from different continents.  This will safeguard
@@ -571,7 +571,7 @@ work/foozolix-1.0/
 	  patch has an extra `<tt>foozolix-1.0/</tt>' in front of the
 	  filenames, then set `<tt>PATCH_DIST_STRIP=-p1</tt>'.
 
-	<p>Don't worry if the patches are compressed, they will be
+	<p>Do not worry if the patches are compressed, they will be
 	  decompressed automatically if the filenames end with
 	  `<tt>.gz</tt>' or `<tt>.Z</tt>'.
 
@@ -590,13 +590,13 @@ work/foozolix-1.0/
 	    depends on.  It is a list of `<tt>lib:dir</tt>' pairs
 	    where <tt>lib</tt> is the name of the shared library, and
 	    <tt>dir</tt> is the directory in which to find it in case
-	    it's not available.  For example,
+	    it is not available.  For example,
 <tscreen><verb>
 LIB_DEPENDS=    tcl\\.7\\.:${PORTSDIR}/lang/tcl
 </verb></tscreen>
 	    will check for a shared tcl library with major version 7,
 	    and descend into the <tt>lang/tcl</tt> subdirectory of
-	    your ports tree to build and install it if it's not found.
+	    your ports tree to build and install it if it is not found.
 
 	    Note that the <tt>lib</tt> part is just an argument given
 	    to `<tt>ldconfig -r | grep</tt>', so periods should be
@@ -607,13 +607,13 @@ LIB_DEPENDS=    tcl\\.7\\.:${PORTSDIR}/lang/tcl
 	    during run-time.  It is a list of `<tt>exec:dir</tt>'
 	    pairs where <tt>exec</tt> is the name of the executable,
 	    and <tt>dir</tt> is the directory in which to find it in
-	    case it's not available.  For example,
+	    case it is not available.  For example,
 <tscreen><verb>
 RUN_DEPENDS=   wish:${PORTSDIR}/x11/tk
 </verb></tscreen>
 	    will check for an executable called `<tt>wish</tt>', and
 	    descend into the <tt>x11/tk</tt> subdirectory of your
-	    ports tree to build and install it if it's not found.
+	    ports tree to build and install it if it is not found.
 
 	    The dependency is checked from within the <tt>install</tt>
 	    target.  Also, the name of the dependency is put in to the 
@@ -629,7 +629,7 @@ BUILD_DEPENDS=   unzip:${PORTSDIR}/archivers/unzip
 </verb></tscreen>
 	    will check for an executable called `<tt>unzip</tt>', and
 	    descend into the <tt>archivers/unzip</tt> subdirectory of
-	    your ports tree to build and install it if it's not found.
+	    your ports tree to build and install it if it is not found.
 
 	    Note that `build' here means everything from extracting to 
 	    compilation.  The dependency is checked from within the
@@ -644,13 +644,13 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 </verb></tscreen>
 	    will check for an executable called `<tt>ncftp2</tt>', and
 	    descend into the <tt>net/ncftp2</tt> subdirectory of
-	    your ports tree to build and install it if it's not found.
+	    your ports tree to build and install it if it is not found.
 
 	    The dependency is checked from within the <tt>fetch</tt>
 	    target.
 	<sect4>
 	  <heading>DEPENDS</heading>
-	  <p>If there is a dependency that doesn't fall into either of
+	  <p>If there is a dependency that does not fall into either of
 	    the above four categories, or your port requires to have
 	    the source of the other port extracted (i.e., having them
 	    installed is not enough), then use this variable.  This is
@@ -681,7 +681,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 
       <sect3>
 	<heading>NO_INSTALL_MANPAGES</heading>
-	<p>If the port uses imake but doesn't understand the
+	<p>If the port uses imake but does not understand the
 	  `<tt>install.man</tt>' target,
 	  `<tt>NO_INSTALL_MANPAGES=yes</tt>' should be set.  In
 	  addition, the author of the original port should be shot.
@@ -696,18 +696,18 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 
       <p>Note that it is your responsibility as a porter to read the
 	licensing terms of the software and make sure that the FreeBSD
-	project won't held accountable of violating them by
+	project will not be held accountable of violating them by
 	redistributing the source or compiled binaries either via ftp
 	or CD-ROM.  If in doubt, please contact the &a.ports;.
 
       <p>We usually get around this problem by setting
 	<tt>&dollar;{NO_PACKAGE}</tt> in the Makefile, and not putting
 	the distfile up for ftp.  However, for most cases, you should
-	at least be able to make a port, so don't let the license
+	at least be able to make a port, so do not let the license
 	scare you away!
 
       <p>Note: The GNU General Public License (GPL), both version 1
-	and 2, shouldn't be a problem for ports.
+	and 2, should not be a problem for ports.
 
       <p>Note: If you are a committer, make sure you update the
 	<tt>ports/LEGAL</tt> file too.
@@ -719,15 +719,15 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
     <sect2>
       <heading>Do's and Dont's</heading>
 
-      <p>Here's a list of common do's and dont's that you encounter
+      <p>Here is a list of common do's and dont's that you encounter
 	during the porting process.
 
       <sect3>
 	<heading>WRKDIR</heading>
-	<p>Don't leave anything valuable lying around in the
+	<p>Do not leave anything valuable lying around in the
 	  `<tt>work</tt>' subdirectory, `<tt>make clean</tt>' will
 	  <em>nuke</em> it completely!  If you need auxiliary files
-	  that aren't scripts or patches, put them in the subdirectory
+	  that are not scripts or patches, put them in the subdirectory
 	  `<tt>files</tt>' and use the <tt>post-extract</tt> target to
 	  copy them to the `<tt>work</tt>' subdirectory.
 
@@ -745,7 +745,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 	  <tt>post-install</tt> rule to do it yourself.  Make sure
 	  that you check the variable <tt>NOMANCOMPRESS</tt> that the
 	  user can set in <tt>/etc/make.conf</tt> to disable man page
-	  compression.  Here's an example:
+	  compression.  Here is an example:
 <tscreen><verb>
  post-install:
 	 strip ${PREFIX}/bin/xdl
@@ -756,7 +756,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 
 	<p>Use the <tt>file</tt> command on the installed executable
 	  to check whether the binary is stripped or not.  If it
-	  doesn't say `not stripped', it is stripped.
+	  does not say `not stripped', it is stripped.
 
       <sect3>
 	<heading>Install additional documentation</heading>
@@ -784,14 +784,14 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
  .endif
 </verb></tscreen>
 
-	<p>Don't forget to add them to <tt>pkg/PLIST</tt> too!  (Don't
+	<p>Do not forget to add them to <tt>pkg/PLIST</tt> too!  (Do not
 	  worry about <tt>NOPORTDOCS</tt> here; there is currently no
 	  way for the packages to read variables from
 	  <tt>/etc/make.conf</tt>.)
 
       <sect3>
 	<heading>DIST_SUBDIR</heading>
-	<p>Don't let your port clutter <tt>/usr/ports/distfiles</tt>.  If
+	<p>Do not let your port clutter <tt>/usr/ports/distfiles</tt>.  If
 	  your port requires a lot of files (including patchfiles) to be
 	  fetched, or contains a file that has a name that might conflict
 	  with other ports (e.g., `Makefile'), set
@@ -813,12 +813,12 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 
       <sect3>
 	<heading>Custom utilities</heading>
-	<p>Don't rely on custom utilities in your local configure
+	<p>Do not rely on custom utilities in your local configure
 	  script or anything -- they may not be there on the user's
 	  system!  If you really need something else to be installed
 	  before you can work, detect this from your configure script,
 	  print a helpful message and exit with a non-zero status!  At
-	  least you'll have given the user some idea of what's needed.
+	  least you will have given the user some idea of what is needed.
 	  If the custom utility or package is actually part of the
 	  ports tree, this should be dealt by the dependency mechanism
 	  of ports.
@@ -841,7 +841,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 
       <sect3>
 	<heading>RCS strings</heading>
-	<p>Don't put RCS strings in patches.  CVS will mangle them
+	<p>Do not put RCS strings in patches.  CVS will mangle them
 	  when we put the files into the ports tree, and when we check
 	  them out again, they will come out different and the patch
 	  will fail.  RCS strings are surrounded by dollar
@@ -874,7 +874,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 	  able to cater to the needs of other sites.  For X ports that use
 	  imake, this is automatic; otherwise, this can often be done by
 	  simply replacing the occurrences of `<tt>/usr/local</tt>' (or
-	  `<tt>/usr/X11R6</tt>' for X ports that don't use imake) in the
+	  `<tt>/usr/X11R6</tt>' for X ports that do not use imake) in the
 	  various scripts/Makefiles in the port to read
 	  `<tt>&dollar;{PREFIX}</tt>', as this variable is automatically
 	  passed down to every stage of the build and install processes.
@@ -882,7 +882,7 @@ FETCH_DEPENDS=   ncftp2:${PORTSDIR}/net/ncftp2
 	<p>The variable <tt>&dollar;{PREFIX}</tt> can be reassigned in your
 	  Makefile or in the user's environment.  However, it is strongly
 	  discouraged for individual ports to set this variable explicitly
-	  in the Makefiles.  (If your port is an X port but doesn't use
+	  in the Makefiles.  (If your port is an X port but does not use
 	  imake, set <tt>USE_X11=yes</tt>; this is quite different from
 	  setting <tt>PREFIX=/usr/X11R6</tt>.)
 
@@ -933,14 +933,14 @@ lib/libtcl.so.7.3
 </verb></tscreen>
 
 	<p>Note: the `-m' option is new since 2.0.5 and
-	  2.1.0-950726-SNAP, so don't be alarmed if it doesn't work on 
+	  2.1.0-950726-SNAP, so do not be alarmed if it does not work on 
 	  your machine.
 
 	<p>Never, ever, <em>ever</em> add a line that says
 	  `<tt>ldconfig</tt>' without any arguments to your Makefile
 	  or pkg/PLIST.  This will reset the shared library cache to
 	  the contents of <tt>/usr/lib</tt> only, and will royally
-	  screw up the user's machine ("Help, xinit doesn't run
+	  screw up the user's machine ("Help, xinit does not run
 	  anymore after I install this port!").  Anybody who does this
 	  will be shot and cut into 65,536 pieces by a rusty knife and
 	  have his liver chopped out by a bunch of crows and will
@@ -952,7 +952,7 @@ lib/libtcl.so.7.3
 	<p>Do look at existing examples and the <tt>bsd.port.mk</tt>
 	  file before asking us questions!  <tt>;)</tt>
 
-	<p>Do ask us questions if you have any trouble!  Don't just
+	<p>Do ask us questions if you have any trouble!  Do not just
 	  beat your head against a wall! <tt>:)</tt>
 
     <sect2>
@@ -976,9 +976,9 @@ lib/libtcl.so.7.3
   person who wrote this Makefile]
  # Whom:			Satoshi Asami <asami@FreeBSD.ORG>
  #
- # $Id: porting.sgml,v 1.18 1996/04/10 06:32:42 asami Exp $
- [ ^^^^ don't worry about this...it will be automatically filled in by CVS when 
-  it is committed to our repository]
+ # $Id: porting.sgml,v 1.19 1996/05/09 23:04:48 mpp Exp $
+ [ ^^^^ do not worry about this...it will be automatically filled in by CVS 
+  when it is committed to our repository]
  #
  
  [section to describe the package itself and main ftp site - DISTNAME
@@ -987,7 +987,7 @@ lib/libtcl.so.7.3
  DISTNAME=	xdvi
  PKGNAME=	xdvi-pl18
  CATEGORIES+=	printing
- [don't forget the trailing slash ("/")!]
+ [do not forget the trailing slash ("/")!]
  MASTER_SITES=	ftp://crl.dec.com/pub/X11/contrib/applications/
  [set this if the source is not in the standard ".tar.gz" form]
  EXTRACT_SUFX=	.tar.Z
@@ -999,7 +999,7 @@ lib/libtcl.so.7.3
  [maintainer; *mandatory*!  This is the person (preferably with commit
   privileges) who a user can contact for questions and bug reports - this
   person should be the porter or someone who can forward questions to the
-  original porter reasonably promptly.  If you really don't want to have your
+  original porter reasonably promptly.  If you really do not want to have your
   address here, set it to "ports@FreeBSD.ORG".]
  MAINTAINER=	asami@FreeBSD.ORG
  
@@ -1007,8 +1007,8 @@ lib/libtcl.so.7.3
  RUN_DEPENDS=	gs:${PORTSDIR}/print/ghostscript
  LIB_DEPENDS=	Xpm\\.4\\.:${PORTSDIR}/graphics/xpm
  
- [this section is for other standard bsd.port.mk variables that don't belong to
-  any of the above]
+ [this section is for other standard bsd.port.mk variables that do not belong 
+  to any of the above]
  [If it extracts to a directory other than ${DISTNAME}...]
  WRKSRC=		${WRKDIR}/xdvi-new
  [If it asks questions during configure, build, install...]
@@ -1094,12 +1094,12 @@ xvgr-2.10pl1	xvgr-2.10.1	`pl' allowed only when no maj/minor numbers
 	version.
 
     <sect2>
-      <heading>That's It, Folks!</heading>
+      <heading>That is It, Folks!</heading>
 
       <p>Boy, this sure was a long tutorial, wasn't it?  Thanks for
 	following us to here, really.
 
-      <p>Well, now that you know how to do a port, let's go at it and
+      <p>Well, now that you know how to do a port, let us go at it and
 	convert everything in the world into ports!  That is the
 	easiest way to start contributing to the FreeBSD Project! 
 	<tt>:)</tt>
diff --git a/share/doc/handbook/ports.sgml b/share/doc/handbook/ports.sgml
index a8a574f30eb3..584970ff713e 100644
--- a/share/doc/handbook/ports.sgml
+++ b/share/doc/handbook/ports.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: ports.sgml,v 1.8 1995/12/04 17:58:45 jfieber Exp $ -->
+<!-- $Id: ports.sgml,v 1.9 1996/05/09 23:04:49 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>The Ports collection<label id="ports"></heading>
@@ -41,8 +41,8 @@ up less than twenty megabytes.
 on your system (usually /usr/ports/distfiles, though this value can be
 customized) for the associated set of original distribution files that
 have been ``ported''.  Those not found locally are searched for
-wherever they're generally provided on the Internet.  If you have a
-CDROM distribution of FreeBSD then you've already got them available
+wherever they are generally provided on the Internet.  If you have a
+CDROM distribution of FreeBSD then you already have them available
 on your CD for ease of use.  See <ref id="ports:cd"
 name="Compiling ports from CD"> if you have such a CDROM
 distribution, otherwise skip to <ref id="ports:inet" 
@@ -58,11 +58,11 @@ from <tt>/usr/ports</tt> to that directory.  Then invoke the <tt>lndir(1)</tt> c
 the full pathname of the ``ports'' directory on the CDROM as an
 argument (this might be, for example, something like: <tt>lndir
 /cdrom/ports</tt>).  Then you can build ports directly off the CDROM by
-building them in the link tree you've created.
+building them in the link tree you have created.
 
-Note that there are some ports for which we can't provide the original
+Note that there are some ports for which we cannot provide the original
 source in the CDROM due to licensing limitations.  In that case,
-you'll need to look at the next section (<ref id="ports:inet"
+you will need to look at the next section (<ref id="ports:inet"
 name="Compiling ports using an Internet connection">).
 
 <sect1><heading>Compiling ports using an Internet connection<label id="ports:inet"></heading>
@@ -71,8 +71,8 @@ name="Compiling ports using an Internet connection">).
 your ports collection source tree up to date, updating the central
 ``distfiles'' version for you the next time you compile the port.
 
-    Of course, this assumes you have a permanent network link or don't
-mind heavy usage of your telephone.  If you don't want heavy network
+    Of course, this assumes you have a permanent network link or do not
+mind heavy usage of your telephone.  If you do not want heavy network
 usage when you compile your ports tree, you can pre-fetch the
 necessary tarballs beforehand and put them into /usr/ports/distfiles
 by hand.  A good way to see what files a port is going to need is to
@@ -86,15 +86,15 @@ line), or some FreeBSD mirror site also carrying a set of distfiles,
 as does the master FTP site on ftp.FreeBSD.org (aka ftp.cdrom.com) in
 the directory <tt>/pub/FreeBSD/distfiles</tt>.  Note that the files in
 that directory are not guaranteed to be kept up to date - this is a
-volunteer project!  We can't make any guarantees about the mirror
-sites either - they are obviously under independent control and don't
+volunteer project!  We canno make any guarantees about the mirror
+sites either - they are obviously under independent control and do not
 even have to mirror the distfiles directory.
 
     If you have a non-permanent link, you can fetch all the distfiles by
 going to the top of the tree and typing ``make fetch''.
 
 
-<sect1><heading>It doesn't work?!</heading>
+<sect1><heading>It does not work?!</heading>
 
 <p>Oh. You can do one of four (4) things :
 <enum>
@@ -105,17 +105,17 @@ going to the top of the tree and typing ``make fetch''.
 <item> Gripe. This is done by e-mail *ONLY*! The people at Walnut Creek are
    in no way responsible for the functionality (or lack thereof) of the
    FreeBSD system as a whole, and especially the ports system, which
-   is mainly contributed by 3rd parties. (If you don't believe me, check
+   is mainly contributed by 3rd parties. (If you do not believe me, check
    the catalogue, especially the line saying "We cannot offer tech-support
    on this product")
 
-   The e-mail address is Ports@FreeBSD.org.  Please include details of
+   The e-mail address is the &a.ports;.  Please include details of
    the port, where you got both the port source &amp; distfile(s) from, and
    what the error was.
 
-   Note: At time of writing, lang/Sather doesn't seem to work on Pentium
+   Note: At time of writing, lang/Sather does not seem to work on Pentium
    machines due to the Intel Curse (aka the Floating Point Division Bug).
-   Please don't tell us about this - gripe to Intel instead - it's their
+   Please do not tell us about this - gripe to Intel instead - it is their
    bug!
 
 <item> Forget it. This is the easiest for most - very few of the programs in
@@ -132,12 +132,12 @@ going to the top of the tree and typing ``make fetch''.
    install them to your system.
 </enum>
 
-<sect1><heading>I've ported a program and I want to make a port out of it. What now?</heading>
+<sect1><heading>I have ported a program and I want to make a port out of it. What now?</heading>
 
 <p>   See the <ref id="porting:starting" name="guidelines"> that
       contain details of the procedure and structure involved.
 
-<sect1><heading>I've got a good port, what now?</heading>
+<sect1><heading>I have got a good port, what now?</heading>
 
 <p>Upload the fixed version to <tt>ftp://freefall.cdrom.com/pub/incoming</tt> or
 <tt>ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming</tt> and send e-mail to
@@ -146,7 +146,7 @@ all-volunteer `ports committee' will (hopefully) look it over and
 commit it to the ports collection if they like the looks of it.
 
 
-<sect1><heading>I want to leave the compile going overnight, but some ports don't like this.</heading>
+<sect1><heading>I want to leave the compile going overnight, but some ports do not like this.</heading>
 
 <p>   There is a way around this. Before starting the compilation, type:
 <verb>
@@ -176,8 +176,8 @@ minute.  The most up-to-date copy can be found in:
   <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/share/mk">
 
     If you find that you still need to go in there and alter things,
-by all means do so, and then send the diffs to ports@FreeBSD.org if
-you'd like them to be a part of the default distribution.  Please also
+by all means do so, and then send the diffs to the &a.ports if
+you would like them to be a part of the default distribution.  Please also
 remember that any changes must respect backwards-compatibility with
 any and all older Makefiles, unless you want a real nightmare of
 /usr/ports munging ahead of you!  Large scale changes will generally
@@ -187,7 +187,7 @@ alteration. Sorry!
 
 <sect1><heading>This FAQ is weak.  What can I do?</heading>
 
-<p>    Send changes to ports@FreeBSD.org.  Changes are most welcome!
+<p>    Send changes to the &a.ports;.  Changes are most welcome!
 This FAQ is also very green and should be considered no more than
 a `good start' for now.  Authors?  You can come out of hiding any
 time now! :-)
@@ -202,7 +202,7 @@ and type:
 </verb>
 This will print a summary of all ports in the tree.
 
-<sect1><heading>I've heard of a new checksum system. What is this for?</heading>
+<sect1><heading>I have heard of a new checksum system. What is this for?</heading>
 
 <p>    For various reasons, when using FTP over the Internet to obtain the
 source code, you may not always end up with the same copy of the code
@@ -223,7 +223,7 @@ checksum routine. The same technique can be applied to a single port.
 for that port. Not all ports currently have checksums, but this should be
 cured soon.
 
-    Some older versions of the system don't recognize the ``checksum''
+    Some older versions of the system do not recognize the ``checksum''
 target. In that case, try the command
 <verb>
 	make check-md5
diff --git a/share/doc/handbook/ppp.sgml b/share/doc/handbook/ppp.sgml
index 157f03d47895..0383cc739958 100644
--- a/share/doc/handbook/ppp.sgml
+++ b/share/doc/handbook/ppp.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: ppp.sgml,v 1.5 1995/09/27 00:46:27 jmz Exp $ -->
+<!-- $Id: ppp.sgml,v 1.6 1995/12/04 17:58:46 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Setting up kernel PPP<label id="ppp"></heading>
@@ -246,7 +246,7 @@ exit
 
 This <tt>/etc/ppp/kermit.dial</tt> script is used for dialing and authorizing
 on remote host. You will need to customize it for your needs.
-Put your login and password in this script , also you'll need
+Put your login and password in this script , also you will need
 to change input statement depending on responses from your modem
 and remote host.
 <verb>
diff --git a/share/doc/handbook/printing.sgml b/share/doc/handbook/printing.sgml
index 1aa5955e1c28..75e67741ce79 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.4 1996/01/31 14:26:14 mpp Exp $
+     $Id: printing.sgml,v 1.5 1996/01/31 19:03:00 mpp Exp $
 
      The FreeBSD Documentation Project
 
@@ -24,13 +24,13 @@
 
     <p><em>Contributed by &a.kelly;<newline>30 September 1995</em>
 
-        In order to use printers with FreeBSD, you'll need to set
+        In order to use printers with FreeBSD, you will need to set
 	them up to work with the Berkeley line printer spooling
-	system, also known as the LPD spooling system.  It's the
+	system, also known as the LPD spooling system.  It iss the
 	standard printer control system in FreeBSD.  This section
 	introduces the LPD spooling system, often simply called LPD.
 
-	If you're already familiar with LPD or another printer
+	If you are already familiar with LPD or another printer
 	spooling system, you may wish to skip to section <ref
 	id="printing:intro:setup" name="Setting up the spooling
 	system">.
@@ -38,7 +38,7 @@
       <sect><heading>What the Spooler Does<label
 	    id="printing:intro:spooler"></heading>
 
-	<p> LPD controls everything about a host's printers.  It's
+	<p> LPD controls everything about a host's printers.  It is
 	  responsible for a number of things:
 
 	  <itemize>
@@ -54,7 +54,7 @@
 
 	    <item>It can print <em/header pages/ (also known as
 	      <em/banner/ or <em/burst/ pages) so users can easily
-	      find jobs they've printed in a stack of printouts.
+	      find jobs they have printed in a stack of printouts.
 
 	    <item>It takes care of communications parameters for
 	      printers connected on serial ports.
@@ -77,7 +77,7 @@
       <sect><heading>Why You Should Use the Spooler<label
 	    id="printing:intro:why"></heading> 
 
-	<p> If you're the sole user of your system, you may be
+	<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
@@ -90,12 +90,12 @@
 	    <item>LPD can conveniently run a job to be printed
 	      through filters to add date/time headers or convert a
 	      special file format (such as a TeX DVI file) into a
-	      format the printer will understand.   You won't have to do
+	      format the printer will understand.   You will not have to do
 	      these steps manually.
 
 	    <item>Many free and commercial programs that provide a
 	      print feature usually expect to talk to the spooler on
-	      your system.  By setting up the spooling system, you'll
+	      your system.  By setting up the spooling system, you will
 	      more easily support other software you may later add or
 	      already have.
 	  </itemize>
@@ -103,7 +103,7 @@
       <sect><heading>Setting Up the Spooling System<label
 	    id="printing:intro:setup"></heading>
 
-	<p> To use printers with the LPD spooling system, you'll need
+	<p> To use printers with the LPD spooling system, you will need
 	  to set up both your printer hardware and the LPD software.
 	  This document describes two levels of setup:
 
@@ -137,12 +137,12 @@
 	    file <tt>/etc/printcap</tt>.
 	</itemize>
 
-        If you're setting up a printer that uses a network protocol
+        If you are setting up a printer that uses a network protocol
 	to accept data to print instead of a serial or parallel interface,
 	see <ref id="printing:advanced:network:net-if" name="Printers
 	  With Networked Data Stream Interaces">.
 
-	Although this section is called ``Simple Printer Setup,'' it's
+	Although this section is called ``Simple Printer Setup,'' it is
 	actually fairly complex.  Getting the printer to work with
 	your computer and the LPD spooler is the hardest part.  The
 	advanced options like header pages and accounting are fairly
@@ -155,7 +155,7 @@
 	  cables, and also the kernel configuration you may need to
 	  enable FreeBSD to speak to the printer.
 
-	  If you've already connected your printer and have
+	  If you have already connected your printer and have
 	  successfully printed with it under another operating system,
 	  you can probably skip to section <ref id="printing:software"
 	  name="Software Setup">.
@@ -193,14 +193,14 @@
 	    one-way communication (computer to printer) while serial
 	    gives you two-way.  Many newer parallel ports can also
 	    receive data from the printer, but only few printers need
-	    to send data back to the computer.  And FreeBSD doesn't
+	    to send data back to the computer.  And FreeBSD does not
 	    support two-way parallel communication yet.
 
 	    Usually, the only time you need two-way communication with
 	    the printer is if the printer speaks PostScript.
 	    PostScript printers can be very verbose.  In fact,
 	    PostScript jobs are actually programs sent to the printer;
-	    they needn't produce paper at all and may return results
+	    they need not produce paper at all and may return results
 	    directly to the computer.  PostScript also uses
 	    two-way communication to tell the computer about problems,
 	    such as errors in the PostScript program or paper jams.
@@ -219,11 +219,11 @@
 		port.  FreeBSD does not yet support two-way
 		communication over a parallel port.
 
-	      <item>If you don't need two-way communication and can
+	      <item>If you do not need two-way communication and can
 		pick parallel or serial, prefer the parallel
 		interface.  It keeps a serial port free for other
 		peripherals---such as a terminal or a modem---and is
-		faster most of the time.  It's also easier to
+		faster most of the time.  It is also easier to
 		configure.
 
 	      <item>Finally, use whatever works.	
@@ -248,7 +248,7 @@
 	    computer.  The instructions that came with the printer,
 	    the computer, or both should give you complete guidance.
 
-	    If you're unsure what the ``proper serial cable'' is, you
+	    If you are unsure what the ``proper serial cable'' is, you
 	    may wish to try one of the following alternatives:
 	    <itemize>
 	      <item>A <em/modem/ cable connects each pin of the
@@ -285,15 +285,15 @@
 	<p> This section describes the software setup necessary to
 	  print with the LPD spooling system in FreeBSD.
 
-	  Here's an outline of the steps involved:
+	  Here is an outline of the steps involved:
 	  <enum>
 	    <item>Configure your kernel, if necessary, for the port
-	      you're using for the printer; section <ref
+	      you are using for the printer; section <ref
 	      id="printing:kernel" name="Kernel Configuration"> tells
 	      you what you need to do.
 
 	    <item>Set the communications mode for the parallel port,
-	      if you're using a parallel port; section <ref
+	      if you are using a parallel port; section <ref
 	      id="printing:parallel-port-mode" name = "Setting the
 	      Communication Mode for the Parallel Port"> gives
 	      details.
@@ -316,10 +316,10 @@
 	    specific set of devices.  The serial or parallel interface
 	    for your printer is a part of that set.  Therefore, it
 	    might be necessary to add support for an additional serial
-	    or parallel port if your kernel isn't already configured
+	    or parallel port if your kernel is not already configured
 	    for one.
 
-	    To find out if the kernel you're currently using supports a serial
+	    To find out if the kernel you are currently using supports a serial
 	    interface, type
 <tscreen>
 <tt>dmesg &verbar; grep sio</tt><it/N/
@@ -346,7 +346,7 @@ lpt0 at 0x378-0x37f on isa
 
 	    You might have to reconfigure your kernel in order for the
 	    operating system to recognize and use the parallel or
-	    serial port you're using for the printer.
+	    serial port you are using for the printer.
 
 	    To add support for a serial port, see the section on
             kernel configuration.  To add support for a parallel port,
@@ -356,9 +356,9 @@ lpt0 at 0x378-0x37f on isa
 	      <label id="printing:dev-ports"></heading>
 
 	    <p> Even though the kernel may support communication along
-	      a serial or parallel port, you'll still need a software
+	      a serial or parallel port, you will still need a software
 	      interface through which programs running on the system
-	      can send and receive data.  That's what entries in the
+	      can send and receive data.  That is what entries in the
 	      <tt>/dev</tt> directory are for.
 
 	      <bf>To add a <tt>/dev</tt> entry for a port:</bf>
@@ -391,7 +391,7 @@ cd /dev
 	  <sect3><heading>Setting the Communication Mode for the Parallel Port
 	      <label id="printing:parallel-port-mode"></heading>
 
-	    <p> When you're using the parallel interface, you can
+	    <p> When you are using the parallel interface, you can
 	      choose whether FreeBSD should use interrupt-driven or
 	      polled communication with the printer.
 
@@ -402,7 +402,7 @@ cd /dev
 		  the printer is ready for data.
 
 		<item>The <em/polled/ method directs the operating
-		  system to repeatedly ask the printer if it's ready
+		  system to repeatedly ask the printer if it is ready
 		  for more data.  When it responds ready, the kernel
 		  sends more data.
 	      </itemize>
@@ -419,7 +419,7 @@ cd /dev
 		kernel:</bf>
 	      <enum>
 		<item>Edit your kernel configuration file.  Look for
-		  or add an <tt/lpt0/ entry.  If you're setting up the
+		  or add an <tt/lpt0/ entry.  If you are setting up the
 		  second parallel port, use <tt/lpt1/ instead.  Use
 		  <tt/lpt2/ for the third port, and so on.
 		  <itemize>
@@ -431,7 +431,7 @@ cd /dev
 		      where <it/N/ is the IRQ number for your
 		      computer's parallel port.
 
-		    <item>If you want polled mode, don't add the
+		    <item>If you want polled mode, do not add the
 		      <tt/irq/ specifier:
 <tscreen>
 <tt>device lpt0 at isa? port? tty vector lptintr</tt>		
@@ -469,17 +469,17 @@ cd /dev
 
 	    <p> Before proceeding to configure the spooling system,
 	      you should make sure the operating system can
-	      successfully send data to your printer.  It's a lot
+	      successfully send data to your printer.  It is a lot
 	      easier to debug printer communication and the spooling
 	      system separately.
 
-	      To test the printer, we'll send some text to it.  For
+	      To test the printer, we will send some text to it.  For
 	      printers that can immediately print characters sent to
 	      them, the program <tt/lptest/ is perfect: it generates
 	      all 96 printable ASCII characters in 96 lines.
 
 	      For a PostScript (or other language-based) printer,
-	      we'll need a more sophisticated test.  A small
+	      we will need a more sophisticated test.  A small
 	      PostScript program, such as the following, will suffice:
 <code>
 %!PS
@@ -490,11 +490,11 @@ cd /dev
 showpage
 </code>
 	      <em/Note:/ When this document refers to a printer
-	      language, I'm assuming a language like PostScript, and
+	      language, I am assuming a language like PostScript, and
 	      not Hewlett Packard's PCL.  Although PCL has great
 	      functionality, you can intermingle plain text with its
 	      escape sequences.  PostScript cannot directly print
-	      plain text, and that's the kind of printer language for
+	      plain text, and that is the kind of printer language for
 	      which we must make special accommodations.
 
 	    <sect4><heading>Checking a Parallel Printer<label
@@ -523,8 +523,8 @@ showpage
 <tt>cat > /dev/lpt<it/N/</tt>
 </tscreen>
 			Then, line by line, type the program
-			<em/carefully/ as you can't edit a line once
-			you've pressed RETURN or ENTER. When you've
+			<em/carefully/ as you cannot edit a line once
+			you have pressed RETURN or ENTER. When you have
 			finished entering the program, press
 			CONTROL+D, or whatever your end of file key
 			is.
@@ -540,7 +540,7 @@ showpage
 		    </itemize>
 		</enum>
 
-		You should see something print.  Don't worry if the
+		You should see something print.  Do not worry if the
 		text doesn't look right; we'll fix such things later.
 
 	    <sect4><heading>Checking a Serial Printer<label
@@ -565,7 +565,7 @@ showpage
 		    required by the printer (either <tt/even/,
 		    <tt/odd/, <tt/none/, or <tt/zero/).
 		    <p>
-		      Here's a sample entry for a printer connected
+		      Here is a sample entry for a printer connected
 		      via a serial line to the third serial port at
 		      19200 bps with no parity:
 <code>
@@ -576,7 +576,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none
 <tscreen><verb>
 tip printer
 </verb></tscreen>
-		    If this step doesn't work, edit the file
+		    If this step does not work, edit the file
 		    <tt>/etc/remote</tt> again and try using
 		    <tt>/dev/cuaa<it/N/</tt> instead of
 		    <tt>/dev/ttyd<it/N/</tt>.
@@ -612,16 +612,16 @@ tip printer
 		    </itemize>
 		</enum>
 
-		You should see something print.  Don't worry if the
-		text doesn't look right; we'll fix that later.
+		You should see something print.  Do not worry if the
+		text does not look right; we will fix that later.
 
 	<sect2><heading>Enabling the Spooler: The <tt>/etc/printcap</tt> File
 	    <label id="printing:printcap"></heading>
 
 	  <p> At this point, your printer should be hooked up, your
 	    kernel configured to communicate with it (if necessary),
-	    and you've been able to send some simple data to the
-	    printer.  Now, we're ready to configure LPD to control
+	    and you have been able to send some simple data to the
+	    printer.  Now, we are ready to configure LPD to control
 	    access to your printer.
 
 	    You configure LPD by editing the file
@@ -673,17 +673,17 @@ tip printer
 	    </enum>
 
 	    <em/Note:/ Language-based printers, such as PostScript
-	    printers, can't directly print plain text.  The simple
+	    printers, cannot directly print plain text.  The simple
 	    setup outlined above and described in the following
-	    sections assumes that if you're installing such a printer
-	    you'll print only files that the printer can understand.
+	    sections assumes that if you are installing such a printer
+	    you will print only files that the printer can understand.
 
 	    Users often expect that they can print plain text to any
 	    of the printers installed on your system.  Programs that
 	    interface to LPD to do their printing usually make the
-	    same assumption.  If you're installing such a printer and
+	    same assumption.  If you are installing such a printer and
 	    want to be able to print jobs in the printer language
-	    <em/and/ print plain text jobs, you're strongly urged to
+	    <em/and/ print plain text jobs, you are strongly urged to
 	    add an additional step to the simple setup outlined above:
 	    install an automatic plain-text--to--PostScript (or other
 	    printer language) conversion program.  Section <ref
@@ -695,23 +695,23 @@ tip printer
 		id="printing:naming"></heading>
 
 	    <p> The first (easy) step is to pick a name for your
-	      printer.  It really doesn't matter whether you choose
+	      printer.  It really does not matter whether you choose
 	      functional or whimsical names since you can also provide
 	      a number aliases for the printer.
 
 	      At least one of the printers specified in the
 	      <tt>/etc/printcap</tt> should have the alias
 	      <tt/lp/. This is the default printer's name.  If users
-	      don't have the PRINTER environment variable nor
+	      do not have the PRINTER environment variable nor
 	      specify a printer name on the command line of any of the
 	      LPD commands, then <tt/lp/ will be the default printer
 	      they get to use.
 
-	      Also, it's common practice to make the last alias for a
+	      Also, it is common practice to make the last alias for a
 	      printer be a full description of the printer, including
 	      make and model.
 
-	      Once you've picked a name and some common aliases, put
+	      Once you have picked a name and some common aliases, put
 	      them in the <tt>/etc/printcap</tt> file.  The name of
 	      the printer should start in the leftmost column.
 	      Separate each alias with a vertical bar and put a colon
@@ -732,7 +732,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:
 	      In this example, the first printer is named <tt/rattan/
 	      and has as aliases <tt/line/, <tt/diablo/, <tt/lp/, and
 	      <tt/Diablo 630 Line Printer/.  Since it has the alias
-	      <tt/lp/, it's also the default printer.  The second is
+	      <tt/lp/, it is also the default printer.  The second is
 	      named <tt/bamboo/, and has as aliases <tt/ps/, <tt/PS/,
 	      <tt/S/, <tt/panasonic/, and <tt/Panasonic KX-P4455
 	      PostScript v51.4/.
@@ -745,12 +745,12 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:
 	      the user name who requested the job, the host from which
 	      the job came, and the name of the job, in nice large
 	      letters.  Unfortunately, all this extra text gets in the
-	      way of debugging the simple printer setup, so we'll
+	      way of debugging the simple printer setup, so we will
 	      suppress header pages.
 
 	      To suppress header pages, add the <tt/sh/ capability to
 	      the entry for the printer in
-	      <tt>/etc/printcap</tt>. Here's the example
+	      <tt>/etc/printcap</tt>. Here is the example
 	      <tt>/etc/printcap</tt> with <tt/sh/ added:
 <code>
 #
@@ -772,17 +772,17 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 
 	    <p> The next step in the simple spooler setup is to make a
 	      <em/spooling directory/, a directory where print jobs
-	      reside until they're printed, and where a number of
+	      reside until they are printed, and where a number of
 	      other spooler support files live.
 
 	      Because of the variable nature of spooling directories,
-	      it's customary to put these directories under
-	      <tt>/var/spool</tt>.  It's not necessary to backup the
+	      it is customary to put these directories under
+	      <tt>/var/spool</tt>.  It is not necessary to backup the
 	      contents of spooling directories, either.  Recreating
 	      them is as simple as running <tt/mkdir/.
 
-	      It's also customary to make the directory with a name
-	      that's identical to the name of the printer, as shown
+	      It is also customary to make the directory with a name
+	      that is identical to the name of the printer, as shown
 	      below:
 <tscreen>
 <tt>mkdir /var/spool/<it>printer-name</it></tt>
@@ -790,7 +790,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      However, if you have a lot of printers on your network,
 	      you might want to put the spooling directories under a
 	      single directory that you reserve just for printing with
-	      LPD.  We'll do this for our two example printers
+	      LPD.  We will do this for our two example printers
 	      <tt/rattan/ and <tt/bamboo/:
 <tscreen><verb>
 mkdir /var/spool/lpd
@@ -798,12 +798,12 @@ mkdir /var/spool/lpd/rattan
 mkdir /var/spool/lpd/bamboo
 </verb></tscreen>
 
-	      <em/Note:/ If you're concerned about the privacy of jobs
+	      <em/Note:/ If you are concerned about the privacy of jobs
 	      that users print, you might want to protect the spooling
-	      directory so it's not publicly accessible.  Spooling
+	      directory so it is not publicly accessible.  Spooling
 	      directories should be owned and be readable, writable,
 	      and searchable by user daemon and group daemon, and no
-	      one else.  We'll do this for our example printers:
+	      one else.  We will do this for our example printers:
 
 <tscreen><verb>
 chown daemon.daemon /var/spool/lpd/rattan
@@ -831,7 +831,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      should be indented with a tab and each line escaped with
 	      a backslash.
 
-	      If you don't specify a spooling directory with <tt/sd/,
+	      If you do not specify a spooling directory with <tt/sd/,
 	      the spooling system will use <tt>/var/spool/lpd</tt> as
 	      a default.
 
@@ -851,7 +851,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      <tt>/etc/printcap</tt> file using the <tt/lp/
 	      capability.
 
-	      In our running example, let's assume that <tt/rattan/ is
+	      In our running example, let us assume that <tt/rattan/ is
 	      on the first parallel port, and <tt/bamboo/ is on a
 	      sixth serial port; here are the additions to
 	      <tt>/etc/printcap</tt>:
@@ -868,12 +868,12 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:lp=/dev/ttyd5:
 </code>
 
-	      If you don't specify the <tt/lp/ capability for a
+	      If you do not specify the <tt/lp/ capability for a
 	      printer in your <tt>/etc/printcap</tt> file, LPD uses
 	      <tt>/dev/lp</tt> as a default.  <tt>/dev/lp</tt>
-	      currently doesn't exist in FreeBSD.
+	      currently does not exist in FreeBSD.
 
-	      If the printer you're installing is connected to a
+	      If the printer you are installing is connected to a
 	      parallel port, skip to the section <ref name="Installing
 	      the Text Filter" id="printing:textfilter">.  Otherwise,
 	      be sure to follow the instructions in the next section.
@@ -888,7 +888,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      <itemize>
 		<item>It lets you try different communication
 		  parameters by simply editing the
-		  <tt>/etc/printcap</tt> file; you don't have to
+		  <tt>/etc/printcap</tt> file; you do not have to
 		  recompile the filter program.
 
 		<item>It enables the spooling system to use the same
@@ -937,10 +937,10 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      the resultant setting.  It does the same for the local
 	      mode bits as well.
 
-	      Let's add to our example printer on the sixth serial
-	      port.  We'll set the bps rate to 38400. For the flag
-	      bits, we'll set the TANDEM, ANYP, LITOUT, FLUSHO, and
-	      PASS8 flags.  For the local mode bits, we'll set the
+	      Let us add to our example printer on the sixth serial
+	      port.  We will set the bps rate to 38400. For the flag
+	      bits, we will set the TANDEM, ANYP, LITOUT, FLUSHO, and
+	      PASS8 flags.  For the local mode bits, we will set the
 	      LITOUT and PASS8 flags:
 <tscreen><verb>
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
@@ -952,7 +952,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	  <sect3><heading>Installing the Text Filter<label
 		id="printing:textfilter"></heading>
 
-	    <p> We're now ready to tell LPD what text filter to use to
+	    <p> We are now ready to tell LPD what text filter to use to
 	      send jobs to the printer.  A <em/text filter/, also
 	      known as an <em/input filter/, is a program that LPD
 	      runs when it has a job to print.  When LPD runs the text
@@ -976,7 +976,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      <tt/lpf/ is described in detail in section <ref
 	      id="printing:advanced:lpf" name="lpf: a Text Filter">.
 
-	      First, let's make the shell script
+	      First, let uss make the shell script
 	      <tt>/usr/local/libexec/if-simple</tt> be a simple text
 	      filter. Put the following text into that file with your
 	      favorite text editor:
@@ -997,7 +997,7 @@ chmod 555 /usr/local/libexec/if-simple
 </verb></tscreen>
 
 	      And then tell LPD to use it by specifying it with the
-	      <tt/if/ capability in <tt>/etc/printcap</tt>.  We'll add
+	      <tt/if/ capability in <tt>/etc/printcap</tt>.  We will add
 	      it to the two printers we have so far in the example
 	      <tt>/etc/printcap</tt>:
 <code>
@@ -1017,9 +1017,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 
 	  <sect3><heading>Trying It Out<label id="printing:trying"></heading>
 
-	    <p> You've reached the end of the simple LPD setup.
+	    <p> You have reached the end of the simple LPD setup.
 	      Unfortunately, congratulations are not quite yet in
-	      order, since we've still got to test the setup and
+	      order, since we still have to test the setup and
 	      correct any problems.  To test the setup, try printing
 	      something.  To print with the LPD system, you use the
 	      command <tt/lpr/, which submits a job for printing.
@@ -1038,14 +1038,14 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      where <it/printer-name/ is a the name of a printer (or
 	      an alias) specified in <tt>/etc/printcap</tt>.  To test
 	      the default printer, type <tt/lpr/ without any <tt/-P/
-	      argument.  Again, if you're testing a printer that
+	      argument.  Again, if you are testing a printer that
 	      expects PostScript, send a PostScript program in that
 	      language instead of using <tt/lptest/.  You can do so by
 	      putting the program in a file and typing <tt/lpr
 	      <it/file//.
 
 	      For a PostScript printer, you should get the results
-	      of the program.  If you're using <tt/lptest/, then your
+	      of the program.  If you are using <tt/lptest/, then your
 	      results should look like the following:
 
 <tscreen><verb>
@@ -1062,7 +1062,7 @@ $%&ero;'()*+,-./01234567
 	      <tt/lptest 80 60/ will produce 60 lines of 80 characters
 	      each.
 
-	      If the printer didn't work, see the next section, <ref
+	      If the printer did not work, see the next section, <ref
 		id="printing:troubleshooting" name="Troubleshooting">.
 
 	  <sect3><heading>Troubleshooting<label
@@ -1072,7 +1072,7 @@ $%&ero;'()*+,-./01234567
 	      might have gotten one of the following results instead of
 	      the correct printout:
 	      <descrip>
-		<tag/It worked, after awhile; or, it didn't eject a full sheet./
+		<tag/It worked, after awhile; or, it did not eject a full sheet./
 
 		  The printer printed the above, but it sat for awhile
 		  and did nothing.  In fact, you might have needed to
@@ -1086,9 +1086,9 @@ $%&ero;'()*+,-./01234567
 		  FEED character (or whatever is necessary) to the
 		  printer.  This is usually sufficient to have the
 		  printer immediately print any text remaining in its
-		  internal buffer.  It's also useful to make sure each
+		  internal buffer.  It is also useful to make sure each
 		  print job ends on a full sheet, so the next job
-		  doesn't start somewhere on the middle of the last
+		  does not start somewhere on the middle of the last
 		  page of the previous job.
 
 		  The following replacement for the shell script
@@ -1115,7 +1115,7 @@ exit 2
                         "#$%&ero;'()*+,-./012345
                                                 #$%&ero;'()*+,-./0123456
 </verb></tscreen>
-		  You've become another victim of the <em/staircase
+		  You have become another victim of the <em/staircase
 		  effect/, caused by conflicting interpretations of
 		  what characters should indicate a new-line.
 		  UNIX-style operating systems use a single character:
@@ -1129,12 +1129,12 @@ exit 2
 		  line feed character.  The printer, upon seeing a
 		  line feed character, advanced the paper one line,
 		  but maintained the same horizontal position on the
-		  page for the next character to print.  That's what
+		  page for the next character to print.  That is what
 		  the carriage return is for: to move the location of
 		  the next character to print to the left edge of the
 		  paper.
 
-		  Here's what FreeBSD wants your printer to do:
+		  Here is what FreeBSD wants your printer to do:
 <tscreen><verb>
 Printer received CR		Printer prints CR
 Printer received LF		Printer prints CR + LF
@@ -1170,7 +1170,7 @@ Printer received LF		Printer prints CR + LF
 		      text filter to send the code first, then send
 		      the print job.
 
-		      <p> Here's an example text filter for printers
+		      <p> Here is an example text filter for printers
 			that understand the Hewlett-Packard PCL escape
 			codes.  This filter makes the printer treat LF
 			characters as a LF and CR; then it sends the
@@ -1192,10 +1192,10 @@ printf "\033&ero;k2G" &ero;&ero; cat &ero;&ero; printf "\f" &ero;&ero; exit 0
 exit 2
 </code>
 
-			Here's an example <tt>/etc/printcap</tt> from
+			Here is an example <tt>/etc/printcap</tt> from
 			a host called orchid.  It has a single printer
 			attached to its first parallel port, a Hewlett
-			Packard LaserJet 3Si named <tt/teak/.  It's
+			Packard LaserJet 3Si named <tt/teak/.  It is
 			using the above script as its text filter:
 <code>
 #
@@ -1230,14 +1230,14 @@ Printer received LF		Printer prints CR + LF
 
 		<tag/The printer lost characters./
 
-		  While printing, the printer didn't print a few
+		  While printing, the printer did nott print a few
 		  characters in each line.  The problem might have
 		  gotten worse as the printer ran, losing more and
 		  more characters.
 
-		  The problem is that the printer can't keep up with
+		  The problem is that the printer cannot keep up with
 		  the speed at which the computer sends data over a
-		  serial line.  (This problem shouldn't occur with
+		  serial line.  (This problem should not occur with
 		  printers on parallel ports.)  There are two ways to
 		  overcome the problem:
 		  <itemize>
@@ -1251,7 +1251,7 @@ Printer received LF		Printer prints CR + LF
 		      printer to the computer is correctly wired for
 		      carrier flow control.
 
-		    <item>If the printer doesn't support any flow
+		    <item>If the printer does not support any flow
 		      control, use some combination of the NLDELAY,
 		      TBDELAY, CRDELAY, VTDELAY, and BSDELAY bits in
 		      the <tt/fs/ capability to add appropriate delays
@@ -1276,8 +1276,8 @@ Printer received LF		Printer prints CR + LF
 		  If nothing happened, the problem is probably within
 		  FreeBSD and not the hardware.  Add the log file
 		  (<tt/lf/) capability to the entry for the printer
-		  you're debugging in the <tt>/etc/printcap</tt> file.
-		  For example, here's the entry for <tt/rattan/, with
+		  you are debugging in the <tt>/etc/printcap</tt> file.
+		  For example, here is the entry for <tt/rattan/, with
 		  the <tt/lf/ capability:
 <tscreen><verb>
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
@@ -1291,13 +1291,13 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
 		  any error messages that might appear.  Based on the
 		  messages you see, try to correct the problem.
 
-		  If you don't specify a <tt/lf/ capability, LPD uses
+		  If you do not specify a <tt/lf/ capability, LPD uses
 		  <tt>/dev/console</tt> as a default.
 	      </descrip>
 
     <sect><heading>Using Printers<label id="printing:using"></heading>
 
-      <p> This section tells you how to use printers you've setup with
+      <p> This section tells you how to use printers you have setup with
 	FreeBSD.  Here's an overview of the user-level commands:
 	<descrip>
 	  <tag/<tt/lpr//
@@ -1311,7 +1311,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
 
 	</descrip>
 
-	There's also an administrative command, <tt/lpc/, described in
+	There is also an administrative command, <tt/lpc/, described in
 	the section <ref id="printing:lpc" name="Administrating the
 	LPD Spooler">, used to control printers and their queues.
 
@@ -1319,15 +1319,15 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
 	accept an option ``<tt/-P/ <it/printer-name/'' to specify on
 	which printer/queue to operate, as listed in the
 	<tt>/etc/printcap</tt> file.  This enables you to submit,
-	remove, and check on jobs for various printers.  If you don't
+	remove, and check on jobs for various printers.  If you do not
 	use the <tt/-P/ option, then these commands use the printer
 	specified in the PRINTER environment variable.  Finally, if
-	you don't have a PRINTER environment variable, these commands
+	you do not have a PRINTER environment variable, these commands
 	default to the printer named <tt/lp/.
 
 	Hereafter, the terminology <em/default printer/ means the
 	printer named in the PRINTER environment variable, or the
-	printer named <tt/lp/ when there's no PRINTER environment
+	printer named <tt/lp/ when there is no PRINTER environment
 	variable.
 
       <sect1><heading>Printing Jobs<label id="printing:lpr"></heading>
@@ -1378,7 +1378,7 @@ ls -l | lpr -P rattan
 <tscreen><verb>
 lpq -P bamboo
 </verb></tscreen>
-	  shows the queue for the printer named <tt/bamboo/.  Here's
+	  shows the queue for the printer named <tt/bamboo/.  Here is
 	  an example of the output of the <tt/lpq/ command:
 <tscreen><verb>
 bamboo is ready and printing
@@ -1391,16 +1391,16 @@ active kelly    9    /etc/host.conf, /etc/hosts.equiv   88 bytes
 	  first job, submitted by user kelly, got assigned <em/job
 	  number/ 9.  Every job for a printer gets a unique job
 	  number.  Most of the time you can ignore the job number, but
-	  you'll need it if you want to cancel the job; see section
+	  you will need it if you want to cancel the job; see section
 	  <ref id="printing:lprm" name="Removing Jobs"> for details.
 
 	  Job number nine consists of two files; multiple files given
 	  on the <tt/lpr/ command line are treated as part of a single
-	  job.  It's the currently active job (note the word
+	  job.  It is the currently active job (note the word
 	  <tt/active/ under the ``Rank'' column), which means the
 	  printer should be currently printing that job.  The second
 	  job consists of data passed as the standard input to the
-	  <tt/lpr/ command. The third job came from user mary; it's a
+	  <tt/lpr/ command. The third job came from user mary; it is a
 	  much larger job.  The pathname of the files she's trying to
 	  print is too long to fit, so the <tt/lpq/ command just shows
 	  three dots.
@@ -1410,7 +1410,7 @@ active kelly    9    /etc/host.conf, /etc/hosts.equiv   88 bytes
 	  least what LPD thinks the printer is doing).
 
 	  The <tt/lpq/ command also support a <tt/-l/ option to
-	  generate a detailed long listing. Here's an example of
+	  generate a detailed long listing. Here is an example of
 	  <tt/lpq -l/:
 <tscreen><verb>
 waiting for bamboo to become ready (offline ?)
@@ -1475,7 +1475,7 @@ lprm -P bamboo 10
 lprm -P rattan -
 </verb></tscreen>
 
-	  <em/Note:/ If you're working in a networked environment,
+	  <em/Note:/ If you are working in a networked environment,
 	  <tt/lprm/ will let you remove jobs only from the host from
 	  which the jobs were submitted, even if the same printer is
 	  available from other hosts.  The following command sequence
@@ -1508,7 +1508,7 @@ rose%
 	      id="printing:lpr:options:format"></heading>
 
 	  <p> The following <tt/lpr/ options control formatting of the
-	    files in the job.  Use these options if the job doesn't
+	    files in the job.  Use these options if the job does not
 	    contain plain text or if you want plain text formatted
 	    through the <tt/pr/ utility.
 
@@ -1518,7 +1518,7 @@ rose%
 <tscreen><verb>
 lpr -P bamboo -d fish-report.dvi
 </verb></tscreen>
-	    These options apply to every file in the job, so you can't
+	    These options apply to every file in the job, so you cannot
 	    mix (say) DVI and ditroff files together in a job.
 	    Instead, submit the files as separate jobs, using a
 	    different conversion option for each job.
@@ -1545,7 +1545,7 @@ lpr -P bamboo -d fish-report.dvi
 		<it/number/, indent by 8 columns.  This option works
 		only with certain conversion filters.
 
-		<em/Note:/ Don't put any space between the <tt/-i/ and
+		<em/Note:/ Do not put any space between the <tt/-i/ and
 		the number.
 
 	      <tag/<tt/-l//
@@ -1571,7 +1571,7 @@ lpr -P bamboo -d fish-report.dvi
 
 	    </descrip>
 		
-	    Here's an example: this command prints a nicely
+	    Here is an example: this command prints a nicely
 	    formatted version of the <tt/ls/ manual page on the
 	    default printer:
 <tscreen><verb>
@@ -1617,26 +1617,26 @@ lpr -#3 parser.c parser.h
 		it will tell you if the job completed successfully or
 		if there was an error, and (often) what the error was.
 
-	      <tag/-s/ Don't copy the files to the spooling directory,
+	      <tag/-s/ Do not copy the files to the spooling directory,
 		but make symbolic links to them instead.
 
-		If you're printing a large job, you probably want to
+		If you are printing a large job, you probably want to
 		use this option.  It saves space in the spooling
 		directory (your job might overflow the free space on
 		the filesystem where the spooling directory resides).
-		It saves time as well since LPD won't have to copy
+		It saves time as well since LPD will not have to copy
 		each and every byte of your job to the spooling
 		directory.
 
 		There is a drawback, though: since LPD will refer to
-		the original files directly, you can't modify or
+		the original files directly, you cannot modify or
 		remove them until they have been printed.
 
-		<em/Note:/ If you're printing to a remote printer, LPD
+		<em/Note:/ If you are printing to a remote printer, LPD
 		will eventually have to copy files from the local host
 		to the remote host, so the <tt/-s/ option will save
 		space only on the local spooling directory, not the
-		remote.  It's still useful, though.
+		remote.  It is still useful, though.
 
 	      <tag/-r/
 
@@ -1667,7 +1667,7 @@ lpr -#3 parser.c parser.h
 
 		Replace the job name on the header page with
 		<it/text/.  The job name is normally the name of the
-		first file of the job, or ``stdin'' if you're printing
+		first file of the job, or ``stdin'' if you are printing
 		standard input.
 
 	      <tag/-h/
@@ -1683,7 +1683,7 @@ lpr -#3 parser.c parser.h
       <sect1><heading>Administrating Printers<label
 	    id="printing:lpc"></heading>
 
-	<p> As an administrator for your printers, you've had to
+	<p> As an administrator for your printers, you have had to
 	  install, set up, and test them.  Using the <tt/lpc/ command,
 	  you can interact with your printers in yet more ways.  With
 	  <tt/lpc/, you can
@@ -1697,14 +1697,14 @@ lpr -#3 parser.c parser.h
 	  </itemize>
 
 	  First, a note about terminology: if a printer is
-	  <em/stopped/, it won't print anything in its queue.  Users
+	  <em/stopped/, it will not print anything in its queue.  Users
 	  can still submit jobs, which will wait in the queue until
 	  the printer is <em/started/ or the queue is cleared.
 
 	  If a queue is <em/disabled/, no user (except root) can
 	  submit jobs for the printer.  An <em/enabled/ queue allows
 	  jobs to be submitted.  A printer can be <em/started/ for a
-	  disabled queue, in which case it'll continue to print jobs
+	  disabled queue, in which case it will continue to print jobs
 	  in the queue until the queue is empty.
 
 	  In general, you have to have root privileges to use the
@@ -1727,10 +1727,10 @@ lpr -#3 parser.c parser.h
 	    <tag/<tt/clean <it/printer-name///
 
 	      Remove old files from the printer's spooling directory.
-	      Occasionally, the files that make up a job aren't
+	      Occasionally, the files that make up a job are not
 	      properly removed by LPD, particularly if there have been
 	      errors during printing or a lot of administrative
-	      activity.  This command finds files that don't belong in
+	      activity.  This command finds files that do not belong in
 	      the spooling directory and removes them.
 
 	    <tag/<tt/disable <it/printer-name///
@@ -1740,9 +1740,9 @@ lpr -#3 parser.c parser.h
 	      queue.  The superuser (root) can always submit jobs,
 	      even to a disabled queue.
 
-	      This command is useful while you're testing a new
+	      This command is useful while you are testing a new
 	      printer or filter installation: disable the queue and
-	      submit jobs as root.  Other users won't be able to
+	      submit jobs as root.  Other users will not be able to
 	      submit jobs until you complete your testing and re-enable
 	      the queue with the <tt/enable/ command.
 
@@ -1756,7 +1756,7 @@ lpr -#3 parser.c parser.h
 	    <tag/<tt/enable <it/printer-name///
 
 	      Enable the queue for a printer.  Users can submit jobs
-	      but the printer won't print anything until it's started.
+	      but the printer will not print anything until it is started.
 
 	    <tag/<tt/help <it/command-name///
 
@@ -1768,7 +1768,7 @@ lpr -#3 parser.c parser.h
 
 	      Start the printer.  Ordinary users can use this command
 	      if some extraordinary circumstance hangs LPD, but they
-	      can't start a printer stopped with either the <tt/stop/
+	      cannot start a printer stopped with either the <tt/stop/
 	      or <tt/down/ commands.  The <tt/restart/ command is
 	      equivalent to <tt/abort/ followed by <tt/start/.
 
@@ -1780,7 +1780,7 @@ lpr -#3 parser.c parser.h
 	    <tag/<tt/stop <it/printer-name///
 
 	      Stop the printer.  The printer will finish the current
-	      job and won't print anything else in its queue.  Even
+	      job and will not print anything else in its queue.  Even
 	      though the printer is stopped, users can still submit
 	      jobs to an enabled queue.
 
@@ -1789,7 +1789,7 @@ lpr -#3 parser.c parser.h
 	      Rearrange the queue for <it/printer-name/ by placing the
 	      jobs with the listed <it/job/ numbers or the jobs
 	      belonging to <it/username/ at the top of the queue.  For
-	      this command, you can't use <tt/all/ as the
+	      this command, you cannot use <tt/all/ as the
 	      <it/printer-name/.
 
 	    <tag/<tt/up <it/printer-name///
@@ -1801,7 +1801,7 @@ lpr -#3 parser.c parser.h
 	  </descrip>
 
 	  <tt/lpc/ accepts the above commands on the command line.  If
-	  you don't enter any commands, <tt/lpc/ enters an interactive
+	  you do not enter any commands, <tt/lpc/ enters an interactive
 	  mode, where you can enter commands until you type <tt/exit/,
 	  <tt/quit/, or end-of-file.
 
@@ -1831,22 +1831,22 @@ lpr -#3 parser.c parser.h
 	  the filter's responsibility to handle these aspects.  And the
 	  bad news is that most of the time <em/you/ have to provide
 	  filters yourself.  The good news is that many are generally
-	  available; when they're not, they're usually easy to write.
+	  available; when they are not, they are usually easy to write.
 
 	  Also, FreeBSD comes with one, <tt>/usr/libexec/lpr/lpf</tt>,
 	  that works with many printers that can print plain text.
 	  (It handles backspacing and tabs in the file, and does
-	  accounting, but that's about all it does.)  There are also
+	  accounting, but that is about all it does.)  There are also
 	  several filters and filter components in the FreeBSD ports
 	  collection.
 
-	  Here's what you'll find in this section:
+	  Here is what you will find in this section:
 
 	  <itemize>
 	    <item>Section <ref id="printing:advanced:filters"
 	      name="How Fitlers Work">, tries to give an overview of a
 	      filter's role in the printing process.  You should read
-	      this section to get an understanding of what's happening
+	      this section to get an understanding of what is happening
 	      ``under the hood'' when LPD uses filters.  This
 	      knowledge could help you anticipate and debug problems
 	      you might encounter as you install more and more filters
@@ -1854,7 +1854,7 @@ lpr -#3 parser.c parser.h
 	      
 	    <item>LPD expects every printer to be able to print plain
 	      text by default.  This presents a problem for PostScript
-	      (or other language-based printers) which can't directly
+	      (or other language-based printers) which cannot directly
 	      print plain text.  Section <ref
 	      id="printing:advanced:if-conversion" name="Accommodating
 	      Plain Text Jobs on PostScript Printers"> tells you what
@@ -1869,7 +1869,7 @@ lpr -#3 parser.c parser.h
 	      tells how you can further modify a printer's text filter
 	      to accept and print PostScript data on a
 	      <em/non-PostScript/ printer.  I recommend reading this
-	      section if you don't have a PostScript printer.
+	      section if you do not have a PostScript printer.
 	      
 	    <item>Section <ref id="printing:advanced:convfilters"
 		name="Conversion Filters"> tells about a way you can
@@ -1884,7 +1884,7 @@ lpr -#3 parser.c parser.h
 
 	    <item>Section <ref id="printing:advanced:of" name="Output
 		Filters"> tells all about a not often used feature of
-		LPD: output filters.  Unless you're printing header
+		LPD: output filters.  Unless you are printing header
 		pages (see <ref id="printing:advanced:header-pages"
 		name="Header Pages">), you can probably skip that
 		section altogether.
@@ -1914,7 +1914,7 @@ lpr -#3 parser.c parser.h
 	    <tt>/dev/console</tt> by default).
 
 	    Which filter LPD starts and the filter's arguments depend
-	    on what's listed in the <tt>/etc/printcap</tt> file and
+	    on what is listed in the <tt>/etc/printcap</tt> file and
 	    what arguments the user specified for the job on the
 	    <tt/lpr/ command line.  For example, if the user typed
 	    <tt/lpr -t/, LPD would start the troff filter, listed in
@@ -1931,11 +1931,11 @@ lpr -#3 parser.c parser.h
 		<em/input filter/ in LPD documentation, handles
 		regular text printing.  Think of it as the default
                 filter.  LPD expects every printer to be able to print
-		plain text by default, and it's the text filter's job
+		plain text by default, and it is the text filter's job
 		to make sure backspaces, tabs, or other special
-		characters don't confuse the printer.
+		characters do not confuse the printer.
 
-		If you're in an environment where you have to account
+		If you are in an environment where you have to account
 		for printer usage, the text filter must also account
 		for pages printed, usually by counting the number of
 		lines printed and comparing that to the number of
@@ -1985,7 +1985,7 @@ lpr -#3 parser.c parser.h
 
 	      <item>A <em/conversion filter/ converts a specific file
 		format into one the printer can render onto paper.
-		For example, ditroff typesetting data can't be
+		For example, ditroff typesetting data cannot be
 		directly printed, but you can install a conversion
 		filter for ditroff files to convert the ditroff data
 		into a form the printer can digest and print.  Section
@@ -2003,7 +2003,7 @@ lpr -#3 parser.c parser.h
 		capability (default 0) and <it/pixel-height/ is the
 		value from the <tt/py/ capability (default 0).
 
-	      <item>The <em/output filter/ is used only if there's no
+	      <item>The <em/output filter/ is used only if there is no
 		text filter, or if header pages are enabled.  In my
 		experience, output filters are rarely used.  Section
 		<ref id="printing:advanced:of" name="Output Filters">
@@ -2031,7 +2031,7 @@ lpr -#3 parser.c parser.h
 
 	      <tag/exit 2/
 
-	        If the filter failed to print the file and doesn't
+	        If the filter failed to print the file and does not
 		want LPD to try again.  LPD will throw out the file.
 	    </descrip>
 
@@ -2042,7 +2042,7 @@ lpr -#3 parser.c parser.h
 	    the login, host, and accounting file arguments to make the
 	    accounting entries.
 
-	    If you're shopping for filters, see if they're
+	    If you are shopping for filters, see if they are
 	    LPD-compatible.  If they are, they must support the
 	    argument lists described above.  If you plan on writing
 	    filters for general use, then have them support the same
@@ -2051,28 +2051,28 @@ lpr -#3 parser.c parser.h
 	<sect2><heading>Accommodating Plain Text Jobs on PostScript Printers
 	    <label id="printing:advanced:if-conversion"></heading>
 
-	  <p> If you're the only user of your computer and PostScript
+	  <p> If you are the only user of your computer and PostScript
 	    (or other language-based) printer, and you promise to
 	    never send plain text to your printer and to never use
 	    features of various programs that will want to send plain
-	    text to your printer, then you don't need to worry about
+	    text to your printer, then you do not need to worry about
 	    this section at all.
 
 	    But, if you would like to send both PostScript and plain
-	    text jobs to the printer, then you're urged to augment
+	    text jobs to the printer, then you are urged to augment
 	    your printer setup.  To do so, we have the text filter
 	    detect if the arriving job is plain text or PostScript.
 	    All PostScript jobs must start with <tt/&percnt;!/ (for
 	    other printer languages, see your printer documentation).
 	    If those are the first two characters in the job, we have
 	    PostScript, and can pass the rest of the job directly.  If
-	    those aren't the first two characters in the file, then
+	    those are not the first two characters in the file, then
 	    the filter will convert the text into PostScript and print
 	    the result.
 
 	    How do we do this?
 
-	    If you've got a serial printer, a great way to do it is to
+	    If you have got a serial printer, a great way to do it is to
 	    install <tt/lprps/.  <tt/lprps/ is a PostScript printer
 	    filter which performs two-way communication with the
 	    printer.  It updates the printer's status file with
@@ -2089,7 +2089,7 @@ lpr -#3 parser.c parser.h
 	    (see <ref id="ports" name="The Ports Collection">); if not,
 	    it should be shortly.  You can fetch, build and install it
 	    yourself, of course.  After installing <tt/lprps/, just
-	    specify the pathname to the <tt/psif/ program that's part
+	    specify the pathname to the <tt/psif/ program that is part
 	    of <tt/lprps/.  If you installed <tt/lprps/ from the ports
 	    collection, use the following in the serial PostScript
 	    printer's entry in <tt>/etc/printcap</tt>:
@@ -2100,7 +2100,7 @@ lpr -#3 parser.c parser.h
 	    LPD to open the printer in read-write mode.
 
 	    If you have a parallel PostScript printer (and therefore
-	    can't use two-way communication with the printer, which
+	    cannot use two-way communication with the printer, which
 	    <tt/lprps/ needs), you can use the following shell script
 	    as the text filter:
 <code>
@@ -2152,16 +2152,16 @@ fi
 	    printer.
 
 	    Ghostscript should be in the FreeBSD ports collection, if
-	    you'd like to install it from there.  You can fetch,
+	    you would like to install it from there.  You can fetch,
 	    build, and install it quite easily yourself, as well.
 
 	    To simulate PostScript, we have the text filter detect if
-	    it's printing a PostScript file.  If it's not, then the
+	    it is printing a PostScript file.  If it is not, then the
 	    filter will pass the file directly to the printer;
 	    otherwise, it will use Ghostscript to first convert the
 	    file into a format the printer will understand.
 
-	    Here's an example: the following script is a text filter
+	    Here is an example: the following script is a text filter
 	    for Hewlett Packard DeskJet 500 printers.  For other
 	    printers, substitute the <tt/-sDEVICE/ argument to the
 	    <tt/gs/ (Ghostscript) command.  (Type <tt/gs -h/ to get a
@@ -2186,7 +2186,7 @@ first_two_chars=`expr "$first_line" : '\(..\)'`
 
 if [ "$first_two_chars" = "%!" ]; then
     #
-    #  It's PostScript; use Ghostscript to scan-convert and print it
+    #  It is PostScript; use Ghostscript to scan-convert and print it
     #
     /usr/local/bin/gs -dSAFER -dNOPAUSE -q -sDEVICE=djet500 -sOutputFile=- - \
         &ero;&ero; exit 0
@@ -2206,7 +2206,7 @@ exit 2
 <tscreen><verb>
 	:if=/usr/local/libexec/hpif:
 </verb></tscreen>
-	    That's it.  You can type <tt/lpr plain.text/ and <tt/lpr
+	    That is it.  You can type <tt/lpr plain.text/ and <tt/lpr
 	    whatever.ps/ and both should print successfully.
 
 
@@ -2215,7 +2215,7 @@ exit 2
 
 	  <p> After completing the simple setup described in <ref
 	      name="Simple Printer Setup" id="printing:simple">, the
-	      first thing you'll probably want to do is install
+	      first thing you will probably want to do is install
 	      conversion filters for your favorite file formats
 	      (besides plain ASCII text).
 
@@ -2225,7 +2225,7 @@ exit 2
 	      files easy.  As an example, suppose we do a lot of work
 	      with the TeX typesetting system, and we have a
 	      PostScript printer.  Every time we generate a DVI file
-	      from TeX, we can't print it directly until we convert
+	      from TeX, we cannot print it directly until we convert
 	      the DVI file into PostScript.  The command sequence
 	      goes like this:
 <tscreen><verb>
@@ -2234,7 +2234,7 @@ lpr seaweed-analysis.ps
 </verb></tscreen>
 	      By installing a conversion filter for DVI files, we can
 	      skip the hand conversion step each time by having LPD do
-	      it for us.  Now, each time we get a DVI file, we're just
+	      it for us.  Now, each time we get a DVI file, we are just
 	      one step away from printing it:
 <tscreen><verb>
 lpr -d seaweed-analysis.dvi
@@ -2258,7 +2258,7 @@ lpr -d seaweed-analysis.dvi
 
 	    <p> You should install the conversion filters you expect
 	      to use.  If you print a lot of DVI data, then a DVI
-	      conversion filter is in order.  If you've got plenty of
+	      conversion filter is in order.  If you have got plenty of
 	      troff to print out, then you probably want a troff
 	      filter.
 
@@ -2288,7 +2288,7 @@ plain text         if     none, -p, or -l
 	      text and plot are probably obsolete.  At your site, you
 	      can give new meanings to these or any of the formatting
 	      options just by installing custom filters.  For example,
-	      suppose you'd like to directly print Printerleaf files
+	      suppose you would like to directly print Printerleaf files
 	      (files from the Interleaf desktop publishing program),
 	      but will never print plot files.  You could install a
 	      Printerleaf conversion filter under the <tt/gf/
@@ -2301,15 +2301,15 @@ plain text         if     none, -p, or -l
 	      outside of the base FreeBSD installation, they should
 	      probably go under <tt>/usr/local</tt>.  The directory
 	      <tt>/usr/local/libexec</tt> is a popular location, since
-	      they they're specialized programs that only LPD will
-	      run; regular users shouldn't ever need to run them.
+	      they they are specialized programs that only LPD will
+	      run; regular users should not ever need to run them.
 
 	      To enable a conversion filter, specify its pathname
 	      under the appropriate capability for the destination
 	      printer in <tt>/etc/printcap</tt>.
 
-	      In our example, we'll add the DVI conversion filter to
-	      the entry for the printer named <tt/bamboo/.  Here's the
+	      In our example, we will add the DVI conversion filter to
+	      the entry for the printer named <tt/bamboo/.  Here is the
 	      example <tt>/etc/printcap</tt> file again, with the new
 	      <tt/df/ capability for the printer <tt/bamboo/
 <code>
@@ -2328,7 +2328,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:df=/usr/local/libexec/psdf:
 </code>
 	      The DVI filter is a shell script named
-	      <tt>/usr/local/libexec/psdf</tt>.  Here's that script:
+	      <tt>/usr/local/libexec/psdf</tt>.  Here is that script:
 <code>
 #!bin/sh
 #
@@ -2350,7 +2350,7 @@ exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"
 
 	  <sect3><heading>More Conversion Filter Examples</heading>
 
-	    <p> Since there's no fixed set of steps to install
+	    <p> Since there is no fixed set of steps to install
 	      conversion filters, let me instead provide more
 	      examples.  Use these as guidance to making your own
 	      filters.  Use them directly, if appropriate.
@@ -2375,7 +2375,7 @@ giftopnm | ppmtopgm | pgmtopbm | pbmtolj -resolution 300 \
 	      converting that into a portable bitmap, and converting
 	      that into LaserJet/PCL-compatible data.
 
-	      Here's the <tt>/etc/printcap</tt> file with an entry for
+	      Here is the <tt>/etc/printcap</tt> file with an entry for
 	      a printer using the above filter:
 <code>
 #
@@ -2400,7 +2400,7 @@ exec grops | /usr/local/libexec/lprps "$@"
 </code>
 	      The above script makes use of <tt/lprps/ again to handle
 	      the communication with the printer.  If the printer were
-	      on a parallel port, we'd use this script instead:
+	      on a parallel port, we would use this script instead:
 <code>
 #!/bin/sh
 #
@@ -2409,15 +2409,15 @@ exec grops | /usr/local/libexec/lprps "$@"
 #
 exec grops
 </code>
-	      That's it.  Here's the entry we need to add to
+	      That is it.  Here is the entry we need to add to
 	      <tt>/etc/printcap</tt> to enable the filter:
 <tscreen><verb>
 	:tf=/usr/local/libexec/pstf:
 </verb></tscreen>
 
-              Here's an example that might make old hands at FORTRAN
-              blush.  It's a FORTRAN-text filter for any printer that
-	      can directly print plain text.  We'll install it for the
+              Here is an example that might make old hands at FORTRAN
+              blush.  It is a FORTRAN-text filter for any printer that
+	      can directly print plain text.  We will install it for the
 	      printer <tt/teak/:
 <code>
 #!/bin/sh
@@ -2429,13 +2429,13 @@ exec grops
 printf "\033&ero;k2G" &ero;&ero; fpr &ero;&ero; printf "\f" &ero;&ero; exit 0
 exit 2
 </code>
-	      And we'll add this line to the <tt>/etc/printcap</tt>
+	      And we will add this line to the <tt>/etc/printcap</tt>
 	      for the printer <tt/teak/ to enable this filter:
 <tscreen><verb>
 	:rf=/usr/local/libexec/hprf:
 </verb></tscreen>
 
-	      Here's one final, somewhat complex example.  We'll add a
+	      Here is one final, somewhat complex example.  We will add a
 	      DVI filter to the LaserJet printer <tt/teak/ introduced
 	      earlier.  First, the easy part: updating
 	      <tt>/etc/printcap</tt> with the location of the DVI
@@ -2454,8 +2454,8 @@ exit 2
 	      codes.
 
 	      <tt/dvilj2p/ makes the filter <tt/hpdf/ quite complex
-	      since <tt/dvilj2p/ can't read from standard input.  It
-	      wants to work with a filename.  What's worse, the
+	      since <tt/dvilj2p/ cannot read from standard input.  It
+	      wants to work with a filename.  What iss worse, the
 	      filename has to end in <tt/.dvi/ so using
 	      <tt>/dev/fd/0</tt> for standard input is problematic.
 	      We can get around that problem by linking (symbolically)
@@ -2464,18 +2464,18 @@ exit 2
 	      from standard input.
 
 	      The only other fly in the ointment is the fact that we
-	      can't use /tmp for the temporary link.  Symbolic links
+	      cannot use /tmp for the temporary link.  Symbolic links
 	      are owned by user and group <tt/bin/.  The filter runs
 	      as user <tt/daemon/.  And the <tt>/tmp</tt> directory
 	      has the sticky bit set.  The filter can create the link,
-	      but it won't be able clean up when done and remove it
+	      but it will not be able clean up when done and remove it
 	      since the link will belong to a different user.
 
 	      Instead, the filter will make the symbolic link in the
 	      current working directory, which is the spooling
 	      directory (specified by the <tt/sd/ capability in
 	      <tt>/etc/printcap</tt>).  This is a perfect place for
-	      filters to do their work, especially since there's
+	      filters to do their work, especially since there is
 	      (sometimes) more free disk space in the spooling directory
 	      than under <tt>/tmp</tt>.
 
@@ -2499,7 +2499,7 @@ cleanup() {
 
 #
 #  Define a function to handle fatal errors: print the given message
-#  and exit 2.  Exiting with 2 tells LPD to don't try to reprint the
+#  and exit 2.  Exiting with 2 tells LPD to do not try to reprint the
 #  job.
 #
 fatal() {
@@ -2515,7 +2515,7 @@ fatal() {
 trap cleanup 1 2 15 
 
 #
-#  Make sure we're not colliding with any existing files.
+#  Make sure we are not colliding with any existing files.
 #
 cleanup
 
@@ -2530,7 +2530,7 @@ ln -s /dev/fd/0 hpdf$$.dvi || fatal "Cannot symlink /dev/fd/0"
 printf "\033&ero;k2G" || fatal "Cannot initialize printer"
 
 # 
-#  Convert and print.  Return value from dvilj2p doesn't seem to be
+#  Convert and print.  Return value from dvilj2p does not seem to be
 #  reliable, so we ignore it.
 #
 dvilj2p -M1 -q -e- dfhp$$.dvi
@@ -2548,19 +2548,19 @@ exit 0
 	    <p> All these conversion filters accomplish a lot for your
 	      printing environment, but at the cost forcing the user
 	      to specify (on the <tt/lpr/ command line) which one to
-	      use.  If your users aren't particularly computer
+	      use.  If your users are not particularly computer
 	      literate, having to specify a filter option will become
-	      annoying.  What's worse, though, is that an incorrectly
+	      annoying.  What is worse, though, is that an incorrectly
 	      specified filter option may run a filter on the wrong
 	      type of file and cause your printer to spew out hundreds
 	      of sheets of paper.
 
 	      Rather than install conversion filters at all, you might
-	      want to try having the text filter (since it's the
+	      want to try having the text filter (since it is the
 	      default filter) detect the type of file it has been asked to
 	      print and then automatically run the right conversion
 	      filter.  Tools such as <tt/file/ can be of help here.
-	      Of course, it'll be hard to determine the differences
+	      Of course, it will be hard to determine the differences
 	      between <em/some/ file types---and, of course, you can
 	      still provide conversion filters just for them.
 
@@ -2573,20 +2573,20 @@ exit 0
 	      id="printing:advanced:of"></heading>
 	  
 	  <p> The LPD spooling system supports one other type of
-	    filter that we've not yet explored: an output filter.  An
+	    filter that we have not yet explored: an output filter.  An
 	    output filter is intended for printing plain text only,
 	    like the text filter, but with many simplifications.  If
-	    you're using an output filter but no text filter, then
+	    you are using an output filter but no text filter, then
 	    <itemize>
 	      <item>LPD starts an output filter once for the entire
 		job instead of once for each file in the job.
 
-	      <item>LPD doesn't make any provision to identify the
+	      <item>LPD does not make any provision to identify the
 		start or the end of files within the job for the
 		output filter.
 
-	      <item>LPD doesn't pass the user's login or host to
-		the filter, so it's not intended to do accounting.  In
+	      <item>LPD does not pass the user's login or host to
+		the filter, so it is not intended to do accounting.  In
 		fact, it gets only two arguments:
 <tscreen>
 <tt>-w<it/width/ -l<it/length/</tt>
@@ -2596,9 +2596,9 @@ exit 0
 		printer in question.
 	    </itemize>
 
-	    Don't be seduced by an output filter's simplicity.  If
-	    you'd like each file in a job to start on a different page
-	    an output filter <em/won't work/.  Use a text filter (also
+	    Do not be seduced by an output filter's simplicity.  If
+	    you would like each file in a job to start on a different page
+	    an output filter <em/will not work/.  Use a text filter (also
 	    known as an input filter); see section <ref
 	    id="printing:textfilter" name="Installing the Text
 	    Filter">.  Furthermore, an output filter is actually
@@ -2609,9 +2609,9 @@ exit 0
 	    However, an output filter is <em/necessary/ if you want
 	    header pages and need to send escape sequences or other
 	    initialization strings to be able to print the header
-	    page.  (But it's also <em/futile/ if you want to charge
+	    page.  (But it is also <em/futile/ if you want to charge
 	    header pages to the requesting user's account, since LPD
-	    doesn't give any user or host information to the output
+	    does not give any user or host information to the output
 	    filter.)
 
 	    On a single printer, LPD allows both an output filter and
@@ -2622,10 +2622,10 @@ exit 0
 	    itself/ by sending two bytes to the filter: ASCII 031
 	    followed by ASCII 001.  When an output filter sees these
 	    two bytes (031, 001), it should stop by sending SIGSTOP to
-	    itself.  When LPD's done running other filters, it'll
+	    itself.  When LPD's done running other filters, it will
 	    restart the output filter by sending SIGCONT to it.
 
-	    If there's an output filter but <em/no/ text filter and
+	    If there is an output filter but <em/no/ text filter and
 	    LPD is working on a plain text job, LPD uses the output
 	    filter to do the job.  As stated before, the output filter
 	    will print each file of the job in sequence with no
@@ -2635,7 +2635,7 @@ exit 0
 
 	    The program <tt/lpf/, which we introduced earlier as a text
 	    filter, can also run as an output filter.  If you need a
-	    quick-and-dirty output filter but don't want to write the
+	    quick-and-dirty output filter but do not want to write the
 	    byte detection and signal sending code, try <tt/lpf/.  You
 	    can also wrap <tt/lpf/ in a shell script to handle any
 	    initialization codes the printer might require.
@@ -2653,7 +2653,7 @@ exit 0
 
 	    <tt/lpf/ is suitable for many printing environments.  And
 	    although it has no capability to send initialization
-	    sequences to a printer, it's easy to write a shell script
+	    sequences to a printer, it is easy to write a shell script
 	    to do the needed initialization and then execute <tt/lpf/.
 
 	    In order for <tt/lpf/ to do page accounting correctly, it
@@ -2673,12 +2673,12 @@ exit 0
 	  <em/header pages/ as a necessary evil.
 
 	  Header pages, also known as <em/banner/ or <em/burst pages/
-	  identify to whom jobs belong after they're printed.  They're
+	  identify to whom jobs belong after they are printed.  They are
 	  usually printed in large, bold letters, perhaps with
 	  decorative borders, so that in a stack of printouts they
 	  stand out from the real documents that comprise users' jobs.
 	  They enable users to locate their jobs quickly.  The obvious
-	  drawback to a header page is that it's yet one more sheet
+	  drawback to a header page is that it is yet one more sheet
 	  that has to be printed for every job, their ephemeral
 	  usefulness lasting not more than a few minutes, ultimately
 	  finding themselves in a recycling bin or rubbish heap.
@@ -2687,7 +2687,7 @@ exit 0
 
 	  The LPD system can provide header pages automatically for
 	  your printouts <em/if/ your printer can directly print plain
-	  text.  If you have a PostScript printer, you'll need an
+	  text.  If you have a PostScript printer, you will need an
 	  external program to generate the header page; see <ref
 	  id="printing:advanced:header-pages:ps" name="Header Pages on
 	  PostScript Printers">.
@@ -2703,9 +2703,9 @@ exit 0
 
 	    Sounds too easy, right?
 
-	    You're right.  You <em/might/ have to provide an output
+	    You are right.  You <em/might/ have to provide an output
 	    filter to send initialization strings to the printer.
-	    Here's an example output filter for Hewlett Packard
+	    Here is an example output filter for Hewlett Packard
 	    PCL-compatible printers:
 <code>
 #!/bin/sh
@@ -2721,7 +2721,7 @@ exec /usr/libexec/lpr/lpf
 	    capability.  See <ref id="printing:advanced:of"
 	    name="Output Filters"> for more information.
 
-	    Here's an example <tt>/etc/printcap</tt> file for the printer
+	    Here is an example <tt>/etc/printcap</tt> file for the printer
 	    <tt/teak/ that we introduced earlier; we enabled header
 	    pages and added the above output filter:
 <code>
@@ -2751,7 +2751,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
 
 	  <p> By enabling header pages, LPD will produce a <em/long
 	      header/, a full page of large letters identifying the
-	    user, host, and job.  Here's an example (kelly printed
+	    user, host, and job.  Here is an example (kelly printed
 	    the job named outline from host rose):
 <tscreen><verb>
 k                   ll       ll
@@ -2828,18 +2828,18 @@ rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995
 
 	    Because the output filter is the only external program
 	    that will have control when the header page is printed
-	    that could do accounting, and it isn't provided with any
+	    that could do accounting, and it is not provided with any
 	    <em/user or host/ information or an accounting file, so it
-	    has no idea whom to charge for printer use.  It's also not
+	    has no idea whom to charge for printer use.  It is also not
 	    enough to just ``add one page'' to the text filter or any
 	    of the conversion filters (which do have user and host
 	    information) since users can suppress header pages with
 	    <tt/lpr -h/.  They could still be charged for header pages
-	    they didn't print.  Basically, <tt/lpr -h/ will be the
+	    they did not print.  Basically, <tt/lpr -h/ will be the
 	    preferred option of environmentally-minded users, but you
-	    can't offer any incentive to use it.
+	    cannot offer any incentive to use it.
 
-	    It's <em/still not enough/ to have each of the filters
+	    It is <em/still not enough/ to have each of the filters
 	    generate their own header pages (thereby being able to
 	    charge for them).  If users wanted the option of
 	    suppressing the header pages with <tt/lpr -h/, they will
@@ -2860,10 +2860,10 @@ rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995
 		LPD.
 
 	      <item>Write a <em/smart/ output filter.  Normally, an
-		output filter isn't meant to do anything more than
+		output filter is not meant to do anything more than
 		initialize a printer or do some simple character
-		conversion.  It's suited for header pages and plain
-		text jobs (when there's no text (input) filter).
+		conversion.  It is suited for header pages and plain
+		text jobs (when there is no text (input) filter).
 
 		But, if there is a text filter for the plain text
 		jobs, then LPD will start the output filter only for
@@ -2871,8 +2871,8 @@ rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995
 		header page text that LPD generates to determine what
 		user and host to charge for the header page.  The only
 		other problem with this method is that the output
-		filter still doesn't know what accounting file to use
-		(it's not passed the name of the file from the <tt/af/
+		filter still does not know what accounting file to use
+		(it is not passed the name of the file from the <tt/af/
 		capability), but if you have a well-known accounting
 		file, you can hard-code that into the output filter.
 
@@ -2889,7 +2889,7 @@ rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995
 
 	  <p> As described above, LPD can generate a plain text header
 	    page suitable for many printers.  Of course, PostScript
-	    can't directly print plain text, so the header page
+	    cannot directly print plain text, so the header page
 	    feature of LPD is useless---or mostly so.
 
 	    One obvious way to get header pages is to have every
@@ -2899,7 +2899,7 @@ rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995
 	    drawback of this method is that users will always get a
 	    header page, even if they submit jobs with <tt/lpr -h/.
 
-	    Let's explore this method.  The following script takes
+	    Let us explore this method.  The following script takes
 	    three arguments (user login name, host name, and job name)
 	    and makes a simple PostScript header page:
 <code>
@@ -2911,7 +2911,7 @@ rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995
 
 #
 #  These are PostScript units (72 to the inch).  Modify for A4 or
-#  whatever size paper you're using:
+#  whatever size paper you are using:
 #
 page_width=612
 page_height=792
@@ -2940,7 +2940,7 @@ exec cat <<EOF
 %!PS
 
 %
-%  Make sure we don't interfere with user's job that will follow
+%  Make sure we do not interfere with user's job that will follow
 %
 save
 
@@ -2977,7 +2977,7 @@ $page_width ($user) stringwidth pop sub 2 div $page_height 200 sub moveto
 } forall
 
 %
-%  That's it
+%  That is it
 %
 restore
 showpage
@@ -2985,7 +2985,7 @@ EOF
 </code>
 	    Now, each of the conversion filters and the text filter
 	    can call this script to first generate the header page,
-	    and then print the user's job.  Here's the DVI conversion
+	    and then print the user's job.  Here is the DVI conversion
 	    filter from earlier in this document, modified to make a
 	    header page:
 <code>
@@ -3028,20 +3028,20 @@ done
 	    (see section <ref id="printing:advanced:filters" name="How
 	    Filters Work">).
 
-	    As we've mentioned before, the above scheme, though fairly
+	    As we have mentioned before, the above scheme, though fairly
 	    simple, disables the ``suppress header page'' option (the
 	    <tt/-h/ option) to <tt/lpr/.  If users wanted to save a
 	    tree (or a few pennies, if you charge for header pages),
-	    they wouldn't be able to do so, since every filter's going
+	    they would not be able to do so, since every filter's going
 	    to print a header page with every job.
 
 	    To allow users to shut off header pages on a per-job
-	    basis, you'll need to use the trick introduced in section
+	    basis, you will need to use the trick introduced in section
 	    <ref id="printing:advanced:header-pages:accounting"
 	    name="Accounting for Header Pages">: write an output
 	    filter that parses the LPD-generated header page and
 	    produces a PostScript version.  If the user submits the
-	    job with <tt/lpr -h/, then LPD won't generate a header
+	    job with <tt/lpr -h/, then LPD will not generate a header
 	    page, and neither will your output filter.  Otherwise,
 	    your output filter will read the text from LPD and send
 	    the appropriate header page PostScript code to the
@@ -3050,7 +3050,7 @@ done
 	    If you have a PostScript printer on a serial line, you
 	    can make use of <tt/lprps/, which comes with an output
 	    filter, <tt/psof/, which does the above.  Note that
-	    <tt/psof/ doesn't charge for header pages.
+	    <tt/psof/ does not charge for header pages.
 
       <sect1><heading>Networked Printing<label
 	    id="printing:advanced:network-printers"></heading>
@@ -3109,9 +3109,9 @@ done
 	    advanced setup in <ref id="printing:advanced"
 	    name="Advanced Printer Setup"> that you need.  Make sure
 	    to test the printer and see if it works with the features
-	    of LPD you've enabled.
+	    of LPD you have enabled.
 
-	    If you're using a printer with a network interface that's
+	    If you are using a printer with a network interface that is
 	    compatible with LPD, then the <em/printer host/ in the
 	    discussion below is the printer itself, and the
 	    <em/printer name/ is the name you configured for the
@@ -3139,17 +3139,17 @@ done
 	      <item>Place the printer name on the <em/printer host/ in
 		the <tt/rp/ capability.
 	    </enum>
-	    That's it.  You don't need to list conversion filters,
+	    That is it.  You do not need to list conversion filters,
 	    page dimensions, or anything else in the
 	    <tt>/etc/printcap</tt> file.
 
-	    Here's an example.  The host rose has two printers,
-	    <tt/bamboo/ and <tt/rattan/.  We'll enable users on the
-	    host orchid to print to those printers.  Here's the
+	    Here is an example.  The host rose has two printers,
+	    <tt/bamboo/ and <tt/rattan/.  We will enable users on the
+	    host orchid to print to those printers.  Here is the
 	    <tt>/etc/printcap</tt> file for orchid (back from section
 	    <ref id="printing:advanced:header-pages:enabling"
 	    name="Enabling Header Pages">).  It already had the entry
-	    for the printer <tt/teak/; we've added entries for the two
+	    for the printer <tt/teak/; we have added entries for the two
 	    printers on the host rose:
 <code>
 #
@@ -3157,7 +3157,7 @@ done
 #
 
 #
-#  teak is local; it's connected directly to orchid:
+#  teak is local; it is connected directly to orchid:
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
 	:lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\
@@ -3212,15 +3212,15 @@ lpr -P bamboo -d sushi-review.dvi
 
 	    The format of the <tt>/etc/printcap</tt> file lets you
 	    specify what serial or parallel interface to use, and (if
-	    you're using a serial interface), what baud rate, whether
+	    you are using a serial interface), what baud rate, whether
 	    to use flow control, delays for tabs, conversion of
-	    newlines, and more.  But there's no way to specify a
-	    connection to a printer that's listening on a TCP/IP or
+	    newlines, and more.  But there is no way to specify a
+	    connection to a printer that is listening on a TCP/IP or
 	    other network port.
 
 	    To send data to a networked printer, you need to develop a
 	    communications program that can be called by the text and
-	    conversion filters.  Here's one such example: the script
+	    conversion filters.  Here is one such example: the script
 	    <tt/netprint/ takes all data on standard input and sends
 	    it to a network-attached printer.  We specify the hostname
 	    of the printer as the first argument and the port number
@@ -3259,7 +3259,7 @@ exit 0;
 	    We can then use this script in various filters.  Suppose
 	    we had a Diablo 750-N line printer connected to the
 	    network.  The printer accepts data to print on port number
-	    5100.  The host name of the printer is scrivener.  Here's
+	    5100.  The host name of the printer is scrivener.  Here is
 	    the text filter for the printer:
 <code>
 #!/bin/sh
@@ -3293,22 +3293,22 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100
 	    tear on your printers, you can disable the <tt/-&num;/ option
 	    to <tt/lpr/ by adding the <tt/sc/ capability to the
 	    <tt>/etc/printcap</tt> file.  When users submit jobs
-	    with the <tt/-&num;/ option, they'll see
+	    with the <tt/-&num;/ option, they will see
 <tscreen><verb>
 lpr: multiple copies are not allowed
 </verb></tscreen>
 
-	    Note that if you've set up access to a printer remotely
+	    Note that if you have set up access to a printer remotely
 	    (see section <ref name="Printers Installed on Remote
 	    Hosts" id="printing:advanced:network:rm">), you need the
 	    <tt/sc/ capability on the remote <tt>/etc/printcap</tt>
 	    files as well, or else users will still be able to submit
 	    multiple-copy jobs by using another host.
 
-	    Here's an example.  This is the <tt>/etc/printcap</tt>
+	    Here is an example.  This is the <tt>/etc/printcap</tt>
 	    file for the host rose.  The printer <tt/rattan/ is quite
-	    hearty, so we'll allow multiple copies, but the laser
-	    printer <tt/bamboo/'s a bit more delicate, so we'll
+	    hearty, so we will allow multiple copies, but the laser
+	    printer <tt/bamboo/'s a bit more delicate, so we will
 	    disable multiple copies by adding the <tt/sc/ capability:
 <code>
 #
@@ -3326,8 +3326,8 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:df=/usr/local/libexec/psdf:
 </code>
 	    Now, we also need to add the <tt/sc/ capability on the
-	    host orchid's <tt>/etc/printcap</tt> (and while we're at
-	    it, let's disable multiple copies for the printer
+	    host orchid's <tt>/etc/printcap</tt> (and while we are at
+	    it, let us disable multiple copies for the printer
 	    <tt/teak/):
 <code>
 #
@@ -3347,7 +3347,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:lp=:rm=rose:rp=bamboo:sd=/var/spool/lpd/bamboo:sc:
 </code>
 	    By using the <tt/sc/ capability, we prevent the use of
-	    <tt/lpr -&num;/, but that still doesn't prevent users from
+	    <tt/lpr -&num;/, but that still does not prevent users from
 	    running <tt/lpr/ multiple times, or from submitting the
 	    same file multiple times in one job like this:
 <tscreen><verb>
@@ -3374,13 +3374,13 @@ lpr: Not a member of the restricted group
 
 	    As with the <tt/sc/ (suppress multiple copies) capability,
 	    you need to specify <tt/rg/ on remote hosts that also have
-	    access to your printers, if you feel it's appropriate (see
+	    access to your printers, if you feel it is appropriate (see
 	    section <ref name="Printers Installed on Remote Hosts"
 	    id="printing:advanced:network:rm">).
 
-	    For example, we'll let anyone access the printer
+	    For example, we will let anyone access the printer
 	    <tt/rattan/, but only those in group <tt/artists/ can use
-	    <tt/bamboo/.  Here's the familiar <tt>/etc/printcap</tt>
+	    <tt/bamboo/.  Here is the familiar <tt>/etc/printcap</tt>
 	    for host rose:
 <code>
 #
@@ -3397,7 +3397,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:if=/usr/local/libexec/psif:\
 	:df=/usr/local/libexec/psdf:
 </code>
-	    Let's leave the other example <tt>/etc/printcap</tt> file
+	    Let us leave the other example <tt>/etc/printcap</tt> file
 	    (for the host orchid) alone.  Of course, anyone on orchid
 	    can print to <tt/bamboo/.  It might be the case that we
 	    only allow certain logins on orchid anyway, and want them
@@ -3411,27 +3411,27 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 
 	  <p> If you have many users accessing the printers, you
 	    probably need to put an upper limit on the sizes of the
-	    files users can submit to print.  After all, there's only
+	    files users can submit to print.  After all, there is only
 	    so much free space on the filesystem that houses the
 	    spooling directories, and you also need to make sure
-	    there's room for the jobs of other users.
+	    there is room for the jobs of other users.
 
 	    LPD enables you to limit the maximum byte size a file in a
 	    job can be with the <tt/mx/ capability.  The units are in
 	    BUFSIZ blocks, which are 1024 bytes.  If you put a zero
-	    for this capability, there'll be no limit on file size.
+	    for this capability, there will be no limit on file size.
 	    Note that the limit applies to <em/files/ in a job, and
 	    <em/not/ the total job size.
 
-	    LPD won't refuse a file that's larger than the limit you
-	    place on a printer.  Instead, it'll queue as much of the
+	    LPD will not refuse a file that is larger than the limit you
+	    place on a printer.  Instead, it will queue as much of the
 	    file up to the limit, which will then get printed.  The
 	    rest will be discarded.  Whether this is correct behavior
 	    is up for debate.
 
-	    Let's add limits to our example printers <tt/rattan/ and
+	    Let us add limits to our example printers <tt/rattan/ and
 	    <tt/bamboo/.  Since those artists' PostScript files tend
-	    to be large, we'll limit them to five megabytes.  We'll
+	    to be large, we will limit them to five megabytes.  We will
 	    put no limit on the plain text line printer:
 <code>
 #
@@ -3456,14 +3456,14 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:df=/usr/local/libexec/psdf:
 </code>
 	    Again, the limits apply to the local users only.  If
-	    you've set up access to your printers remotely, remote
-	    users won't get those limits.  You'll need to specify the
+	    you have set up access to your printers remotely, remote
+	    users will not get those limits.  You will need to specify the
 	    <tt/mx/ capability in the remote <tt>/etc/printcap</tt>
 	    files as well.  See section <ref name="Printers Installed
 	    on Remote Hosts" id="printing:advanced:network:rm"> for
 	    more information on remote printing.
 
-	    There's another specialized way to limit job sizes from
+	    There is another specialized way to limit job sizes from
 	    remote printers; see section <ref
 	    id="printing:advanced:restricting:remote"
 	    name="Restricting Jobs from Remote Printers">.
@@ -3489,7 +3489,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 		also used by the ruserok(3) protocol, and affects
 		programs like <tt/rsh/ and <tt/rcp/, so be careful.
 
-		For example, here's the <tt>/etc/hosts.lpd</tt> file
+		For example, here is the <tt>/etc/hosts.lpd</tt> file
 		on the host rose:
 <code>
 orchid
@@ -3511,16 +3511,16 @@ madrigal.fishbaum.de
 		(512 bytes) of free space there has to be for a remote
 		job to be accepted.
 
-	        This lets you insure that remote users won't fill your
+	        This lets you insure that remote users will not fill your
 		filesystem.  You can also use it to give a certain
-		priority to local users: they'll be able to queue jobs
+		priority to local users: they will be able to queue jobs
 		long after the free disk space has fallen below the
 		amount specified in the <tt/minfree/ file.
 
-	        For example, let's add a <tt/minfree/ file for the
+	        For example, let us add a <tt/minfree/ file for the
 		printer <tt/bamboo/.  We examine
 		<tt>/etc/printcap</tt> to find the spooling directory
-		for this printer; here's <tt/bamboo/'s entry:
+		for this printer; here is <tt/bamboo/'s entry:
 <tscreen><verb>
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:mx#5000:\
@@ -3529,7 +3529,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	:df=/usr/local/libexec/psdf:
 </verb></tscreen>
 		The spooling directory is the given in the <tt/sd/
-		capability.  We'll make three megabytes (which is 6144
+		capability.  We will make three megabytes (which is 6144
 		disk blocks) the amount of free disk space that must
 		exist on the filesystem for LPD to accept remote jobs:
 <tscreen><verb>
@@ -3550,7 +3550,7 @@ echo 6144 > /var/spool/lpd/bamboo/minfree
 		departments sharing a network, and some users
 		transcend departmental boundaries.  By giving them
 		accounts on your systems, they can use your printers
-		from their own departmental systems.  If you'd rather
+		from their own departmental systems.  If you would rather
 		allow them to use <em/only/ your printers and not your
 		compute resources, you can give them ``token''
 		accounts, with no home directory and a useless shell
@@ -3563,12 +3563,12 @@ echo 6144 > /var/spool/lpd/bamboo/minfree
 	<p> So, you need to charge for printouts.  And why not?  Paper
 	  and ink cost money.  And then there are maintenance
 	  costs---printers are loaded with moving parts and tend to
-	  break down.  You've examined your printers, usage patterns,
+	  break down.  You have examined your printers, usage patterns,
 	  and maintenance fees and have come up with a per-page (or
 	  per-foot, per-meter, or per-whatever) cost.  Now, how do you
 	  actually start accounting for printouts?
 
-	  Well, the bad news is the LPD spooling system doesn't
+	  Well, the bad news is the LPD spooling system does not
 	  provide much help in this department.  Accounting is highly
 	  dependent on the kind of printer in use, the formats being
 	  printed, and <em/your/ requirements in charging for printer
@@ -3577,7 +3577,7 @@ echo 6144 > /var/spool/lpd/bamboo/minfree
 	  To implement accounting, you have to modify a printer's text
 	  filter (to charge for plain text jobs) and the conversion
 	  filters (to charge for other file formats), to count pages
-	  or query the printer for pages printed.  You can't get away
+	  or query the printer for pages printed.  You cannot get away
 	  with using the simple output filter, since it cannot do
 	  accounting.  See section <ref name="Filters"
 	  id="printing:advanced:filter-intro">.
@@ -3585,7 +3585,7 @@ echo 6144 > /var/spool/lpd/bamboo/minfree
 	  Generally, there are two ways to do accounting:
 	  <itemize>
 	    <item><em/Periodic accounting/ is the more common way,
-	      possibly because it's easier.  Whenever someone prints a
+	      possibly because it is easier.  Whenever someone prints a
 	      job, the filter logs the user, host, and number of pages
 	      to an accounting file.  Every month, semester, year, or
 	      whatever time period you prefer, you collect the
@@ -3595,7 +3595,7 @@ echo 6144 > /var/spool/lpd/bamboo/minfree
 	      slate for the next period.
 
 	    <item><em/Timely accounting/ is less common, probably
-	      because it's more difficult.  This method has the
+	      because it is more difficult.  This method has the
 	      filters charge users for printouts as soon as they use
 	      the printers.  Like disk quotas, the accounting is
 	      immediate.  You can prevent users from printing when
@@ -3657,10 +3657,10 @@ echo 6144 > /var/spool/lpd/bamboo/minfree
 	    Then, each accounting file will be in the spooling directory
 	    for a printer, in a file named <tt/acct/.
 
-	    When you're ready to charge users for printouts, run the
+	    When you are ready to charge users for printouts, run the
 	    <tt/pac/ program.  Just change to the spooling directory
 	    for the printer you want to collect on and type <tt/pac/.
-	    You'll get a dollar-centric summary like the following:
+	    You will get a dollar-centric summary like the following:
 <code>
   Login               pages/feet   runs    price
 orchid:kelly                5.00    1   $  0.10
@@ -3678,7 +3678,7 @@ total                     337.00  154   $  6.74
 	      <tag/<tt/-P<it/printer///
 
 	        Which <it/printer/ to summarize.  This option works
-		only if there's an absolute path in the <tt/af/
+		only if there is an absolute path in the <tt/af/
 		capability in <tt>/etc/printcap</tt>.
 
 	      <tag/<tt/-c//
@@ -3690,7 +3690,7 @@ total                     337.00  154   $  6.74
 
 		Ignore host name in the accounting files.  With this
 		option, user smith on host alpha is the same user
-		smith on host gamma.  Without, they're different users.
+		smith on host gamma.  Without, they are different users.
 
 	      <tag/<tt/-p<it/price///
 
@@ -3717,7 +3717,7 @@ total                     337.00  154   $  6.74
 
 	    In the default summary that <tt/pac/ produces, you see the
 	    number of pages printed by each user from various hosts.
-	    If, at your site, host doesn't matter (because users can
+	    If, at your site, host does not matter (because users can
 	    use any host), run <tt/pac -m/, to produce the following
 	    summary:
 <code>
@@ -3762,7 +3762,7 @@ pac -p1.50
 
 	    For plain text jobs, the problem's not that hard to solve:
 	    you count how many lines are in a job and compare it to
-	    how many lines per page your printer supports.  Don't
+	    how many lines per page your printer supports.  Do not
 	    forget to take into account backspaces in the file which
 	    overprint lines, or long logical lines that wrap onto one
 	    or more additional physical lines.
@@ -3770,7 +3770,7 @@ pac -p1.50
 	    The text filter <tt/lpf/ (introduced in <ref
 	    id="printing:advanced:lpf" name="lpf: a Text Filter">)
 	    takes into account these things when it does accounting.
-	    If you're writing a text filter which needs to do
+	    If you are writing a text filter which needs to do
 	    accounting, you might want to examine <tt/lpf/'s source
 	    code.
 
@@ -3797,7 +3797,7 @@ pac -p1.50
 	    (networked Imagen laser printers, for example).  Modify
 	    the filters for these printers to get the page usage after
 	    they print each job and have them log accounting
-	    information based on that value <em/only/.  There's no
+	    information based on that value <em/only/.  There is no
 	    line counting nor error-prone file examination required.
 
 	    Of course, you can always be generous and make all
@@ -3806,15 +3806,15 @@ pac -p1.50
     <sect><heading>Alternatives to the Standard Spooler<label
 	  id="printing:lpd-alternatives"></heading> 
 
-      <p> If you've been reading straight through this manual, by now
-	you've learned just about everything there is to know about
+      <p> If you have been reading straight through this manual, by now
+	you have learned just about everything there is to know about
 	the LPD spooling system that comes with FreeBSD.  You can
 	probably appreciate many of its shortcomings, which naturally
 	leads to the question: ``What other spooling systems are out
 	there (and work with FreeBSD)?''
 
-	Unfortunately, I've located only <em/two/ alternatives---and
-	they're almost identical to each other!  They are:
+	Unfortunately, I have located only <em/two/ alternatives---and
+	they are almost identical to each other!  They are:
 	<descrip>
 	  <tag/PLP, the Portable Line Printer Spooler System/
 
@@ -3822,11 +3822,11 @@ pac -p1.50
 	    then maintained by an Internet-wide group of developers.
 	    The main site for the software is at <htmlurl
 	    url="ftp://ftp.iona.ie/pub/plp"
-	    name="ftp://ftp.iona.ie/pub/plp">.  There's also a <htmlurl
+	    name="ftp://ftp.iona.ie/pub/plp">.  There is also a <htmlurl
 	      url="http://www.iona.ie:8000/www/hyplan/jmason/plp.html"
 	      name="web page">.
 
-	    It's quite similar to the BSD LPD spooler, but boasts a
+	    It is quite similar to the BSD LPD spooler, but boasts a
 	    host of features, including:
 	    <itemize>
 	      <item>Better network support, including built-in support
@@ -3857,7 +3857,7 @@ pac -p1.50
 
     <sect><heading>Acknowledgments</heading>
 
-      <p> I'd like to thank the following people who have assisted in
+      <p> I would like to thank the following people who have assisted in
 	the development of this document:
 
 	<descrip>
diff --git a/share/doc/handbook/relnotes.sgml b/share/doc/handbook/relnotes.sgml
index bf941dbabaf2..98a491b65ce0 100644
--- a/share/doc/handbook/relnotes.sgml
+++ b/share/doc/handbook/relnotes.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: relnotes.sgml,v 1.9 1996/01/31 14:26:15 mpp Exp $ -->
+<!-- $Id: relnotes.sgml,v 1.10 1996/02/02 05:27:27 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -28,7 +28,7 @@
 	  the Adaptec 2940 (WIDE and narrow) and many hundreds of
 	  bug fixes.
 
-	  We've also taken the comments and suggestions of many
+	  We have also taken the comments and suggestions of many
 	  of our users to heart and have attempted to provide
 	  what we hope is a more sane and easily understood
 	  installation process.  Your feedback on this
@@ -92,7 +92,7 @@
 	  security may be all you require!  We feel that our
 	  default security model is more than a match for DES,
 	  and without any messy export issues to deal with.  If
-	  you're outside (or even inside) the U.S., give it a
+	  you are outside (or even inside) the U.S., give it a
 	  try!
 
 <![ IGNORE [
@@ -119,7 +119,7 @@
 	  Ethernet adapters, improved support for the Adaptec
 	  2940 and hundreds of bug fixes.
 
-	  We've also taken the comments and suggestions of many
+	  We have also taken the comments and suggestions of many
 	  of our users to heart and have attempted to provide
 	  what we hope is a more sane and easily understood
 	  installation process.  Your feedback on this constantly
@@ -523,7 +523,7 @@
 	  <tag>UNIONFS and LFS</tag> The unionfs and LFS file
 	    systems are known to be severely broken in FreeBSD
 	    2.0.5.  This is in part due to old bugs that we
-	    haven't had time to resolve yet and the need to
+	    have not had time to resolve yet and the need to
 	    update these file systems to deal with the new VM
 	    system.  We hope to address these issues in a later
 	    release of FreeBSD.
@@ -556,7 +556,7 @@
 	The preferred method to submit bug reports from a machine
 	with Internet mail connectivity is to use the send-pr
 	command.  Bug reports will be dutifully filed by our
-	faithful bug-filer program and you can be sure that we'll
+	faithful bug-filer program and you can be sure that we will
 	do our best to respond to all reported bugs as soon as
 	possible.
 
@@ -580,8 +580,8 @@
 	subscribe to: <tscreen>announce@FreeBSD.org</tscreen>
 
 	All but the freebsd-bugs groups can be freely joined by
-	anyone wishing to do so.  Send mail to
-	MajorDomo@FreeBSD.org and include the keyword `help' on a
+	anyone wishing to do so.  Send mail to &a.majordomo
+	and include the keyword `help' on a
 	line by itself somewhere in the body of the message.
 	This will give you more information on joining the
 	various lists, accessing archives, etc.  There are a
diff --git a/share/doc/handbook/routing.sgml b/share/doc/handbook/routing.sgml
index d1080920e2b4..459ca35d24cc 100644
--- a/share/doc/handbook/routing.sgml
+++ b/share/doc/handbook/routing.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: routing.sgml,v 1.1 1995/10/07 04:31:41 jfieber Exp $ -->
+<!-- $Id: routing.sgml,v 1.2 1996/01/31 14:26:16 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
 
@@ -68,7 +68,7 @@ host2.foobar.com link#1             UC          0        0
       (<tt>10.20.30.255</tt> is the broadcast address for the subnet
       <tt>10.20.30</tt>, and <tt>foobar.com</tt> is the domain name
       associated with that subnet). The designation <tt>link&num;1</tt>
-      refers to the first ethernet card in the machine. You'll
+      refers to the first ethernet card in the machine. You will
       notice no additional interface is specified for those.
 
       Both of these groups (local network hosts and local
@@ -150,7 +150,7 @@ host2.foobar.com link#1             UC          0        0
 	world, then the default route will be the gateway machine
 	at your Internet Service Provider's (ISP) site.
 
-	Let's look at an example of default routes. This is a
+	Let us look at an example of default routes. This is a
 	common configuration:
 <tscreen><verb>
 [Local2]  <--ether-->  [Local1]  <--PPP-->  [ISP-Serv]  <--ether-->  [T1-GW]
diff --git a/share/doc/handbook/scsi.sgml b/share/doc/handbook/scsi.sgml
index 7335b49e209d..2e86fe264d6d 100644
--- a/share/doc/handbook/scsi.sgml
+++ b/share/doc/handbook/scsi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: scsi.sgml,v 1.12 1996/01/31 19:03:02 mpp Exp $ -->
+<!-- $Id: scsi.sgml,v 1.13 1996/04/19 21:50:32 asami Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -42,8 +42,8 @@
 
         The SCSI bus is a parallel bus, which comes in a number of
         variants.  The oldest and most used is an 8 bit wide bus, with
-        single-ended signals, carried on 50 wires.  (If you don't know what
-        single-ended means, don't worry, that is what this document is all
+        single-ended signals, carried on 50 wires.  (If you do not know what
+        single-ended means, do not worry, that is what this document is all
         about.)  Modern designs also use 16 bit wide buses, with
         differential signals.  This allows transfer speeds of
         20Mbytes/second, on cables lengths of up to 25 meters. SCSI-2
@@ -112,7 +112,7 @@
 
           So, gold plated connectors, shielded cabling, sturdy connector
           hoods with strain reliefs etc are the way to go. Second golden
-          rule: don't use cables longer than necessary. I once spent 3 days
+          rule: do no use cables longer than necessary. I once spent 3 days
           hunting down a problem with a flaky machine only to discover that
           shortening the SCSI bus by 1 meter solved the problem.  And the
           original bus length was well within the SCSI specification.
@@ -201,7 +201,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 (don't 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
@@ -225,14 +225,14 @@
             reflections or ringing.  If you once made a long distance
             telephone call on a bad line you probably know what reflections
             are.  With 20Mbytes/sec traveling over your SCSI bus, you
-            don't want signals echoing back.
+            do not want signals echoing back.
 
             Terminators come in various incarnations, with more or less
             sophisticated designs.  Of course, there are internal and
             external variants.  Almost every SCSI device comes with a
             number of sockets in which a number of resistor networks can
             (must be!) installed.  If you remove terminators from a device,
-            carefully store 'm. You will need them when you ever decide to
+            carefully store them. You will need them when you ever decide to
             reconfigure your SCSI bus.  There is enough variation in even
             these simple tiny things to make finding the exact replacement
             a frustrating business.  There are also SCSI devices that have
@@ -404,7 +404,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 isn't. 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
@@ -437,7 +437,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 don't 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)
@@ -721,11 +721,11 @@ options        "TUNE_1542"             #dynamic tune of bus DMA speed
           <item>
             If you can compile a kernel, make one with the SCSIDEBUG option,
 	    and try accessing the device with debugging turned on for
-	    that device. If your device doesn't even probe at startup,
+	    that device. If your device does not even probe at startup,
 	    you may have to define the address of the device that
 	    is failing, and the desired debug level in
 	    <tt>/sys/scsi/scsidebug.h</tt>.
-	    If it probes but just doesn't work, you can use the
+	    If it probes but just does not work, you can use the
 	    <tt>scsi(8)</tt> command to dynamically set a debug level to
 	    it in a running kernel (if SCSIDEBUG is defined).
 	    This will give you COPIOUS debugging output with which to confuse
diff --git a/share/doc/handbook/skey.sgml b/share/doc/handbook/skey.sgml
index 70d14db06a7a..c53d66801ead 100644
--- a/share/doc/handbook/skey.sgml
+++ b/share/doc/handbook/skey.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: skey.sgml,v 1.3 1995/10/07 04:31:56 jfieber Exp $ -->
+<!-- $Id: skey.sgml,v 1.4 1996/01/31 14:26:18 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!--
 Copyright 1995 Massachusetts Institute of Technology
@@ -43,12 +43,12 @@ of Bell Communications Research, Inc.
 <!-- XXX - is there a better word to use than UNIX? -->
 <p>There are three different sorts of passwords which we will talk about
 in the discussion below.  The first is your usual UNIX-style or Kerberos
-password; we'll call this a ``UNIX password''.  The second sort is the
+password; we will call this a ``UNIX password''.  The second sort is the
 one-time password which is generated by the S/Key `<tt/key/' program and
-accepted by the `<tt/keyinit/' program and the login prompt; we'll call
+accepted by the `<tt/keyinit/' program and the login prompt; we will call
 this a ``one-time password''.  The final sort of password is the
 secret password which you give to the `<tt/key/' program (and sometimes the
-`<tt/keyinit/' program) which it uses to generate one-time passwords; we'll
+`<tt/keyinit/' program) which it uses to generate one-time passwords; we will
 call it a ``secret password'' or just unqualified ``password''.  
 
 <p>The secret password does not necessarily have anything to do with your
@@ -73,7 +73,7 @@ one-way hash function is used, it is not possible to generate future
 one-time passwords having overheard one which was successfully used;
 the iteration count is decremented after each successful login to keep
 the user and login program in sync.  (When you get the iteration count
-down to 1, it's time to reinitialize S/Key.)
+down to 1, it is time to reinitialize S/Key.)
 
 <p>There are four programs involved in the S/Key system which we will
 discuss below.  The `<tt/key/' program accepts an iteration count, a
@@ -125,7 +125,7 @@ minimum seven words) which will be needed to generate login keys.  The
 line starting `ID' gives the parameters of your particular S/Key
 instance: your login name, the iteration count, and seed.  When
 logging in with S/Key, the system will remember these parameters and
-present them back to you so you don't have to remember them.  The last
+present them back to you so you do not have to remember them.  The last
 line gives the particular one-time password which corresponds to those
 parameters and your secret password; if you were to re-login
 immediately, this one-time password is the one you would use.
@@ -136,7 +136,7 @@ immediately, this one-time password is the one you would use.
 connection, you will need to already have a secure connection to some
 place where you can run the `<tt/key/' program; this might be in the form
 of a desk accessory on a Macintosh, or a shell prompt on a machine you
-trust (we'll show the latter).  You will also need to make up an
+trust (we will show the latter).  You will also need to make up an
 iteration count (100 is probably a good value), and you may make up
 your own seed or use a randomly-generated one.  Over on the insecure
 connection (to the machine you are initializing), use the `<tt/keyinit -s/'
@@ -253,7 +253,7 @@ Enter secret password:
 
 The `<tt/-n 25/' requests twenty-five keys in sequence; the `<tt/57/' indicates
 the <em/ending/ iteration number; and the rest is as before.  Note that
-these are printed out in <em/reverse/ order of eventual use.  If you're
+these are printed out in <em/reverse/ order of eventual use.  If you are
 really paranoid, you might want to write the results down by hand;
 otherwise you can cut-and-paste into `<tt/lpr/'.  Note that each line shows
 both the iteration count and the one-time password; you may still find
diff --git a/share/doc/handbook/slipc.sgml b/share/doc/handbook/slipc.sgml
index 45046d9e5f2a..2b9c09ae93b4 100644
--- a/share/doc/handbook/slipc.sgml
+++ b/share/doc/handbook/slipc.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: slipc.sgml,v 1.4 1995/10/07 04:31:59 jfieber Exp $ -->
+<!-- $Id: slipc.sgml,v 1.5 1995/12/04 17:58:51 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Setting up a SLIP client<label id="slipc"></heading>
@@ -11,8 +11,8 @@ address changes each time you dial up), you probably need to do
 something much fancier.
 
 <!--
-This is just "what I did, and it worked for me".  I'm sharing this
-just for your reference, I'm no expert in SLIP nor networking so your
+This is just "what I did, and it worked for me".  I am sharing this
+just for your reference, I am no expert in SLIP nor networking so your
 mileage may vary.
 -->
 
@@ -27,7 +27,7 @@ Make sure you have
 pseudo-device   sl      1
 </verb>
 in your kernel's config file.  It is included in the GENERIC kernel,
-so this won't be a problem unless you deleted it.
+so this will not be a problem unless you deleted it.
 
 <sect1><heading>Things you have to do only once</heading>
 
@@ -43,7 +43,7 @@ so this won't be a problem unless you deleted it.
 128.32.136.12           ns2.Berkeley.edu ns2
 </verb>
     By the way, silvia is the name of the car that I had when I was
-    back in Japan (it's called 2?0SX here in U.S.).
+    back in Japan (it is called 2?0SX here in U.S.).
 
 <item>Make sure you have "hosts" before "bind" in your <tt>/etc/host.conf</tt>.
     Otherwise, funny things may happen.
@@ -91,7 +91,7 @@ nameserver 128.32.136.12
     actual domain names and addresses depend on your environment.
 
 <item>Set the password for root and toor (and any other accounts that
-    doesn't have a password).  Use passwd, don't edit the <tt>/etc/passwd</tt>
+    does not have a password).  Use passwd, do not edit the <tt>/etc/passwd</tt>
     or <tt>/etc/master.passwd</tt> files!
 
 <item>Reboot your machine and make sure it comes up with the correct
@@ -124,7 +124,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a
     get connected.
 
     <bf>Note</bf>: leaving your password in plain text anywhere in the
-    filesystem is generally a BAD idea.  Do it at your own risk.  I'm
+    filesystem is generally a BAD idea.  Do it at your own risk.  I am
     just too lazy.
 
 <item>Leave the kermit there (you can suspend it by "z") and as root,
@@ -133,7 +133,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a
 slattach -h -c -s 115200 /dev/modem
 </verb>
     if you are able to "ping" hosts on the other side of the router,
-    you are connected! If it doesn't work, you might want to try "-a"
+    you are connected! If it does not work, you might want to try "-a"
     instead of "-c" as an argument to slattach.
 </enum>
 
@@ -144,7 +144,7 @@ slattach -h -c -s 115200 /dev/modem
     and exit from it ("q").
 
     The slattach man page says you have to use "ifconfig sl0 down" to
-    mark the interface down, but this doesn't seem to make any
+    mark the interface down, but this does not seem to make any
     difference for me.  ("ifconfig sl0" reports the same thing.)
 
     Some times, your modem might refuse to drop the carrier (mine
@@ -153,7 +153,7 @@ slattach -h -c -s 115200 /dev/modem
 
 <sect1><heading>Troubleshooting</heading>
 
-<p>If it doesn't work, feel free to ask me.  The things that people
+<p>If it does not work, feel free to ask me.  The things that people
 tripped over so far:
 <itemize>
 <item>Not using "-c" or "-a" in slattach (I have no idea why this can be
diff --git a/share/doc/handbook/slips.sgml b/share/doc/handbook/slips.sgml
index 3f6c2b919d88..3156e98b46b3 100644
--- a/share/doc/handbook/slips.sgml
+++ b/share/doc/handbook/slips.sgml
@@ -46,9 +46,9 @@ Administration</em> published by O'Reilly &amp; Associates, Inc. (ISBN
 Number 0-937175-82-X), or Douglas Comer's books on the TCP/IP
 protocol.
 
-It's further assumed that you have already setup your modem(s) and
+It is further assumed that you have already setup your modem(s) and
 configured the appropriate system files to allow logins through your
-modems.  If you haven't prepared your system for this yet, please see
+modems.  If you have not prepared your system for this yet, please see
 the tutorial for configuring dialup services; if you have a World-Wide
 Web browser available, browse the list of tutorials at
 <tt>http://www.freebsd.org/</tt>; otherwise, check the place
@@ -116,7 +116,7 @@ goes into <tt>/var/log/messages</tt> (see the manual pages for
 <tt>/etc/syslog.conf</tt> to see to which files <tt>syslogd</tt> is
 logging).
 
-OK, enough of the examples -- let's dive into setting up the system.
+OK, enough of the examples -- let us dive into setting up the system.
 
 <sect1><heading>Kernel Configuration</heading>
 <p>
@@ -148,13 +148,13 @@ Internet RFC requirements for Internet hosts (see RFC's 1009
 &lsqb;Requirements for Internet Hosts -- Communication Layers&rsqb;,
 and perhaps 1127 &lsqb;A Perspective on the Host Requirements
 RFCs&rsqb;), so if you want your FreeBSD SLIP Server to act as a
-router, you'll have to add the line
+router, you will have to add the line
 <verb>
 sysctl -w net.inet.ip.forwarding = 0
 </verb>
 to your rc.local file.
 
-You'll notice that near the end of the default kernel configuration
+You will notice that near the end of the default kernel configuration
 file (<tt>/sys/i386/conf/GENERIC</tt>) is a line that reads:
 
 <tscreen><verb>
@@ -231,9 +231,9 @@ included code to make use of the flags).
 
 Your choice of local and remote addresses for your SLIP links depends
 on whether you are going to dedicate a TCP/IP subnet or if you are
-going to use ``proxy ARP'' on your SLIP server (it's not ``true''
+going to use ``proxy ARP'' on your SLIP server (it is not ``true''
 proxy ARP, but that is the terminology used in this document to
-describe it).  If you're not sure which method to select or how to
+describe it).  If you are not sure which method to select or how to
 assign IP addresses, please refer to the TCP/IP books referenced in
 the <ref id="slips:prereqs"> section and/or consult your IP network manager.
 
@@ -249,7 +249,7 @@ subnet.
 
 Otherwise, if you will use the ``proxy ARP'' method, you will need to
 assign your SLIP client's IP addresses out of your SLIP server's
-Ethernet subnet, and you'll also need to adjust your
+Ethernet subnet, and you will also need to adjust your
 <tt>/etc/sliphome/slip.login</tt> and
 <tt>/etc/sliphome/slip.logout</tt> scripts to use <tt>arp(8)</tt> to
 manage the proxy-ARP entries in the SLIP server's ARP table.
@@ -337,7 +337,7 @@ will be unable to execute it.
 
 <p>
 
-<tt>/etc/sliphome/slip.logout</tt> isn't strictly needed (unless you
+<tt>/etc/sliphome/slip.logout</tt> is not strictly needed (unless you
 are implementing ``proxy ARP''), but if you decide to create it, this
 is an example of a basic <tt>slip.logout</tt> script:
 
@@ -357,7 +357,7 @@ is an example of a basic <tt>slip.logout</tt> script:
 ----- end /etc/sliphome/slip.logout -----
 </verb></tscreen>
 
-If you are using ``proxy ARP'', you'll want to have
+If you are using ``proxy ARP'', you will want to have
 <tt>/etc/sliphome/slip.logout</tt> remove the ARP entry for the SLIP
 client:
 
@@ -401,7 +401,7 @@ routers via appropriate routing protocols about your SLIP subnet.
 
 <p>
 Adding static routes to your nearest default routers can be
-troublesome (or impossible, if you don't have authority to do so...).
+troublesome (or impossible, if you do not have authority to do so...).
 If you have a multiple-router network in your organization, some
 routers, such as Cisco and Proteon, may not only need to be configured
 with the static route to the SLIP subnet, but also need to be told
@@ -423,7 +423,7 @@ FreeBSD ``out-of-the-box''.  Complete information and documentation on
 <tt>gated</tt> is available on the Web starting at
 <tt>http://www.gated.cornell.edu/</tt>.  Compile and install it, and
 then write a <tt>/etc/gated.conf</tt> file to configure your gated;
-here's a sample, similar to what the author used on a FreeBSD SLIP
+here is a sample, similar to what the author used on a FreeBSD SLIP
 server:
 
 <tscreen><verb>
@@ -472,17 +472,17 @@ import proto rip interface ed {
 The above sample <tt>gated.conf</tt> file broadcasts routing
 information regarding the SLIP subnet <tt>xxx.xxx.yy</tt> via RIP onto
 the Ethernet; if you are using a different Ethernet driver than the
-<tt/ed/ driver, you'll need to change the references to the <tt/ed/
+<tt/ed/ driver, you will need to change the references to the <tt/ed/
 interface appropriately.  This sample file also sets up tracing to
 <tt>/var/tmp/gated.output</tt> for debugging <tt>gated</tt>'s
 activity; you can certainly turn off the tracing options if
-<tt>gated</tt> works OK for you.  You'll need to change the
+<tt>gated</tt> works OK for you.  You will need to change the
 <tt>xxx.xxx.yy</tt>'s into the network address of your own SLIP subnet
 (be sure to change the net mask in the <tt>proto direct</tt> clause as
 well).
 
 When you get <tt>gated</tt> built and installed and create a
-configuration file for it, you'll need to run <tt>gated</tt> in place
+configuration file for it, you will need to run <tt>gated</tt> in place
 of <tt>routed</tt> on your FreeBSD system; change the
 <tt>routed/gated</tt> startup parameters in <tt>/etc/netstart</tt> as
 appropriate for your system.  Please see the manual page for
diff --git a/share/doc/handbook/stable.sgml b/share/doc/handbook/stable.sgml
index 8e1eb530d04a..18acd26fd565 100644
--- a/share/doc/handbook/stable.sgml
+++ b/share/doc/handbook/stable.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: current.sgml,v 1.8 1996/01/31 14:26:01 mpp Exp $ -->
+<!-- $Id: stable.sgml,v 1.1 1996/02/11 00:16:17 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -10,7 +10,7 @@
 
                         THE FREEBSD STABLE POLICY 
 
-Last updated: $Date: 1996/01/31 14:26:01 $
+Last updated: $Date: 1996/02/11 00:16:17 $
 
 This document attempts to explain the rationale behind
 FreeBSD-stable, what you should expect should you decide to run it,
@@ -27,9 +27,9 @@ branch (see <ref id="current" name="FreeBSD-current">).
 
 <sect><heading>Who needs FreeBSD-stable?</heading>
 
-<p>If you're a commercial user or someone who puts maximum stability of
+<p>If you are a commercial user or someone who puts maximum stability of
 their FreeBSD system before all other concerns, you should consider tracking
-<em>stable</em>.  This is especially true if you've installed the most
+<em>stable</em>.  This is especially true if you have installed the most
 recent release (<htmlurl url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.0-RELEASE"
 name="2.1.0-RELEASE"> at the time of this writing) since the <em>stable</em>
 branch is effectively a bug-fix stream relative to the previous release.
@@ -53,8 +53,7 @@ next section).
     the users a chance to respond if they have any issues to raise concerning
     the proposed change.
 
-    To join this list, send mail to <htmlurl url="mailto:majordomo@FreeBSD.ORG"
-    name="majordomo@FreeBSD.ORG"> and say:
+    To join this list, send mail to &a.majordomo and say:
 <verb>
             subscribe freebsd-stable
 </verb>
@@ -73,7 +72,7 @@ next section).
         <item>  Use the CMU `sup' program (Software Update
 	     Protocol), also described below.
             This is the second most recommended method, since it allows 
-	    you to grab the entire collection once and then only what's
+	    you to grab the entire collection once and then only what has
             changed from then on.  Many people run sup from cron
             and keep their sources up-to-date automatically.
 
diff --git a/share/doc/handbook/submitters.sgml b/share/doc/handbook/submitters.sgml
index 15e1666e6fa1..6e9150aaaeac 100644
--- a/share/doc/handbook/submitters.sgml
+++ b/share/doc/handbook/submitters.sgml
@@ -1,17 +1,17 @@
-<!-- $Id: submitters.sgml,v 1.25 1996/05/09 23:04:50 mpp Exp $ -->
+<!-- $Id: submitters.sgml,v 1.26 1996/05/09 23:32:44 jkh Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
 
 <p><em>Contributed by &a.jkh;.</em>
 
-<p>So you want to contribute something to FreeBSD?  That's great!
+<p>So you want to contribute something to FreeBSD?  That is great!
 We can always use the help, and FreeBSD is one of those systems
 that <em>relies</em> on the contributions of its user base in order
-to survive.  Your contributions are not only appreciated, they're
+to survive.  Your contributions are not only appreciated, they are
 vital to FreeBSD's continued growth!
 
-<p>Contrary to what some people might also have you believe, you don't
+<p>Contrary to what some people might also have you believe, you do not
 need to be a hot-shot programmer or a close personal friend of the
 FreeBSD core team in order to have your contributions accepted.  The
 FreeBSD Project's development is done by a large and growing number of
@@ -24,28 +24,28 @@ system environment (and its installation) rather than just a kernel or
 a few scattered utilities, our "TODO" list also spans a very wide
 range of tasks, from documentation, beta testing and presentation to
 highly specialized types of kernel development.  No matter what your
-skill level, there's almost certainly something you can do to help the
+skill level, there is almost certainly something you can do to help the
 project!
 
 <p>Commercial entities engaged in FreeBSD-related enterprises are
 also encouraged to contact us.  Need a special extension to make your
-product work?  You'll find us receptive to your requests, given that
-they aren't too outlandish.  Working on a value-added product?  Please
+product work?  You will find us receptive to your requests, given that
+they are not too outlandish.  Working on a value-added product?  Please
 let us know!  We may be able to work cooperatively on some aspect of
 it.  The free software world is challenging a lot of existing
 assumptions about how software is developed, sold, and maintained
 throughout its life cycle, and we urge you to at least give it a
 second look.
 
-<sect><heading>What's needed</heading>
+<sect><heading>What is needed</heading>
 
 <p>The following list of tasks and sub-projects represents something
 of an amalgam of the various core team TODO lists and user requests
-we've collected over the last couple of months.  Where possible, tasks
-have been ranked by degree of urgency.  If you're interested in
+we have collected over the last couple of months.  Where possible, tasks
+have been ranked by degree of urgency.  If you are interested in
 working on one of the tasks you see here, send mail to the coordinator
 listed by clicking on their names.  If no coordinator has been
-appointed, maybe you'd like to volunteer?
+appointed, maybe you would like to volunteer?
 
 <sect1><heading>High priority tasks</heading>
 <p>The following tasks are considered to be urgent, usually because
@@ -133,7 +133,7 @@ your hardware, etc.
 
 <sect1><heading>Low priority tasks</heading>
 <p>The following tasks are purely cosmetic or represent such an
-investment of work that it's not likely that anyone will get them done
+investment of work that it is not likely that anyone will get them done
 anytime soon:
 
 <p>The first 20 items are from Terry Lambert &lt;terry@lambert.org&gt
@@ -198,7 +198,7 @@ as opportunity permits.  SCO and Solaris are good candidates,
 followed by UnixWare, etc.
 
 <item>Processor emulation environments for execution of foreign binaries.
-This is easier than it sounds if the system call interface doesn't
+This is easier than it sounds if the system call interface does not
 change much.
 
 <item>Streams to allow the use of commercial streams drivers.
@@ -220,7 +220,7 @@ PCMCIA).
 <item>Reorganization of the source tree for multiple platform ports.
 
 <item>A "make world" that "makes the world" (rename the current one
-to "make regress" if that's all it is good for).
+to "make regress" if that is all it is good for).
 
 <item>A 4M (preferably smaller!) memory footprint.
 
@@ -241,8 +241,7 @@ the following 6 categories:
 	  in such things (and a tolerance for a <em>high</em>
 	  volume of mail!) may
 	  subscribe to the hackers mailing list by sending mail to 
-          <tt><htmlurl url="mailto:majordomo@FreeBSD.ORG"
-	  name="&lt;majordomo@FreeBSD.ORG&gt;"></tt>.  
+          &a.majordomo;.
           See <ref id="eresources:mail" name="mailing lists">
 	  for more information about this and other mailing lists.
 
@@ -251,7 +250,7 @@ the following 6 categories:
 	  you for various fields to fill in.  Simply go to the fields
 	  surrounded by <tt>&lt;&gt;</tt>'s and fill in your own 
           information in place of
-	  what's suggested there.  You should receive confirmation of your
+	  what is suggested there.  You should receive confirmation of your
 	  bug report and a tracking number.  Keep this tracking number and use
 	  it in any subsequent correspondence.
           If you do not receive confirmation in a timely fashion (3 days to
@@ -307,8 +306,8 @@ diff -c -r olddir newdir
    likely get back in touch with you in 24 hours or less,
    assuming of course that your diffs are interesting! :-)
 
-   If your changes don't express themselves well as diffs alone
-   (e.g. you've perhaps added, deleted or renamed files as well)
+   If your changes do not express themselves well as diffs alone
+   (e.g. you have perhaps added, deleted or renamed files as well)
    then you may be better off bundling any new files, diffs and
    instructions for deleting/renaming others into a <tt>tar</tt>
    file and running the <tt>uuencode(1)</tt> program on it before
@@ -317,8 +316,8 @@ diff -c -r olddir newdir
    information on bundling files this way.
 
    If your change is of a potentially sensitive nature, e.g.
-   you're unsure of copyright issues governing its further distribution
-   or you're simply not ready to release it without a tighter review first,
+   you are unsure of copyright issues governing its further distribution
+   or you are simply not ready to release it without a tighter review first,
    then you should send it to <tt><htmlurl url="mailto:core@FreeBSD.ORG"
    name="&lt;core@FreeBSD.ORG&gt;"></tt> rather than the &a.hackers
    The core mailing list
@@ -348,7 +347,7 @@ diff -c -r olddir newdir
 	    who might eventually be inclined to invest something of their own
 	    into FreeBSD.
 
-	<item>The GNU Public License, or ``GPL''.  This license isn't quite
+	<item>The GNU Public License, or ``GPL''.  This license is not quite
 	    as popular with us due to the amount of extra effort demanded
 	    of anyone using the code for commercial purposes, but given
 	    the sheer quantity of GPL'd code we currently require (compiler,
@@ -400,7 +399,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.25 1996/05/09 23:04:50 mpp Exp $
+	$Id: submitters.sgml,v 1.26 1996/05/09 23:32:44 jkh Exp $
 </verb></tscreen>
 For your convenience, a copy of this text can be found in
 <tt>/usr/share/examples/etc/bsd-style-copyright</tt>.
@@ -408,7 +407,7 @@ For your convenience, a copy of this text can be found in
         &porting;
 
 <sect1><heading>Money, Hardware or Internet access</heading>
-<p>We're always very happy to accept donations to further the cause of
+<p>We are always very happy to accept donations to further the cause of
 the FreeBSD Project and, in a volunteer effort like ours, a little can go
 a long way!  Donations of hardware are also very important to expanding
 our list of supported peripherals since we generally lack the funds to
@@ -464,20 +463,20 @@ systems should be sent to the FreeBSD, Inc. address listed in the
 We are currently trying to put together a testing lab of all components
 that FreeBSD supports so that proper regression testing can be done with
 each new release. We are still lacking many important pieces (network cards,
-motherboards, etc) and if you'd like to make such a donation, please contact
+motherboards, etc) and if you would like to make such a donation, please contact
 &a.davidg for information on which items are still required.
 
-<item>Hardware currently unsupported by FreeBSD for which you'd like to
+<item>Hardware currently unsupported by FreeBSD for which you would like to
 see such support added.  Please contact the <htmlurl
 url="mailto:core@FreeBSD.ORG" name="FreeBSD Core Team"> before sending
-such items as we'll need to find a developer willing to take on the task
+such items as we will need to find a developer willing to take on the task
 before we can accept delivery of them.  
 </itemize>
 
 <sect2><heading>Donating Internet access</heading>
 
 <p>We can always use new mirror sites for FTP, WWW or sup.
-If you'd like to be such a mirror, please contact
+If you would like to be such a mirror, please contact
 <htmlurl url="mailto:admin@FreeBSD.ORG" name="the FreeBSD project
 administrators"> for more information.
 
@@ -502,7 +501,7 @@ like to publically thank them here!
 	<item><htmlurl url="http://www.cdrom.com" name="Walnut Creek CDROM">
 	has donated almost more than we can say (see the
 	<ref id="history" name="history"> document for more details).
-	In particular, we'd like to thank them for the hardware used for
+	In particular, we would like to thank them for the hardware used for
 	<em>freefall.FreeBSD.ORG</em>, our primary development machine,
 	and for <em>thud.FreeBSD.ORG</em>, our testing and build box.
 	We are also indebted to them for funding various contributors over
diff --git a/share/doc/handbook/sup.sgml b/share/doc/handbook/sup.sgml
index 48ac680f63b3..4b3ce9569209 100644
--- a/share/doc/handbook/sup.sgml
+++ b/share/doc/handbook/sup.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: sup.sgml,v 1.13 1996/02/11 00:16:18 jkh Exp $ -->
+<!-- $Id: sup.sgml,v 1.14 1996/05/09 23:04:53 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 
@@ -28,9 +28,9 @@ track changes to the -stable release, refer to
 <tt>/usr/share/examples/sup/stable-supfile</tt>
 instead.
 
-If you're inside the United States, you may also uncomment
+If you are inside the United States, you may also uncomment
 the `secure' and `eBones' collection lines to grab the DES code.  
-If you're outside the
+If you are outside the
 U.S., you should NOT sup this code from sup.FreeBSD.ORG as this will
 violate U.S. export restrictions.  Instead you should use the 
 <tt>secure-supfile</tt> found within the above directory.  This will
@@ -45,7 +45,7 @@ listed in the above example files is currently overloaded and any traffic
 that can be transfered to a different host will help relieve some of 
 the strain.
 
-Once this is setup, you're ready to go.  To start sup type:
+Once this is setup, you are ready to go.  To start sup type:
 <verb>
 	sup supfile
 </verb>
@@ -54,7 +54,7 @@ like so:
 <verb>
 	sup -v supfile
 </verb>
-Thats all there is to it!  Remember that if you're running current,
+Thats all there is to it!  Remember that if you are running current,
 which is what you will have if you sup with the standard-supfile, please 
 join the &a.current mailing list.  You should also be sure to read 
 <ref id="current" name="Staying current with FreeBSD">
@@ -125,7 +125,7 @@ ports-x11:	  /usr/ports/x11	X11 software
 <p>If you want to keep updated on the original source of the ports,
 you can also add this to your supfile.  But note that this collection
 is <em>enormous</em>, and unless you are an ftp site mirroring the
-entire FreeBSD tree (but can't use ``mirror'' for some reason), you
+entire FreeBSD tree (but cannot use ``mirror'' for some reason), you
 (and us) are much better off not using sup to collect these:
 <verb>
 ports-distfiles: /usr/ports/distfiles	original tarballs
diff --git a/share/doc/handbook/troubleshooting.sgml b/share/doc/handbook/troubleshooting.sgml
index 07efb816fbfd..788beef25575 100644
--- a/share/doc/handbook/troubleshooting.sgml
+++ b/share/doc/handbook/troubleshooting.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: troubleshooting.sgml,v 1.2 1995/06/30 17:37:53 jfieber Exp $ -->
+<!-- $Id: troubleshooting.sgml,v 1.3 1995/07/07 22:25:55 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Troubleshooting<label id="troubleshooting"></heading>
@@ -13,16 +13,16 @@
 
       <p><descrip>
 	  <tag>Problem:</tag> A device is conflicting with
-	another or doesn't match the kernel's compiled-in IRQ or
+	another or does not match the kernel's compiled-in IRQ or
 	address.
 
 	  <tag>Cause:</tag> While most device drivers in
 	FreeBSD are now smart enough to match themselves to your
 	hardware settings dynamically, there are a few that still
 	require fairly rigid configuration parameters to be
-	compiled in (and matched by the hardware) before they'll
-	work.  We're working hard to eliminate as many of these
-	last hold-outs as we can, but it's not always as easy as
+	compiled in (and matched by the hardware) before they will
+	work.  We are working hard to eliminate as many of these
+	last hold-outs as we can, but it is not always as easy as
 	it looks.
 
 	<tag>Solution:</tag> There are several possible
@@ -40,16 +40,16 @@
 	You can use this utility to reset the IRQ, memory
 	address, IO address or a number of other device
 	configuration parameters.  You can also disable a device
-	entirely if it's causing problems for other devices you'd
+	entirely if it is causing problems for other devices you would
 	much rather have work.
 
 	Another solution is, obviously, to remove the offending
 	hardware or simply strip the system down to the bare
 	essentials until the problem (hopefully) goes away.  Once
-	you're up, you can do the same thing mentioned
+	you are up, you can do the same thing mentioned
 	above---compile a kernel more suited to your hardware, or
 	incrementally try to figure out what it was about your
-	original hardware configuration that didn't work.
+	original hardware configuration that did not work.
 
 	</descrip>
 
@@ -62,8 +62,8 @@
 
 	Solution: You should re-enter the installation process,
 	invoke the (F)disk editor and chose the (W)rite option.
-	This won't hurt an existing installation and will make
+	This will not hurt an existing installation and will make
 	sure that the new boot blocks get written to the drive.
-	If you're installing for the first time, don't forget to
+	If you are installing for the first time, do not forget to
 	(W)rite out your new boot blocks! :-)
 
diff --git a/share/doc/handbook/userppp.sgml b/share/doc/handbook/userppp.sgml
index 69f92342c3c8..2cecb4912d80 100644
--- a/share/doc/handbook/userppp.sgml
+++ b/share/doc/handbook/userppp.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: userppp.sgml,v 1.5 1995/12/06 22:01:50 jfieber Exp $ -->
+<!-- $Id: userppp.sgml,v 1.6 1996/01/31 14:26:20 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect>Setting up user PPP<label id="userppp">
@@ -11,11 +11,11 @@
   (and above).
 
   I hope this document turns into a collaborative effort, largely
-  because I am not really much of an authority on PPP. I've got
+  because I am not really much of an authority on PPP. I have got
   it working, and want to pass on details of what I did so that
-  other people can get it working. But I'm not 100% clear on some
+  other people can get it working. But I am not 100% clear on some
   details, so I hope that by writing this and having others
-  flesh out some of the information I'm going to learn something
+  flesh out some of the information I am going to learn something
   as well.
 -->
 
@@ -27,7 +27,7 @@
 <quote>
        This is a user process PPP software package. Normally, PPP is
        implemented as a part of the kernel (e.g. as managed by pppd) and
-       it's thus somewhat hard to debug and/or modify its behavior. However,
+       it is thus somewhat hard to debug and/or modify its behavior. However,
        in this implementation PPP is done as a user process with the help of
        the tunnel device driver (tun).
 </quote>
@@ -50,7 +50,7 @@
 
 <sect1><heading>Before you start</heading>
 
-<p>This document assumes you're in roughly this position:
+<p>This document assumes you are in roughly this position:
 
     You have an account with an Internet Service Provider (ISP) which lets you
     use PPP. Further, you have a modem (or other device) connected and
@@ -77,7 +77,7 @@
   your kernel. Check <ref id="kernelconfig" name="Kernel
   Configuration"> for more information on how to acquire these.
 
-  In addition, I've assumed that because your connection to the Internet is  
+  In addition, I have assumed that because your connection to the Internet is  
   not full time you are not running a name server (<tt>named(8)</tt>).
 
 <sect1><heading>Building a ppp ready kernel</heading>
@@ -92,7 +92,7 @@
 pseudo-device	  tun		1
 </verb></tscreen>
   in it somewhere. The stock GENERIC kernel has this as standard, so if you
-  have not installed a custom kernel you don't have to change anything.
+  have not installed a custom kernel you do not have to change anything.
   If your kernel configuration file does not have this line in it then you
   should add the line, re-compile and then re-install the kernel. Boot from
   this new kernel.
@@ -159,7 +159,7 @@ bind
      and then to consult the DNS if the name was not found in the
      <tt>/etc/hosts</tt> file.
 
-     It's probably a good idea to make sure you are not running the ``named''
+     It is probably a good idea to make sure you are not running the ``named''
      service. Check your <tt>/etc/sysconfig</tt> file for the line that refers
      to ``namedflags'', and make sure the line reads
 <tscreen><verb>
@@ -170,7 +170,7 @@ namedflags="NO"
 
 <p>This file should contain the IP addresses and names of machines on your
      network. At a bare minimum it should contain entries for the machine
-     which will be running ppp. Assuming that you're machine is called
+     which will be running ppp. Assuming that your machine is called
      foo.bar.com with the IP address 10.0.0.1, <tt>/etc/hosts</tt> should
      contain:
 <tscreen><verb>
@@ -228,7 +228,7 @@ nameserver 158.152.1.65
 10       set timeout 120
 11       set ifaddr x.x.x.x y.y.y.y
 </verb></tscreen>
-    Don't include the line numbers, they're just for this discussion.
+    Do not include the line numbers, they are just for this discussion.
 
 <descrip>
 <tag/Line 1:/ Identifies the default entry. Commands in this entry are
@@ -239,7 +239,7 @@ nameserver 158.152.1.65
 
 <tag/Line 3:/ Sets the speed you want to connect at.
 
-<tag/* Lines 4 and 5:/ Don't know exactly what effect these lines have
+<tag/* Lines 4 and 5:/ Do not know exactly what effect these lines have
 
 <tag/Line 6:/ Dial string commands. user ppp uses the <tt>chat(8)</tt>
               language. Check the manual page for information on the features
@@ -247,10 +247,10 @@ nameserver 158.152.1.65
 
 <tag/Line 7:/ Identifies an entry for a provider called ``provider''.
 
-<tag/Line 8:/ Sets the phone number for this provider. Don't include any
+<tag/Line 8:/ Sets the phone number for this provider. Do not include any
               spaces in the phone number.
 
-<tag/Line 9:/ Set's the login string sequence. In this example, the string is
+<tag/Line 9:/ Sets the login string sequence. In this example, the string is
 	      for a service who's login session looks like
 <tscreen><verb>
 J. Random Provider
@@ -298,8 +298,8 @@ set ifaddr 0 0
 
 <sect1><heading>Final system configuration</heading>
 
-<p>You now have PPP configured, but there's a few more things to do before
-    it's ready to work. They all involve editing the <tt>/etc/sysconfig</tt>
+<p>You now have PPP configured, but there are a few more things to do before
+    it is ready to work. They all involve editing the <tt>/etc/sysconfig</tt>
     file.
 
     Working from the top down in this file, make sure the ``hostname='' line
@@ -330,7 +330,7 @@ ifconfig_tun0="inet foo.bar.com y.y.y.y netmask 0xffffffff"
 <tscreen><verb>
 routedflags=-s
 </verb></tscreen>
-    It's probably worth your while ensuring that the ``sendmail_flags'' line
+    It is probably worth your while ensuring that the ``sendmail_flags'' line
     does not include the ``-q'' option, otherwise sendmail will attempt to do
     a network lookup every now and then, possibly causing your machine to dial
     out. My sendmail line looks like
@@ -343,7 +343,7 @@ sendmail_flags="-bd"
 # /usr/sbin/sendmail -q
 </verb></tscreen>
     That should be about all you need to do to get PPP working with a static
-    IP address. All that's left is to reboot the machine. During startup the
+    IP address. All that is left is to reboot the machine. During startup the
     tun0 device should be detected, and two lines like the following should be
     printed,
 <tscreen><verb>