From fa09742e7eff9a3eeee4dbbc0672292686c93405 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Mon, 27 Aug 2018 16:21:57 -0700 Subject: [PATCH] Grammar fixes --- storage/storagedriver/device-mapper-driver.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/storage/storagedriver/device-mapper-driver.md b/storage/storagedriver/device-mapper-driver.md index 9dd8d4117d..aceb8019a9 100644 --- a/storage/storagedriver/device-mapper-driver.md +++ b/storage/storagedriver/device-mapper-driver.md @@ -19,7 +19,7 @@ Docker. The `devicemapper` driver uses block devices dedicated to Docker and operates at the block level, rather than the file level. These devices can be extended by adding physical storage to your Docker host, and they perform better than using -a filesystem at the level of the operating system. +a filesystem at the operating system (OS) level. ## Prerequisites @@ -32,7 +32,7 @@ a filesystem at the level of the operating system. - Changing the storage driver makes any containers you have already created inaccessible on the local system. Use `docker save` to save containers, - and push existing images to Docker Hub or a private repository, so that you + and push existing images to Docker Hub or a private repository, so you do not need to re-create them later. ## Configure Docker with the `devicemapper` storage driver @@ -136,14 +136,14 @@ below to configure Docker to use the `devicemapper` storage driver in > **Warning**: Changing the storage driver makes any containers you have already created inaccessible on the local system. Use `docker save` to save containers, - and push existing images to Docker Hub or a private repository, so that you - don't need to recreate them later. + and push existing images to Docker Hub or a private repository, so you do not + need to recreate them later. #### Allow Docker to configure direct-lvm mode -In Docker 17.06 and higher, Docker can manage the block device for you, -simplifying configuration of `direct-lvm` mode. **This is appropriate for fresh -Docker set-ups only.** You can only use a single block device. If you need to +With Docker `17.06` and higher, Docker can manage the block device for you, +simplifying configuration of `direct-lvm` mode. **This is appropriate for fresh +Docker setups only.** You can only use a single block device. If you need to use multiple block devices, [configure direct-lvm mode manually](#configure-direct-lvm-mode-manually) instead. The following new configuration options have been added: @@ -158,7 +158,7 @@ configuration options have been added: | `dm.directlvm_device_force` | Whether to format the block device even if a filesystem already exists on it. If set to `false` and a filesystem is present, an error is logged and the filesystem is left intact. | No | false | `dm.directlvm_device_force=true` | Edit the `daemon.json` file and set the appropriate options, then restart Docker -for the changes to take effect. The following `daemon.json` sets all of the +for the changes to take effect. The following `daemon.json` configuration sets all of the options in the table above. ```json