From 6cb10b7de6b6cd57f44ba88b9405277a8b4ec24e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Antonio=20Fiuman=C3=B2?= Date: Mon, 7 Jun 2021 18:15:59 +0100 Subject: [PATCH] Fix typo in azure-keyvault-managed-identity.md (#1541) --- .../supported-secret-stores/azure-keyvault-managed-identity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md b/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md index f73f4ada5..55d4abd88 100644 --- a/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md +++ b/daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault-managed-identity.md @@ -13,7 +13,7 @@ To setup Azure Key Vault secret store with Managed Identies create a component o In Kubernetes mode, you store the certificate for the service principal into the Kubernetes Secret Store and then enable Azure Key Vault secret store with this certificate in Kubernetes secretstore. -The component yaml uses the name of your key vault and the Cliend ID of the managed identity to setup the secret store. +The component yaml uses the name of your key vault and the Client ID of the managed identity to setup the secret store. ```yaml apiVersion: dapr.io/v1alpha1