style(azure-acs): de-youification for dns quickstart

Author: slack

src/quickstart/provider/azure-acs/dns.md

@@ -1,31 +1,33 @@
-## Find Your Load Balancer Address
+## Find the Load Balancer Address
 
 On Azure Container Engine, Deis Workflow will automatically provision and
 attach a Azure Load Balancer to the router component. This component is
 responsible for routing HTTP and HTTPS requests from the public internet to
 applications that are deployed and managed by Deis Workflow.
 
-By describing the `deis-router` service, you can see what IP address has been
-allocated by Azure Cloud for your Deis Workflow cluster:
+Discover the ip address assigned to the `deis-router`, by describing the
+`deis-router` service:
 
 ```
 $ kubectl --namespace=deis get service deis-router
 NAME          CLUSTER-IP    EXTERNAL-IP    PORT(S)                            AGE
 deis-router   10.0.60.172   13.82.148.57   80/TCP,443/TCP,2222/TCP,9090/TCP   54m
 ```
 
-TODO: mention `<pending>` state
+If the `EXTERNAL-IP` column shows `<pending>` instead of an ip address continue
+to wait until Azure finishes provisioning and attaching the load balancer.
 
 ## Prepare the Hostname
 
-Now that you have the ip address of your load balancer we can use the `nip.io`
-DNS service to route arbitrary hostnames to the Deis Workflow edge router. This
-lets us point the Workflow CLI at your cluster without having to either use
-your own domain or update DNS!
+Now that an ip address has been attached to the load balancer use the `nip.io`
+DNS service to route arbitrary hostnames to the Deis Workflow edge router.
+Usage of `nip.io` is not recommended for long-term use and is intended here as
+a short cut to prevent fiddling with DNS.
 
-To verify the Workflow API server and nip.io, construct your hostname by taking
-the ip address for your load balancer and adding `nip.io`. For our example
-above, the address would be: `13.82.148.57.nip.io`.
+To verify connectivity to the Workflow API server and nip.io, construct the
+hostname by taking the ip address of load balancer and adding `nip.io`.
+
+For our example above, the address would be: `13.82.148.57.nip.io`.
 
 Nip answers with the ip address no matter the hostname:
 ```
@@ -35,15 +37,15 @@ $ host something-random.13.82.148.57.nip.io
 something-random.13.82.148.57.nip.io has address 13.82.148.57
 ```
 
-By default, any HTTP traffic for the hostname `deis` will be sent to the Workflow API service. To test that everything is connected properly you may validate connectivity using `curl`:
+By default, any HTTP traffic destined for the hostname `deis` is automatically sent to the Workflow API service. To test that everything is connected properly use `curl`:
 
 ```
 $ curl http://deis.13.82.148.57.nip.io/v2/ && echo
 {"detail":"Authentication credentials were not provided."}
 ```
 
-You should see a failed request because we provided no credentials to the API server.
+Since no authentication information has been provided, `curl` will return an error. However this does validate that `curl` has reached the Workflow API service.
 
-Remember the hostname, we will use it in the next step.
+Remember the hostname, it will used in the next step.
 
 You are now ready to [register an admin user and deploy your first app](../../deploy-an-app.md).