- Run through ispell.

- Capitalize VFS.
- Spell netatalk correctly.
- Write "boot loader" as two words; bootloader isn't a word.

en_US.ISO8859-1/articles/5-roadmap/article.sgml

@@ -99,7 +99,7 @@
         <para>VM: the kmem_malloc(M_NOWAIT) path no longer needs Giant held.
           The kmem_malloc(M_WAITOK) path is in progress and is expected to be
           finished in the coming weeks.  Other facets of the VM system, like
-          the vfs interface, buffer/cache, etc, are largely untouched.</para>
+          the VFS interface, buffer/cache, etc, are largely untouched.</para>
       </listitem>
 
       <listitem>
@@ -115,7 +115,7 @@
           complete.  Work is in progress to lock up the IP stack, including
           the routing tree, ARP code, raw IP, and ifaddr and inet data
           structures.  IPv6 has been lightly touched during the inp locking
-          but is hindered by the KAME code being significnatly out of date.
+          but is hindered by the KAME code being significantly out of date.
           Work has not started on any of the other protocols such as
           AppleTalk, XNS, or IPX.  Locking of the socket layer is in progress
           but has been largely untested.  None of the hardware drivers or
@@ -299,7 +299,7 @@
               stack free of Giant but not the hardware drivers, investigation
               should be done into making it configurable.</para>
 
-            <para>Lesser-used network stacks like netatlk, netipx, etc, should
+            <para>Lesser-used network stacks like netatalk, netipx, etc, should
               not break while this work is going on.  However, locking them is
               not a high priority.  Special kernel config options might be
               needed in order for these layers to operate with the rest of the
@@ -361,7 +361,7 @@
         <listitem>
           <para>PCI resource allocation: PC2003 compliance requires that x86
             systems no longer configure PCI devices from the system BIOS,
-            leaving this task soley to the OS.  &os; must gain the ability to
+            leaving this task solely to the OS.  &os; must gain the ability to
             manage and allocate PCI memory resources on its own.  Implementing
             this should take into account cardbus, PCI-HotPlug, and laptop
             dockstation requirements.  This feature will become increasingly
@@ -475,7 +475,7 @@
             and/or have many other problems.  Fixing these problems seems to
             be an uphill battle and is often times causing a poor
             first-impression of &os; 5.0.  Most x86 systems can function with
-            ACPI disabled, and logic should be added to the bootloader and
+            ACPI disabled, and logic should be added to the boot loader and
             sysinstall to allow users to easily and intuitively turn it off.
             Turning off ACPI by default is prone to problems also as many
             newer systems rely on it to provide correct interrupt routing
@@ -494,7 +494,7 @@
             inconvenient for users of older laptops.  If OLDCARD cannot be
             completely deprecated for &t.releng.5;, then provisions must be made
             to allow users to easily install an OLDCARD-enabled kernel.
-            Documentation should be written to help trasition users from
+            Documentation should be written to help transition users from
             OLDCARD to NEWCARD and from &man.pccardd.8; to
             &man.devd.8;.  The power management and
             <quote>dumpcis</quote> functionality of &man.pccardc.8; needs to be