Fix some grammar problems (mainly its/it's stuff).

8 files changed, 37 insertions, 37 deletions

diff --git a/share/doc/handbook/booting.sgml b/share/doc/handbook/booting.sgml
index 9c36d59..8c258c3 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.8 1995/10/22 00:41:56 jfieber Exp $
+     $Id: booting.sgml,v 1.9 1996/01/31 14:25:57 mpp Exp $
 
 
 <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
@@ -57,7 +57,7 @@
           Dosboot will boot the kernel from a MS-DOS file or from a FreeBSD
           filesystem partition on the disk.  It attempts to negotiate with
           the various and strange kinds of memory manglers that lurk in
-          high memory on MS/DOS systems and usually wins them for it's
+          high memory on MS/DOS systems and usually wins them for its
           case.
 
       <tag>Netboot</tag>
diff --git a/share/doc/handbook/esdi.sgml b/share/doc/handbook/esdi.sgml
index 0950003..5d784df 100644
--- a/share/doc/handbook/esdi.sgml
+++ b/share/doc/handbook/esdi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: esdi.sgml,v 1.4 1995/12/04 17:58:38 jfieber Exp $ -->
+<!-- $Id: esdi.sgml,v 1.5 1996/01/31 14:26:05 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -59,7 +59,7 @@
 
 	The second cable is a a 20 pin flat cable edge connector that
 	carries the data to and from the drive. This cable is radially
-	connected, so each drive has it's own direct connection to the
+	connected, so each drive has its own direct connection to the
 	controller.
 
 	To the best of my knowledge PC ESDI controllers are limited
@@ -76,7 +76,7 @@
 
 	On PC type controllers the first drive is set to address 0, 
 	the second disk to address 1. <it>Always make sure</it> you
-	set each disk to an unique address! So, on a PC with it's
+	set each disk to an unique address! So, on a PC with its
 	two drives/controller maximum the first drive is drive 0, the
 	second is drive 1.
 
@@ -90,7 +90,7 @@
 
 	So, one and <it>only</it> one drive, the one at 
 	the farthest end of the command
-	cable has it's terminator installed/enabled. The controller
+	cable has its terminator installed/enabled. The controller
 	automatically terminates the other end of the cable. 
 	Please note that this implies that the controller must be 
 	at one end of the cable and <it>not</it> in the middle.
@@ -219,8 +219,8 @@
 	The result is that the number of cylinders is reduced to
 	something below 1024 and is therefore usable by the system
 	without problems.
-	It is noteworthy to know that FreeBSD after it's kernel has
-	started no longer uses the BIOS. More on this later.
+	It is noteworthy to know that FreeBSD does not use the
+	BIOS after its kernel has started.  More on this later.
 
 	A second reason for translations is the fact that most
 	older system BIOSes could only handle drives with 17 sectors
diff --git a/share/doc/handbook/firewalls.sgml b/share/doc/handbook/firewalls.sgml
index 4436edd..91f5115 100644
--- a/share/doc/handbook/firewalls.sgml
+++ b/share/doc/handbook/firewalls.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: firewalls.sgml,v 1.2 1995/11/01 00:42:17 gpalmer Exp $ -->
+<!-- $Id: firewalls.sgml,v 1.3 1996/01/31 14:26:06 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Firewalls<label id="firewalls"></heading>
@@ -47,7 +47,7 @@ impossible to cover them in this document.
 <sect2><heading>Packet filtering routers<label id="firewalls:packet_filters"></heading>
 
 <p>A router is a machine which forwards packets between two or more
-networks. A packet filtering router has an extra piece of code in it's
+networks. A packet filtering router has an extra piece of code in its
 kernel, which compares each packet to a list of rules before deciding
 if it should be forwarded or not. Most modern IP routing software has
 packet filtering code in it, which defaults to forwarding all
@@ -56,7 +56,7 @@ the filtering code, so that it can decide if the packet should be
 allowed to pass or not.
 
 <p>To decide if a packet should be passed on or not, the code looks
-through it's set of rules for a rule which matches the contents of
+through its set of rules for a rule which matches the contents of
 this packets headers. Once a match is found, the rule action is
 obeyed.  The rule action could be to drop the packet, to forward the
 packet, or even to send an ICMP message back to the originator.  Only
@@ -146,7 +146,7 @@ will happen.
 <p>The configuration of the <tt>IPFW</tt> software is done through the
 <tt>ipfw(8)</tt> utility. The syntax for this command looks
 quite complicated, but it is relatively simple once you understand
-it's structure.
+its structure.
 
 <p>There are currently two different command line formats for the
 utility, depending on what you are doing. The first form is used when
diff --git a/share/doc/handbook/install.sgml b/share/doc/handbook/install.sgml
index e4ba3dc..3d0bf25 100644
--- a/share/doc/handbook/install.sgml
+++ b/share/doc/handbook/install.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: install.sgml,v 1.21 1995/12/21 16:10:22 jfieber Exp $ -->
+<!-- $Id: install.sgml,v 1.22 1996/01/31 14:26:09 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -405,11 +405,11 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent
 	  floppies for the install.
 
 
-	  The first floppy you'll 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'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"
+	  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'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
diff --git a/share/doc/handbook/kerneldebug.sgml b/share/doc/handbook/kerneldebug.sgml
index 24744b8..ba3538e 100644
--- a/share/doc/handbook/kerneldebug.sgml
+++ b/share/doc/handbook/kerneldebug.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kerneldebug.sgml,v 1.6 1996/01/03 11:10:30 gclarkii Exp $ -->
+<!-- $Id: kerneldebug.sgml,v 1.7 1996/01/31 14:26:11 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
@@ -73,7 +73,7 @@
   Here's 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 of this, it's a real-world error
+  numbered for reference.  Despite this, it's 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
diff --git a/share/doc/handbook/memoryuse.sgml b/share/doc/handbook/memoryuse.sgml
index 79932a5..2cec37d 100644
--- a/share/doc/handbook/memoryuse.sgml
+++ b/share/doc/handbook/memoryuse.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: memoryuse.sgml,v 1.4 1995/10/22 00:42:13 jfieber Exp $ -->
+<!-- $Id: memoryuse.sgml,v 1.5 1995/12/19 10:21:07 gclarkii Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>PC memory utilization<label id="memoryuse"></heading>
@@ -30,7 +30,7 @@ The boot code itself uses segment selectors <tt>0x18</tt> and <tt>0x20</tt> for
 kernel is finally started with <tt>%cs</tt> <tt>0x08</tt> and <tt>%ds/%es/%ss</tt> <tt>0x10</tt>, which
 refer to dummy descriptors covering the entire address space.
 
-The kernel will be started at its load point.  Since it's been linked
+The kernel will be started at its load point.  Since it has been linked
 for another (high) address, it will have to execute PIC until the page
 table and page directory stuff is setup properly, at which point
 paging will be enabled and the kernel will finally run at the address
diff --git a/share/doc/handbook/printing.sgml b/share/doc/handbook/printing.sgml
index ba113c2..1aa5955 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.3 1995/12/04 17:58:47 jfieber Exp $
+     $Id: printing.sgml,v 1.4 1996/01/31 14:26:14 mpp Exp $
 
      The FreeBSD Documentation Project
 
@@ -207,7 +207,7 @@
 	    Your users may be appreciative of such information.
 	    Furthermore, the best way to do effective accounting with
 	    a PostScript printer requires two-way communication: you
-	    ask the printer for its page count (how many pages it's
+	    ask the printer for its page count (how many pages it has
 	    printed in its lifetime), then send the user's job, then
 	    ask again for its page count. Subtract the two values and
 	    you know how much paper to charge the user.
@@ -2557,7 +2557,7 @@ exit 0
 
 	      Rather than install conversion filters at all, you might
 	      want to try having the text filter (since it's the
-	      default filter) detect the type of file it's asked to
+	      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
@@ -2668,7 +2668,7 @@ exit 0
       <sect1><heading>Header Pages<label
 	    id="printing:advanced:header-pages"></heading>
 
-	<p> If you've got <em/lots/ of users, all of them using
+	<p> If you have <em/lots/ of users, all of them using
 	  various printers, then you probably want to consider
 	  <em/header pages/ as a necessary evil.
 
@@ -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've got a PostScript printer, you'll need an
+	  text.  If you have a PostScript printer, you'll need an
 	  external program to generate the header page; see <ref
 	  id="printing:advanced:header-pages:ps" name="Header Pages on
 	  PostScript Printers">.
@@ -2803,7 +2803,7 @@ r         oooo     ssss     eeee
 					Date: Sun Sep 17 11:04:58 1995
 </verb></tscreen>
 	    LPD appends a form feed after this text so the job starts
-	    on a new page (unless you've got <tt/sf/ (suppress form
+	    on a new page (unless you have <tt/sf/ (suppress form
 	    feeds) in the destination printer's entry in
 	    <tt>/etc/printcap</tt>).
 
@@ -3047,7 +3047,7 @@ done
 	    the appropriate header page PostScript code to the
 	    printer.
 
-	    If you've got a PostScript printer on a serial line, you
+	    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.
diff --git a/share/doc/handbook/scsi.sgml b/share/doc/handbook/scsi.sgml
index 7923747..c9982d6 100644
--- a/share/doc/handbook/scsi.sgml
+++ b/share/doc/handbook/scsi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: scsi.sgml,v 1.10 1995/12/04 17:58:50 jfieber Exp $ -->
+<!-- $Id: scsi.sgml,v 1.11 1996/01/31 14:26:17 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -196,7 +196,7 @@
             A differential SCSI bus has a maximum length of 25
             meters. Quite a difference from the 3 meters for a single-ended
             fast-SCSI bus. The idea behind differential signals is that
-            each bus signal has it's own return wire. So, each signal is
+            each bus signal has its own return wire. So, each signal is
             carried on a (preferably twisted) pair of wires. The voltage
             difference between these two wires determines whether the
             signal is asserted or de-asserted. To a certain extent the
@@ -284,7 +284,7 @@
             operate properly.  On the SCSI bus, a line is dedicated to this
             purpose.  So, simple huh?
 
-            Not so. Each device can provide it's own terminator power to
+            Not so. Each device can provide its own terminator power to
             the terminator sockets it has on-device. But if you have
             external terminators, or when the device supplying the
             terminator power to the SCSI bus line is switched off you are
@@ -359,7 +359,7 @@
             You might notice that the terminator issue discussed earlier
             becomes rather hairy if your bus is not linear..
 
-            The electrical characteristics, it's noise margins and
+            The electrical characteristics, its noise margins and
             ultimately the reliability of it all are tightly related to
             linear bus rule.
 
@@ -374,7 +374,7 @@
 
           When you want to use a SCSI disk on your PC as boot disk, you
           must aware of some quirks related to PC BIOSes. The PC BIOS in
-          it's first incarnation used a low level physical interface to the
+          its first incarnation used a low level physical interface to the
           hard disk. So, you had to tell the BIOS (using a setup tool or a
           BIOS built-in setup) how your disk physically looked like. This
           involved stating number of heads, number of cylinders, number of
@@ -388,7 +388,7 @@
 	  FreeBSD kernel during boot.
 
           The SCSI host adapter or SCSI controller you have put in your
-          AT/EISA/PCI/whatever bus to connect your disk therefore has it's
+          AT/EISA/PCI/whatever bus to connect your disk therefore has its
           own on-board BIOS. During system startup, the SCSI BIOS takes over
           the hard disk interface routines from the system BIOS. To fool the
           system BIOS, the system setup is normally set to No hard disk
@@ -464,7 +464,7 @@
           controller card a device driver is written. This driver
           knows all the intimate details about the hardware it
           controls. The driver has a interface to the upper layers of the
-          SCSI subsystem through which it receives it's commands and
+          SCSI subsystem through which it receives its commands and
           reports back any status.
 
           On top of the card drivers there are a number of more generic
@@ -557,7 +557,7 @@ device cd0 at scbus?			[the first ever CDROM found, no wiring]
 	  is reserved for that device, even if it is turned off at boot
 	  time. This allows the device to be turned on and brought
 	  on-line at a later time, without rebooting. Notice that a device's
-	  unit number has <em>no</em> relationship with it's target ID on 
+	  unit number has <em>no</em> relationship with its target ID on 
 	  the SCSI bus.
 
 	  Below is another example of a kernel config file as used by