Index: en_US.ISO8859-1/articles/vinum/article.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/vinum/article.sgml,v
retrieving revision 1.9
diff -u -r1.9 article.sgml
--- en_US.ISO8859-1/articles/vinum/article.sgml	2002/07/07 17:54:24	1.9
+++ en_US.ISO8859-1/articles/vinum/article.sgml	2002/12/01 13:31:36
@@ -1078,7 +1078,7 @@
 	      <devicename>/dev/ad0s1f</devicename>
 	      by default.)</para>
 
-	    <note><para>If you prefer soft updates as I do and you are
+	    <note><para>If you prefer Soft Updates as I do and you are
 	      using 4.4-RELEASE or better, this is a good time to enable
 	      them.</para></note>
 
Index: en_US.ISO8859-1/books/developers-handbook/vm/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/vm/chapter.sgml,v
retrieving revision 1.5
diff -u -r1.5 chapter.sgml
--- en_US.ISO8859-1/books/developers-handbook/vm/chapter.sgml	2002/10/13 16:22:23	1.5
+++ en_US.ISO8859-1/books/developers-handbook/vm/chapter.sgml	2002/12/01 13:31:36
@@ -237,7 +237,7 @@
 	especially the VM related ones.</para>
 
       <para>Run time VM and system tuning is relatively straightforward.
-	First, use softupdates on your UFS/FFS filesystems whenever possible.
+	First, use Soft Updates on your UFS/FFS filesystems whenever possible.
 	<filename>/usr/src/sys/ufs/ffs/README.softupdates</filename> contains
 	instructions (and restrictions) on how to configure it.</para>
 
Index: en_US.ISO8859-1/books/faq/book.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.497
diff -u -r1.497 book.sgml
--- en_US.ISO8859-1/books/faq/book.sgml	2002/11/30 12:17:03	1.497
+++ en_US.ISO8859-1/books/faq/book.sgml	2002/12/01 13:31:47
@@ -5478,24 +5478,24 @@
 
       <qandaentry>
         <question id="safe-softupdates">
-          <para>Which partitions can safely use softupdates?  I have
-            heard that softupdates on <filename>/</filename> can cause
+          <para>Which partitions can safely use Soft Updates?  I have
+            heard that Soft Updates on <filename>/</filename> can cause
             problems.</para>
         </question>
 
         <answer>
-          <para>Short answer: you can usually use softupdates safely
+          <para>Short answer: you can usually use Soft Updates safely
             on all partitions.</para>
 
           <para>Long answer: There used to be some concern over using
-            softupdates on the root partition.  Softupdates has two
-            characteristics that caused this.  First, a softupdates
+            Soft Updates on the root partition.  Soft Updates has two
+            characteristics that caused this.  First, a Soft Updates
             partition has a small chance of losing data during a
             system crash.  (The partition will not be corrupted; the
-            data will simply be lost.)  Also, softupdates can cause
+            data will simply be lost.)  Also, Soft Updates can cause
             temporary space shortages.</para>
 
-          <para>When using softupdates, the kernel can take up to
+          <para>When using Soft Updates, the kernel can take up to
             thirty seconds to actually write changes to the physical
             disk.  If you delete a large file, the file still resides
             on disk until the kernel actually performs the deletion.
@@ -5517,9 +5517,9 @@
             This risk is extremely small, but generally manageable.
             Use of IDE write caching greatly increases this risk; it
             is strongly recommended that you disable IDE write caching
-            when using softupdates.</para>
+            when using Soft Updates.</para>
 
-          <para>These issues affect all partitions using softupdates.
+          <para>These issues affect all partitions using Soft Updates.
             So, what does this mean for the root partition?</para>
 
           <para>Vital information on the root partition changes very
@@ -5531,7 +5531,7 @@
             possible that data could be lost.  This risk is negligible
             for most applications, but you should be aware that it
             exists.  If your system cannot tolerate this much risk,
-            do not use softupdates on the root filesystem!</para>
+            do not use Soft Updates on the root filesystem!</para>
 
           <para><filename>/</filename> is traditionally one of the
             smallest partitions.  By default, FreeBSD puts the
@@ -6136,7 +6136,7 @@
             <command>du</command> and <command>df</command> will
             agree.</para>
 
-          <para>Note that softupdates can delay the freeing of disk
+          <para>Note that Soft Updates can delay the freeing of disk
             space; you might need to wait up to 30 seconds for the
             change to be visible!</para>
 
Index: en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v
retrieving revision 1.88
diff -u -r1.88 chapter.sgml
--- en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml	2002/11/30 11:07:57	1.88
+++ en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml	2002/12/01 13:31:48
@@ -614,7 +614,7 @@
       is at a premium and disk access speed is less important, such as a
       firewall.</para>
 
-    <programlisting>options          SOFTUPDATES  #Enable FFS soft updates support</programlisting>
+    <programlisting>options          SOFTUPDATES  #Enable FFS Soft Updates support</programlisting>
 
     <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