PR for #686 for setup section (#584)

* add another q for setup k8s FAQ #686

* additional consul FAQ tweaks #686

* clean up

* adding the prerequisites link #686

* minor cleanup

* add a clarification step

_docs/setup/consul/faq.md

@@ -3,7 +3,6 @@ title: FAQ
 overview: Frequently asked questions, current limitations and troubleshooting tips.
 
 order: 100
-draft: true
 
 layout: docs
 type: markdown
@@ -11,10 +10,10 @@ type: markdown
 
 {% include home.html %}
 
-* _My application isn't working, where can I start by debugging this?_
+* _My application isn't working, where can I troubleshoot this?_
 
   Please ensure all required containers are running: etcd, istio-apiserver, consul, registrator, pilot.  If one of them is not running, you may find the {containerID} using `docker ps -a` and then use `docker logs {containerID}` to read the logs.   
   
 * _How do I unset the context changed by istioctl at the end?_
 
-  Your kubectl is switched to use the istio context at the end of the `istio context-create` command.  You can use ```kubectl config use-context {desired-context}``` to switch to use your desired context.
+  Your ```kubectl``` is switched to use the istio context at the end of the `istio context-create` command.  You can use ```kubectl config get-contexts``` to obtain the list of contexts and ```kubectl config use-context {desired-context}``` to switch to use your desired context.

_docs/setup/consul/quick-start.md

@@ -65,9 +65,8 @@ Quick Start instructions to install and configure Istio in a Docker Compose setu
    ```bash
    docker ps -a
    ```
-
-   > If the `Istio-Pilot` container terminates, re-run the command from the previous step.
-
+   > If the `Istio-Pilot` container terminates, ensure that you run the `istioctl context-create` comamnd and re-run the command from the previous step.
+    
 1. Configure `istioctl` to use mapped local port for the Istio API server:
 
     ```bash
@@ -88,7 +87,7 @@ installation like [BookInfo]({{home}}/docs/guides/bookinfo.html).
 > Note 2: the application must use HTTP/1.1 or HTTP/2.0 protocol for all its HTTP traffic because HTTP/1.0 is not supported.
 
 ```bash
-docker-compose -f <your-app-spec>.yaml up -d)
+docker-compose -f <your-app-spec>.yaml up -d
 ```
 
 ## Uninstalling

_docs/setup/kubernetes/faq.md

@@ -9,15 +9,19 @@ type: markdown
 ---
 {% include home.html %}
 
-* _How do I check if my cluster has enabled the alpha features required for automatic sidecar injection?_
+* _How do I check if my cluster has enabled the alpha feature required for automatic sidecar injection?_
 
-  Automatic sidecar injection requires the [initilizer alpha feature] (https://kubernetes.io/docs/admin/extensible-admission-controllers/#enable-initializers-alpha-feature).
+  Automatic sidecar injection requires the [initilizer alpha feature](https://kubernetes.io/docs/admin/extensible-admission-controllers/#enable-initializers-alpha-feature).
   Run the following command to check if the initializer has been enabled (empty output indicates that initializers are not enabled):
  
   ```bash
   kubectl api-versions | grep admissionregistration
   ```
 
+* _Automatic sidecar injection doesn't work for my microservice, how can I debug this?_
+  
+  Please ensure your cluster has met the [prerequisites](automatic-sidecar-inject.html#prerequisites) for the automatic sidecar injection.  If your microservice is deployed in kube-system, kube-public or istio-system namespaces, they are exempted from automatic sidecar injection.  Please use a different namespace instead.
+  
 * _Can I migrate an existing installation from Istio v0.1.x to v0.2.x?_
   
   Upgrading from Istio 0.1.x to 0.2.x is not supported. You must uninstall Istio v0.1, _including pods with Istio sidecars_ and start with a fresh install of Istio v0.2.