diff --git a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
index 992560d286a11..6269dd520c9bd 100644
--- a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
+++ b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
@@ -160,24 +160,28 @@ Once you’ve created a Service of type LoadBalancer, you can use this
 command to find the external IP:
 
 ```
-kubectl get service frontend
+kubectl get service frontend --watch
 ```
 
-The external IP field may take some time to populate.  If this is the
-case, the external IP is listed as `<pending>`.
+This displays the configuration for the `frontend` Service and watches for
+changes. Initially, the external IP is listed as `<pending>`:
 
 ```
 NAME       CLUSTER-IP      EXTERNAL-IP   PORT(S)  AGE
 frontend   10.51.252.116   <pending>     80/TCP   10s
 ```
 
-Repeat the same command again until it shows an external IP address:
+As soon as an external IP is provisioned, however, the configuration updates
+to include the new IP under the `EXTERNAL-IP` heading:
 
 ```
 NAME       CLUSTER-IP      EXTERNAL-IP        PORT(S)  AGE
 frontend   10.51.252.116   XXX.XXX.XXX.XXX    80/TCP   1m
 ```
 
+That IP can now be used to interact with the `frontend` service from outside the
+cluster.
+
 ### Send traffic through the frontend
 
 The frontend and backends are now connected. You can hit the endpoint
@@ -189,7 +193,7 @@ curl http://<EXTERNAL-IP>
 
 The output shows the message generated by the backend:
 
-```
+```json
 {"message":"Hello"}
 ```