Note that device.hints(5) is a FreeBSD 5.0 feature

Use 'file system' over 'filesystem'

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

@@ -108,7 +108,7 @@
       process is finished, the kernel passes control to the user process
       &man.init.8;, which then makes sure the disks are in a usable state.
       &man.init.8; then starts the user-level resource configuration which
-      mounts filesystems, sets up network cards to communicate on the
+      mounts file systems, sets up network cards to communicate on the
       network, and generally starts all the processes that usually
       are run on a FreeBSD system at startup.</para>
   </sect1>
@@ -199,7 +199,7 @@ label=FreeBSD</programlisting>
 	<abbrev>MBR</abbrev> expects to find the program to run to
 	continue the boot process.  The files in the
 	<filename>/boot</filename> directory are copies of the real files,
-	which are stored outside of the FreeBSD filesystem.</para>
+	which are stored outside of the FreeBSD file system.</para>
 
       <para><filename>boot1</filename> is very simple, since it too 
 	can only be 512 bytes
@@ -208,7 +208,7 @@ label=FreeBSD</programlisting>
 	about the slice, to find and execute <filename>boot2</filename>.</para>
       
       <para><filename>boot2</filename> is slightly more sophisticated, and understands
-	the FreeBSD filesystem enough to find files on it, and can
+	the FreeBSD file system enough to find files on it, and can
 	provide a simple interface to choose the kernel or loader to
 	run.</para>
 
@@ -253,7 +253,7 @@ boot:</screen>
 
     <indexterm><primary>boot-loader</primary></indexterm>
     <para>The loader is the final stage of the three-stage
-      bootstrap, and is located on the filesystem, usually as
+      bootstrap, and is located on the file system, usually as
       <filename>/boot/loader</filename>.</para>
       
     <para>The loader is intended as a user-friendly method for
@@ -512,7 +512,7 @@ boot:</screen>
 
 	  <listitem>
 	    <para>during kernel initialization, ask for the device
-	      to mount as the root filesystem.</para>
+	      to mount as the root file system.</para>
 	  </listitem>
 	</varlistentry>
 
@@ -581,6 +581,9 @@ boot:</screen>
     <para>During initial system startup, the boot &man.loader.8; will read the
       &man.device.hints.5; file.  This file stores kernel boot information
       known as variables, sometimes referred to as <quote>device hints</quote>.</para>
+      
+      <note><para>This is a FreeBSD 5.0 feature and does not exist in the earlier
+        versions.</para>
 
     <para>Setup of this file is one variable per line, using the standard hash
       <quote>#</quote> as comment markers.  After system initialization, new
@@ -651,7 +654,7 @@ boot:</screen>
       <title>Automatic Reboot Sequence</title>
       
       <para>The automatic reboot sequence makes sure that the
-	filesystems available on the system are consistent.  If they
+	file systems available on the system are consistent.  If they
 	are not, and &man.fsck.8; cannot fix the
 	inconsistencies, &man.init.8; drops the system
 	into <link linkend="boot-singleuser">single-user mode</link>
@@ -707,7 +710,7 @@ console none                            unknown off insecure</programlisting>
       <title>Multi-User Mode</title>
       <indexterm><primary>multi-user mode</primary></indexterm>
       
-      <para>If &man.init.8; finds your filesystems to be
+      <para>If &man.init.8; finds your file systems to be
 	in order, or once the user has finished in <link
 	  linkend="boot-singleuser">single-user mode</link>, the
 	system enters multi-user mode, in which it starts the
@@ -722,7 +725,7 @@ console none                            unknown off insecure</programlisting>
 	  <filename>/etc/defaults/rc.conf</filename>, and
 	  system-specific details from
 	  <filename>/etc/rc.conf</filename>, and then proceeds to
-	  mount the system filesystems mentioned in
+	  mount the system file systems mentioned in
 	  <filename>/etc/fstab</filename>, start up networking
 	  services, start up miscellaneous system daemons, and
 	  finally runs the startup scripts of locally installed