- Correct comment about MCA support (FreeBSD provides a limited support)

- s/pesudo/pseudo
- While I'm there: various tags cleaning/adding, use of man entities and
other cleanings.

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

@@ -234,7 +234,7 @@
       <para>Be sure to always check the file
         <filename>/usr/src/UPDATING</filename>, before you perform any update
         steps, in the case you <link
-        linkend="cutting-edge">sync your source-tree</link> with the
+        linkend="cutting-edge">sync your source tree</link> with the
         latest sources of the FreeBSD project.
         In this file all important issues with updating FreeBSD
         are written down.  <filename>/usr/src/UPDATING</filename> always fits
@@ -357,7 +357,7 @@
     <para>The new kernel will be copied to the root directory as
       <filename>/kernel</filename> and the old kernel will be moved to
       <filename>/kernel.old</filename>.  Now, shutdown the system and
-      reboot to use your kernel.  In case something goes wrong, there are
+      reboot to use your new kernel.  In case something goes wrong, there are
       some <link linkend="kernelconfig-trouble">troubleshooting</link>
       instructions at the end of this chapter.  Be sure to read the
       section which explains how to recover in case your new kernel <link
@@ -472,7 +472,7 @@ cpu          I686_CPU</programlisting>
       sure whether you should use <literal>I586_CPU</literal> or
       <literal>I686_CPU</literal>), however, for a custom kernel, it is
       best to specify only the CPU you have.  If you are unsure of your CPU type,
-      you can use the <command>dmesg</command> command to
+      you can use the &man.dmesg.8; command to
       view your boot up messages.</para>
     <indexterm>
       <primary>kernel options</primary>
@@ -615,10 +615,10 @@ options          FFS_ROOT     #FFS usable as root device [keep this!]</programli
 
     <programlisting>options          SOFTUPDATES  #Enable FFS soft updates support</programlisting>
 
-    <para>This option enables soft updates in the kernel, this will help speed
+    <para>This option enables Soft Updates in the kernel, this will help speed
       up write access on the disks.  They are enabled by default in the 4.X branch
       but may not be turned on.  Review the output from &man.mount.8; to see
-      if you have them enabled.  If you do not see the soft-updates option then
+      if you have them enabled.  If you do not see the <literal>soft-updates</literal> option then
       you will need to activate it using the &man.tunefs.8; or &man.newfs.8;
       for new filesystems.</para>      
 
@@ -702,9 +702,9 @@ options          CD9660_ROOT  #CD-ROM usable as root, CD9660 required</programli
     <programlisting>options          UCONSOLE            #Allow users to grab the console</programlisting>
 
     <para>Allow users to grab the console, which is useful for X users.
-      For example, you can create a console xterm by typing <command>xterm
+      For example, you can create a console <application>xterm</application> by typing <command>xterm
-      -C</command>, which will display any <command>write</command>,
+      -C</command>, which will display any &man.write.1;,
-      <command>talk</command>, and any other messages you receive, as well
+      &man.talk.1;, and any other messages you receive, as well
       as any console messages sent by the kernel.</para>
 
     <programlisting>options          USERCONFIG          #boot -c editor</programlisting>
@@ -778,8 +778,8 @@ options 	_KPOSIX_PRIORITY_SCHEDULING</programlisting>
     <programlisting>device          isa</programlisting>
 
     <para>All PCs supported by FreeBSD have one of these.  If you have an
-      IBM PS/2 (Micro Channel Architecture), you cannot run FreeBSD at
+      IBM PS/2 (Micro Channel Architecture), FreeBSD provides some limited support at
-      this time (support is being worked on).</para>
+      this time.  For more information about the MCA support, see <filename>/usr/src/sys/i386/conf/LINT</filename>.</para>
 
     <programlisting>device          eisa</programlisting>
 
@@ -1112,7 +1112,7 @@ pseudo-device   pty           # Pseudo-ttys (telnet etc)</programlisting>
       It is used by incoming <command>telnet</command> and
       <command>rlogin</command> sessions,
       <application>xterm</application>, and some other applications such
-      as <application>emacs</application>.  A
+      as <application>Emacs</application>.  A
       <replaceable>number</replaceable> after <literal>pty</literal> indicates the number of
       <literal>pty</literal>s to create.  If you need more than the
       default of 16 simultaneous <application>xterm</application> windows
@@ -1123,7 +1123,7 @@ pseudo-device   pty           # Pseudo-ttys (telnet etc)</programlisting>
 
     <para>Memory disk pseudo-devices.</para>
 
-    <programlisting>pesudo-device   gif</programlisting>
+    <programlisting>pseudo-device   gif</programlisting>
 
     <para>or</para>
 
@@ -1258,16 +1258,16 @@ pseudo-device   bpf           # Berkeley packet filter</programlisting>
 	<term><command>config</command> fails:</term>
 
 	<listitem>
-	  <para>If the <command>config</command> command fails when you
+	  <para>If the &man.config.8; command fails when you
 	    give it your kernel description, you have probably made a
 	    simple error somewhere.  Fortunately,
-	    <command>config</command> will print the line number that it
+	    &man.config.8; will print the line number that it
 	    had trouble with, so you can quickly skip to it with
-	    <command>vi</command>.  For example, if you see:</para>
+	    <application>vi</application>.  For example, if you see:</para>
 
 	  <screen>config: line 17: syntax error</screen>
 
-	  <para>You can skip to the problem in <command>vi</command> by
+	  <para>You can skip to the problem in <application>vi</application> by
 	    typing <command>17G</command> in command mode.  Make sure the
 	    keyword is typed correctly, by comparing it to the
 	    <filename>GENERIC</filename> kernel or another
@@ -1281,7 +1281,7 @@ pseudo-device   bpf           # Berkeley packet filter</programlisting>
 	<listitem>
 	  <para>If the <command>make</command> command fails, it usually
 	    signals an error in your kernel description, but not severe
-	    enough for <command>config</command> to catch it.  Again, look
+	    enough for &man.config.8; to catch it.  Again, look
 	    over your configuration, and if you still cannot resolve the
 	    problem, send mail to the &a.questions; with your kernel
 	    configuration, and it should be diagnosed very quickly.</para>
@@ -1289,7 +1289,7 @@ pseudo-device   bpf           # Berkeley packet filter</programlisting>
       </varlistentry>
 
       <varlistentry>
-	<term>Installing the new kernel fails</term>
+	<term>Installing the new kernel fails:</term>
 	
 	<listitem>
 	  <para>If the kernel compiled fine, but failed to install
@@ -1306,17 +1306,17 @@ pseudo-device   bpf           # Berkeley packet filter</programlisting>
       </varlistentry>
 
       <varlistentry>
-	<term>The kernel will not boot:<anchor
+	<term>The kernel does not boot:<anchor
 	  id="kernelconfig-noboot"></term>
 
 	<listitem>
 	  <para>If your new kernel does not boot, or fails to
-	    recognize your devices, do not panic!  Fortunately, BSD has
+	    recognize your devices, do not panic!  Fortunately, FreeBSD has
 	    an excellent mechanism for recovering from incompatible
 	    kernels.  Simply choose the kernel you want to boot from at
 	    the FreeBSD boot loader. You can access this when the system
 	    counts down from 10.  Hit any key except for the
-            <keycap>enter</keycap> key, type <command>unload</command>
+            <keycap>Enter</keycap> key, type <command>unload</command>
             and then type
 	    <command>boot <replaceable>kernel.old</replaceable></command>,
             or the filename of any other kernel that will boot properly.
@@ -1365,8 +1365,8 @@ pseudo-device   bpf           # Berkeley packet filter</programlisting>
       </varlistentry>
 
       <varlistentry>
-	<term>The kernel works, but <command>ps</command> does not work
+	<term>The kernel works, but &man.ps.1; does not work
-	  any more!:</term>
+	  any more:</term>
 
 	<listitem>
 	  <para>If you have installed a different version of the kernel