1 files changed, 1 insertions, 1 deletions
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
 The more-sophisticated device-mapper targets require complex metadata
 that is managed in kernel.  In late 2010 we were seeing that various
-different targets were rolling their own data strutures, for example:
+different targets were rolling their own data structures, for example:
 - Mikulas Patocka's multisnap implementation
 - Heinz Mauelshagen's thin provisioning target

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
4	The more-sophisticated device-mapper targets require complex metadata	4	The more-sophisticated device-mapper targets require complex metadata
5	that is managed in kernel. In late 2010 we were seeing that various	5	that is managed in kernel. In late 2010 we were seeing that various
6	different targets were rolling their own data strutures, for example:	6	different 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