Run a few chapters through aspell.

svn path=/head/; revision=15330

en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml

@@ -316,7 +316,7 @@ subscribe cvs-all</programlisting>
 	      linkend="makeworld">make world</link> the first time through
 	      as part of the upgrading process.  Reading the &a.current;
 	      will keep you up-to-date on other bootstrapping procedures
-	      that sometimes become necessary as we move towards the next
+	      that sometimes become necessary as we move toward the next
 	      release.</para>
 	  </listitem>
 	      
@@ -523,7 +523,7 @@ subscribe cvs-all</programlisting>
 	    linkend="makeworld">make world</link> the first time through
 	    as part of the upgrading process.  Reading the &a.stable; will
 	    keep you up-to-date on other bootstrapping procedures that
-	    sometimes become necessary as we move towards the next
+	    sometimes become necessary as we move toward the next
 	    release.</para>
 	  </listitem>
 	</orderedlist>
@@ -639,7 +639,7 @@ subscribe cvs-all</programlisting>
       <para>Sometimes these mistakes can be quite harmless, just causing
 	your system to print a new diagnostic warning.  Or the change may
 	be catastrophic, and render your system unbootable or destroy your
-	filesystems (or worse).</para>
+	file systems (or worse).</para>
 
       <para>If problems like these occur, a <quote>heads up</quote> is
         posted to the appropriate mailing list, explaining the nature of
@@ -791,8 +791,8 @@ subscribe cvs-all</programlisting>
 &prompt.root; <userinput>mount -a -t ufs</userinput>
 &prompt.root; <userinput>swapon -a</userinput></screen>
 
-      <para>This checks the filesystems, remounts <filename>/</filename>
-	read/write, mounts all the other UFS filesystems referenced in
+      <para>This checks the file systems, remounts <filename>/</filename>
+	read/write, mounts all the other UFS file systems referenced in
 	<filename>/etc/fstab</filename> and then turns swapping on.</para>
 
 
@@ -1420,7 +1420,7 @@ Script done, &hellip;</screen>
 	<filename>/stand</filename> as well.  These files consist of hard
 	links to the <filename>/stand/sysinstall</filename> binary.  This
 	binary should be statically linked, so that it can work when no other
-	filesystems (and in particular <filename>/usr</filename>) have been
+	file systems (and in particular <filename>/usr</filename>) have been
 	mounted.</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src/release/sysinstall</userinput>
@@ -1542,7 +1542,7 @@ Script done, &hellip;</screen>
 	      problems can creep in, causing your build to fail in odd ways.
 	      This frequently generates noise on the &os; mailing lists,
 	      when one person complains that their build has failed, not
-	      realising that it is because they have tried to cut
+	      realizing that it is because they have tried to cut
 	      corners.</para>
 	  </answer>
 	</qandaentry>
@@ -1606,12 +1606,12 @@ Building everything..
 	      <listitem>
 		<para>Put the <filename>/usr/src</filename> and
 		  <filename>/usr/obj</filename> directories on separate
-		  filesystems held on separate disks.  If possible, put these
+		  file systems held on separate disks.  If possible, put these
 		  disks on separate disk controllers.</para>
 	      </listitem>
 	      
 	      <listitem>
-		<para>Better still, put these filesystems across multiple
+		<para>Better still, put these file systems across multiple
 		  disks using the &man.ccd.4; (concatenated disk
 		  driver) device.</para>
 	      </listitem>
@@ -1640,26 +1640,26 @@ Building everything..
 		  machine.</para>
 	      </listitem>
 	      
-	      <listitem><para>The filesystem holding
+	      <listitem><para>The file system holding
 		  <filename>/usr/src</filename> can be mounted (or remounted)
 		  with the <option>noatime</option> option.  This prevents the
-		  filesystem from recording the file access time.  You probably
+		  file system from recording the file access time.  You probably
 		  do not need this information anyway.
 		  
 		  <screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen>
 		  
 		  <warning>
 		    <para>The example assumes <filename>/usr/src</filename> is
-		      on its own filesystem.  If it is not (if it is a part of
+		      on its own file system.  If it is not (if it is a part of
 		      <filename>/usr</filename> for example) then you will
-		      need to use that filesystem mount point, and not
+		      need to use that file system mount point, and not
 		      <filename>/usr/src</filename>.</para>
 		  </warning>
 		</para>
 	      </listitem>
 	      
 	      <listitem>
-		<para>The filesystem holding <filename>/usr/obj</filename> can
+		<para>The file system holding <filename>/usr/obj</filename> can
 		  be mounted (or remounted) with the <quote>async</quote>
 		  option.  This causes disk writes to happen asynchronously.
 		  In other words, the write completes immediately, and the
@@ -1668,14 +1668,14 @@ Building everything..
 		  dramatic performance boost.</para>
 
 		<warning>
-		  <para>Keep in mind that this option makes your filesystem
+		  <para>Keep in mind that this option makes your file system
 		    more fragile.  With this option there is an increased
-		    chance that, should power fail, the filesystem will be in
+		    chance that, should power fail, the file system will be in
 		    an unrecoverable state when the machine restarts.</para>
 	   
 		  <para>If <filename>/usr/obj</filename> is the only thing on
-		    this filesystem then it is not a problem.  If you have
-		    other, valuable data on the same filesystem then ensure
+		    this file system then it is not a problem.  If you have
+		    other, valuable data on the same file system then ensure
 		    your backups are fresh before you enable this
 		    option.</para>
 		</warning>
@@ -1684,7 +1684,7 @@ Building everything..
 		
 		<warning>
 		  <para>As above, if <filename>/usr/obj</filename> is not on
-		    its own filesystem, replace it in the example with the
+		    its own file system, replace it in the example with the
 		    name of the appropriate mount point.</para>
 		</warning>
 	      </listitem>

en_US.ISO8859-1/books/handbook/desktop/chapter.sgml

@@ -928,7 +928,7 @@
   <sect1 id="desktop-summary">
     <title>Summary</title>
 
-    <para>While FreeBSD is popular amongst ISPs for its performance and
+    <para>While FreeBSD is popular among ISPs for its performance and
       stability, it is quite ready for day-to-day use as a desktop.
       With several thousand applications available as
       <ulink url="http://www.freebsd.org/where.html">packages</ulink> or

en_US.ISO8859-1/books/handbook/disks/chapter.sgml

@@ -1776,7 +1776,7 @@ sa0(ncr1:4:0):  Logical unit is in process of becoming ready</screen>
       <para>&man.dump.8; <emphasis>Period.</emphasis> Elizabeth D. Zwicky
 	torture tested all the backup programs discussed here.  The clear
 	choice for preserving all your data and all the peculiarities of Unix
-	file systems is <command>dump</command>.  Elizabeth created filesystems containing
+	file systems is <command>dump</command>.  Elizabeth created file systems containing
 	a large variety of unusual conditions (and some not so unusual ones)
 	and tested each program by doing a backup and restore of those
 	file systems.  The peculiarities included: files with holes, files with

en_US.ISO8859-1/books/handbook/introduction/chapter.sgml

@@ -514,7 +514,7 @@
 	objectives were set after consulting with the system's current
 	users and, once it became clear that the project was on the road
 	to perhaps even becoming a reality, I contacted Walnut Creek CDROM
-	with an eye towards improving FreeBSD's distribution channels for
+	with an eye toward improving FreeBSD's distribution channels for
 	those many unfortunates without easy access to the Internet.
 	Walnut Creek CDROM not only supported the idea of distributing
 	FreeBSD on CD but also went so far as to provide the project with a