diff options
| author | Elmar Hoffmann <elho@elho.net> | 2019-06-15 13:19:43 +0200 |
|---|---|---|
| committer | Elmar Hoffmann <elho@elho.net> | 2019-06-15 13:19:43 +0200 |
| commit | d2595065b491ad309687c1937e4515b1f5c00daf (patch) | |
| tree | a006495721513c38102b6bcbfbd757337617261d | |
| parent | 47fa7a83a7fea30e8dbd314c3aefecfe344fd127 (diff) | |
fix spelling
| -rw-r--r-- | docs/usage/notes.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/usage/notes.rst b/docs/usage/notes.rst index 2eb0b03f0..b957dfb56 100644 --- a/docs/usage/notes.rst +++ b/docs/usage/notes.rst @@ -131,7 +131,7 @@ Imagine you have made some snapshots of logical volumes (LVs) you want to backup For some scenarios, this is a good method to get "crash-like" consistency (I call it crash-like because it is the same as you would get if you just - hit the reset button or your machine would abrubtly and completely crash). + hit the reset button or your machine would abruptly and completely crash). This is better than no consistency at all and a good method for some use cases, but likely not good enough if you have databases running. |