diff --git a/datacenter/dtr/2.2/guides/admin/configure/use-a-load-balancer.md b/datacenter/dtr/2.2/guides/admin/configure/use-a-load-balancer.md
index 28a368fcc8..5664052b37 100644
--- a/datacenter/dtr/2.2/guides/admin/configure/use-a-load-balancer.md
+++ b/datacenter/dtr/2.2/guides/admin/configure/use-a-load-balancer.md
@@ -14,14 +14,14 @@ This allows users to access DTR using a centralized domain name. If a replica
 goes down, the load balancer can detect that and stop forwarding requests to
 it, so that the failure goes unnoticed by users.
 
-## Load-balancing DTR
+## Load balancing DTR
 
 DTR does not provide a load balancing service. You can use an on-premises
 or cloud-based load balancer to balance requests across multiple DTR replicas.
 
 Make sure you configure your load balancer to:
 
-* Load-balance TCP traffic on ports 80 and 443
+* Load balance TCP traffic on ports 80 and 443
 * Not terminate HTTPS connections
 * Use the `/health` endpoint on each DTR replica, to check if
 the replica is healthy and if it should remain on the load balancing pool or