diff --git a/datacenter/dtr/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md b/datacenter/dtr/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
index a874e32bfe..6a4aedea4e 100644
--- a/datacenter/dtr/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
+++ b/datacenter/dtr/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
@@ -8,32 +8,31 @@ This guide contains tips and tricks for troubleshooting DTR problems.
 
 ## Troubleshoot overlay networks
 
-High availability in DTR depends on having overlay networking working in UCP.
-One way to test if overlay networks are working correctly you can deploy
-containers in different nodes, that are attached to the same overlay network
-and see if they can ping one another.
+High availability in DTR depends on swarm overlay networking.  One way to test
+if overlay networks are working correctly is to deploy containers to the same
+overlay network on different nodes and see if they can ping one another.
 
-Use SSH to log into a UCP node, and run:
+Use SSH to log into a node and run:
 
-```none
+```bash
 docker run -it --rm \
   --net dtr-ol --name overlay-test1 \
   --entrypoint sh docker/dtr
 ```
 
-Then use SSH to log into another UCP node and run:
+Then use SSH to log into another node and run:
 
-```none
+```bash
 docker run -it --rm \
   --net dtr-ol --name overlay-test2 \
   --entrypoint ping docker/dtr -c 3 overlay-test1
 ```
 
-If the second command succeeds, it means that overlay networking is working
-correctly.
+If the second command succeeds, it indicates overlay networking is working
+correctly between those nodes.
 
-You can run this test with any overlay network, and any Docker image that has
-`sh` and `ping`.
+You can run this test with any attachable overlay network and any Docker image
+that has `sh` and `ping`.
 
 
 ## Access RethinkDB directly
diff --git a/datacenter/dtr/2.3/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md b/datacenter/dtr/2.3/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
index 17ea68a2b7..36220e7104 100644
--- a/datacenter/dtr/2.3/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
+++ b/datacenter/dtr/2.3/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
@@ -8,32 +8,31 @@ This guide contains tips and tricks for troubleshooting DTR problems.
 
 ## Troubleshoot overlay networks
 
-High availability in DTR depends on having overlay networking working in UCP.
-One way to test if overlay networks are working correctly you can deploy
-containers in different nodes, that are attached to the same overlay network
-and see if they can ping one another.
+High availability in DTR depends on swarm overlay networking.  One way to test
+if overlay networks are working correctly is to deploy containers to the same
+overlay network on different nodes and see if they can ping one another.
 
-Use SSH to log into a UCP node, and run:
+Use SSH to log into a node and run:
 
-```none
+```bash
 docker run -it --rm \
   --net dtr-ol --name overlay-test1 \
   --entrypoint sh {{ page.dtr_org }}/{{ page.dtr_repo }}
 ```
 
-Then use SSH to log into another UCP node and run:
+Then use SSH to log into another node and run:
 
-```none
+```bash
 docker run -it --rm \
   --net dtr-ol --name overlay-test2 \
   --entrypoint ping {{ page.dtr_org }}/{{ page.dtr_repo }} -c 3 overlay-test1
 ```
 
-If the second command succeeds, it means that overlay networking is working
-correctly.
+If the second command succeeds, it indicates overlay networking is working
+correctly between those nodes.
 
-You can run this test with any overlay network, and any Docker image that has
-`sh` and `ping`.
+You can run this test with any attachable overlay network and any Docker image
+that has `sh` and `ping`.
 
 
 ## Access RethinkDB directly
diff --git a/datacenter/dtr/2.4/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md b/datacenter/dtr/2.4/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
index ebafe1c0d0..215049c3f5 100644
--- a/datacenter/dtr/2.4/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
+++ b/datacenter/dtr/2.4/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
@@ -8,32 +8,31 @@ This guide contains tips and tricks for troubleshooting DTR problems.
 
 ## Troubleshoot overlay networks
 
-High availability in DTR depends on having overlay networking working in UCP.
-One way to test if overlay networks are working correctly you can deploy
-containers in different nodes, that are attached to the same overlay network
-and see if they can ping one another.
+High availability in DTR depends on swarm overlay networking.  One way to test
+if overlay networks are working correctly is to deploy containers to the same
+overlay network on different nodes and see if they can ping one another.
 
-Use SSH to log into a UCP node, and run:
+Use SSH to log into a node and run:
 
-```none
+```bash
 docker run -it --rm \
   --net dtr-ol --name overlay-test1 \
   --entrypoint sh {{ page.dtr_org }}/{{ page.dtr_repo }}
 ```
 
-Then use SSH to log into another UCP node and run:
+Then use SSH to log into another node and run:
 
-```none
+```bash
 docker run -it --rm \
   --net dtr-ol --name overlay-test2 \
   --entrypoint ping {{ page.dtr_org }}/{{ page.dtr_repo }} -c 3 overlay-test1
 ```
 
-If the second command succeeds, it means that overlay networking is working
-correctly.
+If the second command succeeds, it indicates overlay networking is working
+correctly between those nodes.
 
-You can run this test with any overlay network, and any Docker image that has
-`sh` and `ping`.
+You can run this test with any attachable overlay network and any Docker image
+that has `sh` and `ping`.
 
 
 ## Access RethinkDB directly
diff --git a/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md b/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
index 8df55b692d..b33e44ff55 100644
--- a/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
+++ b/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
@@ -8,12 +8,11 @@ This guide contains tips and tricks for troubleshooting DTR problems.
 
 ## Troubleshoot overlay networks
 
-High availability in DTR depends on having overlay networking working in UCP.
-One way to test if overlay networks are working correctly you can deploy
-containers in different nodes, that are attached to the same overlay network
-and see if they can ping one another.
+High availability in DTR depends on swarm overlay networking.  One way to test
+if overlay networks are working correctly is to deploy containers to the same
+overlay network on different nodes and see if they can ping one another.
 
-Use SSH to log into a UCP node, and run:
+Use SSH to log into a node and run:
 
 ```bash
 docker run -it --rm \
@@ -21,7 +20,7 @@ docker run -it --rm \
   --entrypoint sh {{ page.dtr_org }}/{{ page.dtr_repo }}
 ```
 
-Then use SSH to log into another UCP node and run:
+Then use SSH to log into another node and run:
 
 ```bash
 docker run -it --rm \
@@ -29,11 +28,11 @@ docker run -it --rm \
   --entrypoint ping {{ page.dtr_org }}/{{ page.dtr_repo }} -c 3 overlay-test1
 ```
 
-If the second command succeeds, it means that overlay networking is working
-correctly.
+If the second command succeeds, it indicates overlay networking is working
+correctly between those nodes.
 
-You can run this test with any overlay network, and any Docker image that has
-`sh` and `ping`.
+You can run this test with any attachable overlay network and any Docker image
+that has `sh` and `ping`.
 
 
 ## Access RethinkDB directly