diff --git a/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md b/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md
index ab7632e09..42e4eee16 100644
--- a/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md
+++ b/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md
@@ -6,7 +6,7 @@ weight: 2000
 description: "Use Redis as a backend state store"
 ---
 
-Dapr doesn't transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec]({{<ref state_api.md>}}). You can directly interact with the underlying store to manipulate the state data, such querying states, creating aggregated views and making backups.
+Dapr doesn't transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec]({{<ref state_api.md>}}). You can directly interact with the underlying store to manipulate the state data, such as querying states, creating aggregated views and making backups.
 
 >**NOTE:** The following examples uses Redis CLI against a Redis store using the default Dapr state store implementation.
 
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 06ae8a853..5613eba2c 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
@@ -102,16 +102,16 @@ description: How to configure Azure Key Vault and Kubernetes to use Azure Manage
       name: [you managed identity name]
     spec:
       type: 0
-      ResourceID: [you managed identity id]
-      ClientID: [you managed identity Client ID]
+      resourceID: [you managed identity id]
+      clientID: [you managed identity Client ID]
     ---
     apiVersion: "aadpodidentity.k8s.io/v1"
     kind: AzureIdentityBinding
     metadata:
       name: [you managed identity name]-identity-binding
     spec:
-      AzureIdentity: [you managed identity name]
-      Selector: [you managed identity selector]
+      azureIdentity: [you managed identity name]
+      selector: [you managed identity selector]
     ```
 
 10. Deploy the azure-identity-config.yaml: