addressed comments

Author: anraghun

articles/azure-arc/kubernetes/troubleshooting.md

@@ -144,7 +144,7 @@ If you get the above helm timeout issue, you can troubleshoot as follows:
       ```console
       kubectl get pods -n azure-arc
       ```
-  2. Check if the `clusterconnect-agent` or the `config-agent` pods are showing crashloopbackoff, or not all instances are running:
+  2. Check if the `clusterconnect-agent` or the `config-agent` pods are showing crashloopbackoff, or not all containers are running:
     
       ```output
       NAME                                        READY   STATUS             RESTARTS   AGE
@@ -163,7 +163,7 @@ If you get the above helm timeout issue, you can troubleshoot as follows:
       name: azure-identity-certificate
       ```
       This could be a transient issue. You can try deleting the Arc deployment by running the `az connectedk8s delete` command and reinstalling it. If you're consistently facing this, it could be an issue with your proxy settings. Please follow [these steps](./quickstart-connect-cluster.md#connect-using-an-outbound-proxy-server) to connect your cluster to Arc via a proxy.
-  4. If the `clusterconnect-agent` and the `config-agent` pods are running, but the `kube-aad-proxy` pod is missing, check your pod security policies. This pod requires hostpath mount but doesn't have admin permissions. This pod uses the `azure-arc-kube-aad-proxy-sa` service account.
+  4. If the `clusterconnect-agent` and the `config-agent` pods are running, but the `kube-aad-proxy` pod is missing, check your pod security policies. This pod uses the `azure-arc-kube-aad-proxy-sa` service account, which doesn't have admin permissions but requires the permission to mount host path.
   
 
 ### Helm validation error