summaryrefslogtreecommitdiff
path: root/mdmon.8
diff options
context:
space:
mode:
authorNamhyung Kim <namhyung@gmail.com>2011-06-24 13:26:49 +0900
committerNeilBrown <neilb@suse.de>2011-06-28 16:36:42 +1000
commit2f48b33d1d7da25cd54edf32edeb0a59a7f75f43 (patch)
treeaf7d69c7b1b450494302f309e31a6ac86a911842 /mdmon.8
parent2d3603ba0cb497429d2841d2fb4a5e36879e808b (diff)
mdmon.8: fix possible typos
Signed-off-by: Namhyung Kim <namhyung@gmail.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdmon.8')
-rw-r--r--mdmon.84
1 files changed, 2 insertions, 2 deletions
diff --git a/mdmon.8 b/mdmon.8
index 7939a99a..03b31b86 100644
--- a/mdmon.8
+++ b/mdmon.8
@@ -104,7 +104,7 @@ 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
set of disks, MD metadata requires the disks be partitioned and then
-each array can created be created with a subset of those partitions. The
+each array can be created with a subset of those partitions. The
supported external formats perform this disk carving internally.
.P
Container devices simply hold references to all member disks and allow
@@ -172,7 +172,7 @@ Note that
is automatically started by
.I mdadm
when needed and so does not need to be considered when working with
-RAID arrays. The only times it is run other that by
+RAID arrays. The only times it is run other than by
.I mdadm
is when the boot scripts need to restart it after mounting the new
root filesystem.