diff --git a/docker-for-mac/kubernetes.md b/docker-for-mac/kubernetes.md
index 4685cce5b4..30adeac851 100644
--- a/docker-for-mac/kubernetes.md
+++ b/docker-for-mac/kubernetes.md
@@ -85,7 +85,7 @@ docker-for-desktop   Ready     master    3h        v1.8.2
 ## Example app
 
 Docker has created the following demo app that you can deploy to swarm mode or
-to to Kubernetes using the `docker stack deploy` command.
+to Kubernetes using the `docker stack deploy` command.
 
 ```yaml
 version: '3.3'
diff --git a/engine/userguide/storagedriver/device-mapper-driver.md b/engine/userguide/storagedriver/device-mapper-driver.md
index c6afed3722..4fb53bf9e2 100644
--- a/engine/userguide/storagedriver/device-mapper-driver.md
+++ b/engine/userguide/storagedriver/device-mapper-driver.md
@@ -774,7 +774,7 @@ use `loop-lvm`, the blocks may not be freed. This is another reason not to use
 - **`allocate-on demand` performance impact**:
 
   The `devicemapper` storage driver uses an `allocate-on-demand` operation to
-  allocate new blocks from the thin pool into to a container's writable layer.
+  allocate new blocks from the thin pool into a container's writable layer.
   Each block is 64KB, so this is the minimum amount of space that will be used
   for a write.