make MD array and RAID synonymous, fjp request

1 files changed, 15 insertions, 14 deletions

diff --git a/debian/mdadm.templates b/debian/mdadm.templates
index 50f0efa6..00193227 100644
--- a/debian/mdadm.templates
+++ b/debian/mdadm.templates
@@ -1,7 +1,7 @@
 Template: mdadm/initrdstart
 Type: string
 Default: all
-_Description: MD arrays needed for the root filesystem:
+_Description: MD arrays (RAIDs) needed for the root filesystem:
  ${msg}
  .
  Please enter a space-separated list of devices, 'all', or 'none'. You may
@@ -10,7 +10,7 @@ _Description: MD arrays needed for the root filesystem:
 Template: mdadm/initrdstart_msg_intro
 Type: text
 _Description: 
- If your system has its root filesystem on a MD volume, it needs to be
+ If your system has its root filesystem on a MD array (RAID), it needs to be
  started early during the boot sequence. If your root filesystem is on
  a logical volume (LVM), which is on MD, all constituent arrays need to be
  started.
@@ -37,7 +37,7 @@ _Description:
 Template: mdadm/initrdstart_msg_errmd
 Type: text
 _Description:
- An error occurred: not a MD array
+ An error occurred: not a MD array (RAID)
 
 Template: mdadm/initrdstart_msg_errconf
 Type: text
@@ -64,19 +64,20 @@ _Description: Proceed with starting arrays not listed in mdadm.conf?
 Template: mdadm/autostart
 Type: boolean
 Default: true
-_Description: Do you want to start MD devices automatically?
- Once the base system has come up, mdadm can start all MD devices specified
- in /etc/mdadm/mdadm.conf, which have not yet been started. Unless you have
- compiled MD support into the kernel (in which case all MD arrays with
- partitions of type 0xfd (and only those) are started automatically anyway),
+_Description: Do you want to start MD arrays (RAIDs) automatically?
+ Once the base system has come up, mdadm can start all MD arrays (RAIDs)
+ specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless
+ you have compiled MD support into the kernel (in which case all MD arrays
+ with partitions of type 0xfd (and only those) are started automatically
+ anyway),
  this is probably what you want.
 
 Template: mdadm/autocheck
 Type: boolean
 Default: true
-_Description: Should mdadm run monthly redundancy checks of the MD arrays?
+_Description: Should mdadm run monthly redundancy checks of the MD arrays (RAIDs)?
  If your kernel supports it (>> 2.6.14), mdadm can periodically check the
- redundancy of your MD devices. This may be a resource-intensive process,
+ redundancy of your MD arrays (RAIDs). This may be a resource-intensive process,
  depending on your setup, but it could help prevent rare cases of data loss.
  Note that this is a read-only check unless errors are found; if errors are
  found, mdadm will try to correct them, which may result in write access to
@@ -88,13 +89,13 @@ _Description: Should mdadm run monthly redundancy checks of the MD arrays?
 Template: mdadm/start_daemon
 Type: boolean
 Default: true
-_Description: Do you want to start the MD monitoring daemon?
- The MD monitor daemon sends email notifications in response to important
- MD events (such as a disk failure). You probably want to enable it.
+_Description: Do you want to start the MD (RAID) monitoring daemon?
+ The MD (RAID) monitor daemon sends email notifications in response to
+ important MD events (such as a disk failure). You probably want to enable it.
 
 Template: mdadm/mail_to
 Type: string
 Default: root
 _Description: Recipient for email notifications:
  Please enter the email address of the user who should get the email
- notification for these important MD events.
+ notification for important MD (RAID) events.