diff --git a/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md b/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md
index 053c1de..4af9e8c 100644
--- a/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md
+++ b/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md
@@ -10,7 +10,7 @@ Despite an AKS created and kubectl and Azure CLI installed and configured to use
 
 You need to have helm installed on your machine, and Tiller must be installed on the AKS. Follow [these instructions](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/kubernetes-helm.md) to setup Helm and Tiller for AKS
 
-**Note** If your ASK cluster is not RBAC-enabled (default option in portal) you may receive following error when running a helm command:
+**Note**: If your ASK cluster is not RBAC-enabled (default option in portal) you may receive following error when running a helm command:
 
 ```
 Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp [::1]:8080: connect: connection refused
@@ -31,7 +31,7 @@ automountServiceAccountToken: false
 And change it to:
 
 ```
-automountServiceAccountToken: false
+automountServiceAccountToken: true
 ```
 
 Save the file and close the editor. This should reapply the deployment in the cluster. Now Helm commands should work.