diff --git a/docs/multitenant-identity/key-vault.md b/docs/multitenant-identity/key-vault.md
index 4d6f056aa75..7930cfdef62 100644
--- a/docs/multitenant-identity/key-vault.md
+++ b/docs/multitenant-identity/key-vault.md
@@ -19,7 +19,7 @@ It's common to have application settings that are sensitive and must be protecte
 
 As a security best practice, you should never store these secrets in source control. It's too easy for them to leak — even if your source code repository is private. And it's not just about keeping secrets from the general public. On larger projects, you might want to restrict which developers and operators can access the production secrets. (Settings for test or development environments are different.)
 
-A more secure option is to store these secrets in [Azure Key Vault][KeyVault]. Key Vault is a cloud-hosted service for managing cryptographic keys and other secrets. This article shows how to use Key Vault to store configuration settings for you app.
+A more secure option is to store these secrets in [Azure Key Vault][KeyVault]. Key Vault is a cloud-hosted service for managing cryptographic keys and other secrets. This article shows how to use Key Vault to store configuration settings for your app.
 
 In the [Tailspin Surveys][Surveys] application, the following settings are secret: