align spelling of “RAID” and RAID levels

* Aligned the spelling of “RAID” to use captial letters in all places.
* Aligned the spelling of the RAID level names (LINEAR, RAID1, …) to use capital
  letters in all places, except for the string “faulty” in places where not the
  RAID level was meant.

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>

diff --git a/md.4 b/md.4
index 2574c37e498d325e506b483d2fba8791fded64e4..5f6c3a7c264af867e377588bb17ea6ae7179d7cc 100644 (file)
--- a/md.4
+++ b/md.4
@@ -78,7 +78,7 @@ The metadata contains, among other things:
 .TP
 LEVEL
 The manner in which the devices are arranged into the array
-(linear, raid0, raid1, raid4, raid5, raid10, multipath).
+(LINEAR, RAID0, RAID1, RAID4, RAID5, RAID10, MULTIPATH).
 .TP
 UUID
 a 128 bit Universally Unique Identifier that identifies the array that
@@ -101,7 +101,7 @@ array without superblocks is preferred.  These include:
 LEGACY ARRAYS
 Early versions of the
 .B md
-driver only supported Linear and Raid0 configurations and did not use
+driver only supported LINEAR and RAID0 configurations and did not use
 a superblock (which is less critical with these configurations).
 While such arrays should be rebuilt with superblocks if possible,
 .B md
@@ -118,7 +118,7 @@ written to the device and searched for on all paths.  In this case,
 a MULTIPATH array with no superblock makes sense.
 .TP
 RAID1
-In some configurations it might be desired to create a raid1
+In some configurations it might be desired to create a RAID1
 configuration that does not use a superblock, and to maintain the state of
 the array elsewhere.  While not encouraged for general use, it does
 have special-purpose uses and is supported.
@@ -159,7 +159,7 @@ arrays.
 
 .SS LINEAR
 
-A linear array simply catenates the available space on each
+A LINEAR array simply catenates the available space on each
 drive to form one large virtual drive.
 
 One advantage of this arrangement over the more common RAID0
@@ -317,7 +317,7 @@ are some similarities.
 A MULTIPATH array is composed of a number of logically different
 devices, often fibre channel interfaces, that all refer the the same
 real device. If one of these interfaces fails (e.g. due to cable
-problems), the multipath driver will attempt to redirect requests to
+problems), the MULTIPATH driver will attempt to redirect requests to
 another interface.
 
 The MULTIPATH drive is not receiving any ongoing development and
@@ -325,7 +325,7 @@ should be considered a legacy driver.  The device-mapper based
 multipath drivers should be preferred for new installations.
 
 .SS FAULTY
-The FAULTY md module is provided for testing purposes.  A faulty array
+The FAULTY md module is provided for testing purposes.  A FAULTY array
 has exactly one component device and is normally assembled without a
 superblock, so the md array created provides direct access to all of
 the data in the component device.
@@ -610,7 +610,7 @@ is the processes of re-arranging the data stored in each stripe into a
 new layout.  This might involve changing the number of devices in the
 array (so the stripes are wider), changing the chunk size (so stripes
 are deeper or shallower), or changing the arrangement of data and
-parity (possibly changing the raid level, e.g. 1 to 5 or 5 to 6).
+parity (possibly changing the RAID level, e.g. 1 to 5 or 5 to 6).
 
 As of Linux 2.6.35, md can reshape a RAID4, RAID5, or RAID6 array to
 have a different number of devices (more or fewer) and to have a
@@ -621,7 +621,7 @@ Other possibilities may follow in future kernels.
 
 During any stripe process there is a 'critical section' during which
 live data is being overwritten on disk.  For the operation of
-increasing the number of drives in a raid5, this critical section
+increasing the number of drives in a RAID5, this critical section
 covers the first few stripes (the number being the product of the old
 and new number of devices).  After this critical section is passed,
 data is only written to areas of the array which no longer hold live

diff --git a/mdadm.conf.5 b/mdadm.conf.5
index ced52186e7d2ecda224d0576318af2132aba20a8..6d9b2a4a610bc5e552f2602cd71bae3b04fe7e98 100644 (file)
--- a/mdadm.conf.5
+++ b/mdadm.conf.5
@@ -152,7 +152,7 @@ to assemble the array.  Note that the devices
 listed there must also be listed on a DEVICE line.
 .TP
 .B level=
-The value is a raid level.  This is not normally used to
+The value is a RAID level.  This is not normally used to
 identify an array, but is supported so that the output of
 
 .B "mdadm \-\-examine \-\-scan"

diff --git a/mdassemble.8 b/mdassemble.8
index a55862f04604956fa1d2951bb07cb14cb753f9e5..3721d99bf7f9dd85e1b62e33b0c231152046c0ce 100644 (file)
--- a/mdassemble.8
+++ b/mdassemble.8
@@ -13,7 +13,7 @@ Linux Software RAID
 .B mdassemble
 is a tiny program that can be used to assemble MD devices inside an
 initial ramdisk (initrd) or initramfs; it is meant to replace the in-kernel
-automatic raid detection and activation.
+automatic RAID detection and activation.
 It can be built statically and linked against lightweight libc alternatives, like
 .B dietlibc,
 .B klibc

diff --git a/mdmon.8 b/mdmon.8
index a968cdb031aa8e9e9b2f1f45a710e292eb835b87..0b74b216d18071810ee32d7aad526fd1fd19eabc 100644 (file)
--- a/mdmon.8
+++ b/mdmon.8
@@ -101,8 +101,8 @@ call is still required.
 External metadata formats, like DDF, differ from the native MD metadata
 formats in that they define a set of disks and a series of sub-arrays
 within those disks.  MD metadata in comparison defines a 1:1
-relationship between a set of block devices and a raid array.  For
-example to create 2 arrays at different raid levels on a single
+relationship between a set of block devices and a RAID array.  For
+example to create 2 arrays at different RAID levels on a single
 set of disks, MD metadata requires the disks be partitioned and then
 each array can be created with a subset of those partitions.  The
 supported external formats perform this disk carving internally.