summaryrefslogtreecommitdiffstats
path: root/Documentation/device-mapper/persistent-data.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/device-mapper/persistent-data.txt')
-rw-r--r--Documentation/device-mapper/persistent-data.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/device-mapper/persistent-data.txt b/Documentation/device-mapper/persistent-data.txt
index 0e5df9b04ad2..a333bcb3a6c2 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
OpenPOWER on IntegriCloud