Doc corrections and improvements (#1449)

content/docs/guides/bookinfo.md

@@ -137,11 +137,13 @@ To start the application, follow the instructions below corresponding to your Is
 
 #### Determining the ingress IP and port
 
-Follow [the instructions](/docs/tasks/traffic-management/ingress/#determining-the-ingress-ip-and-ports) to set the `INGRESS_HOST` and `INGRESS_PORT` variables. Set `GATEWAY_URL`:
+1. Follow [these instructions](/docs/tasks/traffic-management/ingress/#determining-the-ingress-ip-and-ports) to set the `INGRESS_HOST` and `INGRESS_PORT` variables.
 
-```command
-$ export GATEWAY_URL=$INGRESS_HOST:$INGRESS_PORT
-```
+1. Set `GATEWAY_URL`:
+
+   ```command
+   $ export GATEWAY_URL=$INGRESS_HOST:$INGRESS_PORT
+   ```
 
 ### Running on Docker with Consul or Eureka
 

content/docs/setup/kubernetes/quick-start.md

@@ -237,7 +237,7 @@ installation directory contains:
     * The `istioctl` client binary in the `bin/` directory. `istioctl` is used when manually injecting Envoy as a sidecar proxy and for creating routing rules and policies.
     * The `istio.VERSION` configuration file
 
-1.  Change directory to the istio package. For example, if the package is istio-{{< istio_version >}}.0;
+1.  Change directory to the istio package. For example, if the package is istio-{{< istio_version >}}.0:
 
     ```command
     $ cd istio-{{< istio_version >}}.0
@@ -295,8 +295,8 @@ OR
     ```
 
     > If your cluster is running in an environment that does not support an external load balancer
-    (e.g., minikube), the `EXTERNAL-IP` of `istio-ingress` says `<pending>`. You must access the
-    application using the service NodePort, or use port-forwarding instead.
+    (e.g., minikube), the `EXTERNAL-IP` of `istio-ingressgateway` will say `<pending>`. You will need to access
+    it using the service NodePort, or use port-forwarding instead.
 
 1.  Ensure the corresponding Kubernetes pods are deployed and all containers are up and running:
 `istio-pilot-*`, `istio-ingressgateway-*`, `istio-egressgateway-*`, `istio-policy-*`, `istio-telemtry-*`, `istio-citadel-*`, `prometheus-*` and, optionally, `istio-sidecar-injector-*`.

content/docs/tasks/traffic-management/egress.md

@@ -33,7 +33,7 @@ or alternatively, to simply bypass the Istio proxy for a specific range of IPs.
 
 Using Istio `ServiceEntry` configurations, you can access any publicly accessible service
 from within your Istio cluster. In this task we will use
-[httpbin.org](http://httpbin.org) and [www.google.com](http://www.google.com) as examples.
+[httpbin.org](http://httpbin.org) and [www.google.com](https://www.google.com) as examples.
 
 ### Configuring the external services
 
@@ -89,7 +89,7 @@ from within your Istio cluster. In this task we will use
     $ curl http://httpbin.org/headers
     ```
 
-1.  Make a request to the external HTTPS service.
+1.  Make a request to the external HTTPS service:
 
     ```command
     $ curl https://www.google.com

content/docs/tasks/traffic-management/request-routing.md

@@ -107,7 +107,9 @@ you'll need to use `replace` rather than `create` in the following command.
     Since rule propagation to the proxies is asynchronous, you should wait a few seconds for the rules
     to propagate to all pods before attempting to access the application.
 
-1.  Open the Bookinfo URL (http://$GATEWAY_URL/productpage) in your browser.  If `$GATEWAY_URL` isn't set, follow the [instruction](/docs/guides/bookinfo/#determining-the-ingress-ip-and-port).
+1.  Open the Bookinfo URL (`http://$GATEWAY_URL/productpage`) in your browser. Recall that `GATEWAY_URL`
+    should have been set using [these instructions](/docs/guides/bookinfo/#determining-the-ingress-ip-and-port)
+    when the Bookinfo sample was deployed.
 
     You should see the Bookinfo application productpage displayed.
     Notice that the `productpage` is displayed with no rating stars since `reviews:v1` does not access the ratings service.