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

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

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

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

1 files changed, 13 insertions, 13 deletions

diff --git a/share/doc/handbook/kernelopts.sgml b/share/doc/handbook/kernelopts.sgml
index 88faf63..2255082 100644
--- a/share/doc/handbook/kernelopts.sgml
+++ b/share/doc/handbook/kernelopts.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kernelopts.sgml,v 1.1 1996/12/23 12:20:04 joerg Exp $ -->
+<!-- $Id: kernelopts.sgml,v 1.2 1996/12/26 22:08:11 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
 
@@ -20,7 +20,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   after running <tt/config(8)/, the build process will automatically
   pick up modified options, and only recompile those files where it is
   necessary.  Wiping out the old compile directory on each run of
-  <tt/config(8)/ as it's still done now can then be eliminated again.
+  <tt/config(8)/ as it is still done now can then be eliminated again.
 
   <p>Basically, a kernel option is nothing else than the definition of
   a C preprocessor macro for the kernel compilation process.  To make
@@ -41,7 +41,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   must be a valid C expression in whatever context the default value
   would have been used.
 
-  <p>It's also possible to create value-less options that simply
+  <p>It is also possible to create value-less options that simply
   enable or disable a particular piece of code by embracing it in
 
 <verb>
@@ -57,7 +57,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
 
   <p>People familiar with the C language will immediately recognize
   that everything could be counted as a ``config option'' where
-  there's at least a single <tt/#ifdef/ referencing it...  Now only
+  there is at least a single <tt/#ifdef/ referencing it...  Now only
   few people probably would try to say
 
 <verb>
@@ -67,7 +67,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   fall over. :-)
 
   <p>Apparently, using arbitrary names for the options makes it very
-  hard to track their usage throughout the kernel source tree.  That's
+  hard to track their usage throughout the kernel source tree.  That is
   the rationale behind the <em/new-style/ option scheme, where each
   option goes into a separate <tt/.h/ file in the kernel compile
   directory, which is by convention named <tt>opt_<em>foo</em>.h</tt>.
@@ -77,9 +77,9 @@ id="kernelconfig" name="kernel configuration"> before reading here.
 
   <p>The old-style option mechanism still has one advantage for local
   options or maybe experimental options that have a short anticipated
-  lifetime: since it's easy to add a new <tt/#ifdef/ to the kernel
-  source, this already made it a kernel config option, so that's
-  already all about it.  In this case, the administrator using such an
+  lifetime: since it is easy to add a new <tt/#ifdef/ to the kernel
+  source, this has already made it a kernel config option.
+  In this case, the administrator using such an
   option is responsible himself for knowing about its implications
   (and maybe manually forcing the recompilation of parts of his
   kernel).  Once the transition of all supported options has been
@@ -96,7 +96,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   <tt>opt_<em>foo</em>.h</tt> file where your new option would best go
   into.
 
-  <p>If there's already something that comes close to the purpose of
+  <p>If there is already something that comes close to the purpose of
   the new option, pick this.  For example, options modifying the
   overall behaviour of the SCSI subsystem can go into <tt/opt_scsi.h/.
   By default, simply mentioning an option in the appropriate option
@@ -104,7 +104,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   corresponding file <tt/opt_foo.h/.  This can be overridden on the
   right-hand side of a rule by specifying another filename.
 
-  <p>If there's no <tt>opt_<em>foo</em>.h</tt> already available for
+  <p>If there is no <tt>opt_<em>foo</em>.h</tt> already available for
   the intended new option, invent a new name.  Make it meaningful, and
   comment the new section in the
   <tt>options[<em>.&lt;arch&gt;</em>]</tt> file.  <tt/config(8)/ will
@@ -116,7 +116,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   rebuilt when one of the options has been changed in the config file.
 
   <p>Finally, find out which kernel files depend on the new option.
-  Unless you've just invented your option, so it doesn't exist
+  Unless you have just invented your option, and it dos not exist
   anywhere yet,
 
 <verb>
@@ -144,6 +144,6 @@ id="kernelconfig" name="kernel configuration"> before reading here.
   (i. e., a file sitting in <tt>/usr/include/sys/</tt>) is almost
   always a mistake.  <tt>opt_<em>foo</em>.h</tt> cannot be included
   into those files since it would break the headers more seriously,
-  but if it isn't included, then places that include it may get an
+  but if it is not included, then places that include it may get an
   inconsistent value for the option.  Yes, there are precedents for
-  this right now, but that doesn't make them more correct.
+  this right now, but that does not make them more correct.