aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/device-mapper
diff options
context:
space:
mode:
authorMasanari Iida <standby24x7@gmail.com>2012-03-04 09:16:11 -0500
committerJiri Kosina <jkosina@suse.cz>2012-03-07 10:08:24 -0500
commit40e47125e6c5110383b0176d7b9d530f2936b1ae (patch)
tree9653ac1f586cbfe36286c2d987c9330078eb37ad /Documentation/device-mapper
parent4e70daaf05a181b6968e29e72e9f1c16a183e92c (diff)
Documentation: Fix multiple typo in Documentation
Signed-off-by: Masanari Iida <standby24x7@gmail.com> Acked-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/device-mapper')
-rw-r--r--Documentation/device-mapper/dm-raid.txt2
-rw-r--r--Documentation/device-mapper/persistent-data.txt2
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/device-mapper/dm-raid.txt b/Documentation/device-mapper/dm-raid.txt
index 2a8c11331d2..946c73342cd 100644
--- a/Documentation/device-mapper/dm-raid.txt
+++ b/Documentation/device-mapper/dm-raid.txt
@@ -28,7 +28,7 @@ The target is named "raid" and it accepts the following parameters:
28 raid6_nc RAID6 N continue 28 raid6_nc RAID6 N continue
29 - rotating parity N (right-to-left) with data continuation 29 - rotating parity N (right-to-left) with data continuation
30 30
31 Refererence: Chapter 4 of 31 Reference: Chapter 4 of
32 http://www.snia.org/sites/default/files/SNIA_DDF_Technical_Position_v2.0.pdf 32 http://www.snia.org/sites/default/files/SNIA_DDF_Technical_Position_v2.0.pdf
33 33
34<#raid_params>: The number of parameters that follow. 34<#raid_params>: The number of parameters that follow.
diff --git a/Documentation/device-mapper/persistent-data.txt b/Documentation/device-mapper/persistent-data.txt
index 0e5df9b04ad..a333bcb3a6c 100644
--- a/Documentation/device-mapper/persistent-data.txt
+++ b/Documentation/device-mapper/persistent-data.txt
@@ -3,7 +3,7 @@ Introduction
3 3
4The more-sophisticated device-mapper targets require complex metadata 4The more-sophisticated device-mapper targets require complex metadata
5that is managed in kernel. In late 2010 we were seeing that various 5that is managed in kernel. In late 2010 we were seeing that various
6different targets were rolling their own data strutures, for example: 6different targets were rolling their own data structures, for example:
7 7
8- Mikulas Patocka's multisnap implementation 8- Mikulas Patocka's multisnap implementation
9- Heinz Mauelshagen's thin provisioning target 9- Heinz Mauelshagen's thin provisioning target