From c29f78cd6d9eec2fcac10714e30e22403b5c9639 Mon Sep 17 00:00:00 2001
From: Ceri Davies <ceri@FreeBSD.org>
Date: Sun, 18 Aug 2002 11:56:03 +0000
Subject: [PATCH] Fix some spelling errors. Move some text into a footnote
 where it belongs.

---
 .../books/handbook/vinum/chapter.sgml         | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml b/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
index 73e709555f..6d19e7738e 100644
--- a/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
@@ -57,7 +57,7 @@
     <para>Disks are getting bigger, but so are data storage requirements.
       Often you'll find you want a file system that is bigger than the disks
       you have available.  Admittedly, this problem is not as acute as it was
-      ten years ago, but it still exists.  Some systems have solve this by
+      ten years ago, but it still exists.  Some systems have solved this by
       creating an abstract device which stores its data on a number of disks.</para>
   </sect1>
 
@@ -150,9 +150,9 @@
     <secondary>Array of Inexpensive Disks</secondary></indexterm>
     
     <para><acronym>RAID</acronym> stands for <emphasis>Redundant Array of
-    Inexpensive Disks</emphasis> and offers various forms of fault tolerance.
-    </para></footnote> though the latter term is somewhat misleading: it
-    provides no redundancy.  Striping requires somewhat more effort to locate
+    Inexpensive Disks</emphasis> and offers various forms of fault tolerance,
+    though the latter term is somewhat misleading: it
+    provides no redundancy.</para></footnote>  Striping requires somewhat more effort to locate
     the data, and it can cause additional I/O load where a transfer is spread
     over multiple disks, but it can also provide a more constant load across
     the disks.  <xref linkend="vinum-striped"> illustrates the sequence in
@@ -368,7 +368,7 @@
 
 	  <tbody>
 	    <row>
-	      <entry>concatnated</entry>
+	      <entry>concatenated</entry>
 	      <entry>1</entry>
 	      <entry>yes</entry>
 	      <entry>no</entry>
@@ -654,14 +654,14 @@
     <title>Object naming</title>
     <para>As described above, Vinum assigns default names to plexes and
       subdisks, although they may be overridden.  Overriding the default names
-      is not recommended: experience with the VERITAS\(rg volume manager, which
+      is not recommended: experience with the VERITAS volume manager, which
       allows arbitrary naming of objects, has shown that this flexibility does
       not bring a significant advantage, and it can cause confusion.</para>
 
     <para>Names may contain any non-blank character, but it is recommended to
       restrict them to letters, digits and the underscore characters.  The names
       of volumes, plexes and subdisks may be up to 64 characters long, and the
-      names of drives may up to 32 characters long.</para>
+      names of drives may be up to 32 characters long.</para>
 
     <para><indexterm><primary>/dev/vinum</primary></indexterm>Vinum objects
       are assigned device nodes in the hierarchy <filename>/dev/vinum</filename>.
@@ -679,7 +679,7 @@
 	<para>Block and character device entries for each volume.
 	  These are the main devices used by Vinum.  The block device names are
 	  the name of the volume, while the character device names follow the BSD 
-	  tradition of perpending the letter <emphasis>r</emphasis> to the name.  
+	  tradition of prepending the letter <emphasis>r</emphasis> to the name.  
 	  Thus the configuration above would include the block devices 
 	  <devicename>/dev/vinum/myvol</devicename>, 
 	  <devicename>/dev/vinum/mirror</devicename>,  
@@ -717,7 +717,7 @@
 	  <devicename>/dev/vinum/sd</devicename>, 
 	  <devicename>/dev/vinum/rsd</devicename>, which contain block device
 	  nodes for each plex and block and character device nodes respectively 
-	  for subdisk.</para>
+	  for each subdisk.</para>
       </listitem>
     </itemizedlist>
 
@@ -811,7 +811,7 @@
 	  For example, a disk drive may have a name like <devicename>/dev/wd0a</devicename>
 	  or <devicename>/dev/da2h</devicename>.  These names represent the first
 	  partition (<devicename>a</devicename>) on the first (0) IDE disk
-	  (<devicename>wd</devicename>) and the eight partition
+	  (<devicename>wd</devicename>) and the eighth partition
 	  (<devicename>h</devicename>) on the third (2) SCSI disk
 	  (<devicename>da</devicename>) respectively.  By contrast, a Vinum volume
 	  might be called <devicename>/dev/vinum/concat</devicename>, a name which