diff --git a/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault-managed-identity.md b/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault-managed-identity.md
index 21c561f67..125277aa1 100644
--- a/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault-managed-identity.md
+++ b/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault-managed-identity.md
@@ -67,13 +67,13 @@ The above example uses secrets as plain strings. It is recommended to use a loca
 
 3. Create the managed identity(Optional)
    
-    This step is required only if the AKS Cluster is provisoned without the flag "--enable-managed-identity". If the cluster is provisioned with managed identity, than is suggested to use the autogenerated managed identity that is associated to the Resource Group MC_*.
+    This step is required only if the AKS Cluster is provisoned without the flag "--enable-managed-identity". If the cluster is provisioned with managed identity, than it is suggested to use the autogenerated managed identity that is associated to the Resource Group MC_*.
 
     ```bash
     $identity = az identity create -g [your resource group] -n [your managed identity name] -o json | ConvertFrom-Json
     ```
 
-    Below the command to retrieve the managed identity in the autogenerated scenario:
+    Below is the command to retrieve the managed identity in the autogenerated scenario:
 
       ```bash
       az aks show -g <AKSResourceGroup> -n <AKSClusterName>