diff --git a/ee/dtr/admin/configure/use-a-load-balancer.md b/ee/dtr/admin/configure/use-a-load-balancer.md
index c9f58e0f04..5351e917fb 100644
--- a/ee/dtr/admin/configure/use-a-load-balancer.md
+++ b/ee/dtr/admin/configure/use-a-load-balancer.md
@@ -30,7 +30,11 @@ replicas.
 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.
 
-> **Note:** If you also use UCP there are [additional requirements](https://docs.docker.com/ee/ucp/admin/configure/join-nodes/use-a-load-balancer/#load-balancing-ucp-and-dtr) if you plan to load balance both UCP and DTR using the same load balancer. 
+> Additional load balancer requirements for UCP
+>
+> If you are also using UCP, there are [additional requirements](https://docs.docker.com/ee/ucp/admin/configure/join-nodes/use-a-load-balancer/#load-balancing-ucp-and-dtr) if you plan to load balance both UCP and DTR using the same load balancer. 
+>
+>{: .important}
 
 You can use the unauthenticated `/_ping` endpoint on each DTR replica,
 to check if the replica is healthy and if it should remain in the load balancing