Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
| ... | ... |
@@ -201,7 +201,7 @@ Here is the list of supported options: |
| 201 | 201 |
|
| 202 | 202 |
Enables or disables the use of blkdiscard when removing |
| 203 | 203 |
devicemapper devices. This is enabled by default (only) if using |
| 204 |
- loopback devices and is required to res-parsify the loopback file |
|
| 204 |
+ loopback devices and is required to resparsify the loopback file |
|
| 205 | 205 |
on image/container removal. |
| 206 | 206 |
|
| 207 | 207 |
Disabling this on loopback can lead to *much* faster container |
| ... | ... |
@@ -277,7 +277,7 @@ is 64K. |
| 277 | 277 |
#### dm.blkdiscard |
| 278 | 278 |
Enables or disables the use of blkdiscard when removing devicemapper devices. |
| 279 | 279 |
This is enabled by default (only) if using loopback devices and is required to |
| 280 |
-res-parsify the loopback file on image/container removal. |
|
| 280 |
+resparsify the loopback file on image/container removal. |
|
| 281 | 281 |
|
| 282 | 282 |
Disabling this on loopback can lead to *much* faster container removal times, |
| 283 | 283 |
but will prevent the space used in `/var/lib/docker` directory from being returned to |
| ... | ... |
@@ -325,7 +325,7 @@ Currently supported options are: |
| 325 | 325 |
|
| 326 | 326 |
Enables or disables the use of blkdiscard when removing devicemapper |
| 327 | 327 |
devices. This is enabled by default (only) if using loopback devices and is |
| 328 |
- required to res-parsify the loopback file on image/container removal. |
|
| 328 |
+ required to resparsify the loopback file on image/container removal. |
|
| 329 | 329 |
|
| 330 | 330 |
Disabling this on loopback can lead to *much* faster container removal |
| 331 | 331 |
times, but will make the space used in `/var/lib/docker` directory not be |