diff --git a/modules/nw-configuring-route-timeouts.adoc b/modules/nw-configuring-route-timeouts.adoc
index 5eb7d06b22f3..20b7f747558f 100644
--- a/modules/nw-configuring-route-timeouts.adoc
+++ b/modules/nw-configuring-route-timeouts.adoc
@@ -7,15 +7,19 @@
 [id="nw-configuring-route-timeouts_{context}"]
 = Configuring route timeouts
 
-You can configure the default timeouts for an existing route when you
-have services in need of a low timeout, which is required for Service Level
-Availability (SLA) purposes, or a high timeout, for cases with a slow
-back end.
+You can configure the default timeouts for an existing route when you have services in need of a low timeout, which is required for Service Level Availability (SLA) purposes, or a high timeout, for cases with a slow back end.
+
+[IMPORTANT]
+====
+If you configured a user-managed external load balancer in front of your {product-title} cluster, ensure that the timeout value for the user-managed external load balancer is higher than the timeout value for the route service. This configuration prevents network congestion issues over the network that your cluster uses.
+====
 
 .Prerequisites
+
 * You need a deployed Ingress Controller on a running cluster.
 
 .Procedure
+
 . Using the `oc annotate` command, add the timeout to the route:
 +
 [source,terminal]
@@ -23,10 +27,9 @@ back end.
 $ oc annotate route <route_name> \
     --overwrite haproxy.router.openshift.io/timeout=<timeout><time_unit> <1>
 ----
-<1> Supported time units are microseconds (us), milliseconds (ms), seconds (s),
-minutes (m), hours (h), or days (d).
+<1> Supported time units are microseconds (us), milliseconds (ms), seconds (s), minutes (m), hours (h), or days (d).
 +
-The following example sets  a timeout of two seconds on a route named `myroute`:
+The following example sets a timeout of two seconds on a route named `myroute`:
 +
 [source,terminal]
 ----