DDF: when first activating an array, record any missing devices.

[thirdparty/mdadm.git] / mdmon.8

diff --git a/mdmon.8 b/mdmon.8
index a968cdb031aa8e9e9b2f1f45a710e292eb835b87..d7d26205f5228efcbb7a037a8c1de78f68b74e9a 100644 (file)
--- a/mdmon.8
+++ b/mdmon.8
@@ -1,5 +1,5 @@
 .\" See file COPYING in distribution for details.
-.TH MDMON 8 "" v3.2.5
+.TH MDMON 8 "" v3.3
 .SH NAME
 mdmon \- monitor MD external metadata arrays
 
@@ -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.