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 fa1e015fe..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 manahed 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 [you managed identity name] -o json | ConvertFrom-Json
+    $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>
@@ -134,19 +134,19 @@ The above example uses secrets as plain strings. It is recommended to use a loca
     apiVersion: "aadpodidentity.k8s.io/v1"
     kind: AzureIdentity
     metadata:
-      name: [you managed identity name]
+      name: [your managed identity name]
     spec:
       type: 0
-      resourceID: [you managed identity id]
-      clientID: [you managed identity Client ID]
+      resourceID: [your managed identity id]
+      clientID: [your managed identity Client ID]
     ---
     apiVersion: "aadpodidentity.k8s.io/v1"
     kind: AzureIdentityBinding
     metadata:
-      name: [you managed identity name]-identity-binding
+      name: [your managed identity name]-identity-binding
     spec:
-      azureIdentity: [you managed identity name]
-      selector: [you managed identity selector]
+      azureIdentity: [your managed identity name]
+      selector: [your managed identity selector]
     ```
 
 10. Deploy the azure-identity-config.yaml:
diff --git a/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault.md b/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault.md
index db83a3a7d..555df3ea0 100644
--- a/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault.md
+++ b/daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault.md
@@ -88,7 +88,7 @@ The above example uses secrets as plain strings. It is recommended to use a loca
     }
     ```
 
-    **Save the both the appId and tenant from the output which will be used in the next step**
+    **Save both the appId and tenant from the output which will be used in the next step**
 
 4. Get the Object Id for [your_service_principal_name]