From 460310b36d06079a20d9b270e2073edc5ec3bdf1 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Tue, 17 Oct 2017 07:22:13 +0800 Subject: [PATCH] Update 9_load-balance_the_service.md (#4934) --- .../deploy-app/9_load-balance_the_service.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md b/docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md index fd5d21efda..42565714ee 100644 --- a/docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md +++ b/docker-cloud/getting-started/deploy-app/9_load-balance_the_service.md @@ -60,11 +60,11 @@ lb-1 9793e58b ▶ Running dockercloud/haproxy:latest ``` You should notice an URL endpoint in the *PORT* column for haproxy-1. In the -example above this is `lb-1.my-username.cont.dockerapp.io:80`. Open the `lb-1` +example above, this is `lb-1.my-username.cont.dockerapp.io:80`. Open the `lb-1` URL in your browser or curl from the CLI. -If you refresh or run curl multiple times you should see requests distributed -between the two containers of in the `web` service. You can see which container +If you refresh or run curl multiple times, you should see requests distributed +between the two containers of the `web` service. You can see which container responds to your request in the `Hostname` section of the response. ```none