Update vs-key-vault-add-connected-service.md

Fixed typo.

Author: v-shils

articles/key-vault/general/vs-key-vault-add-connected-service.md

@@ -51,7 +51,7 @@ See code examples of working with secrets at [Azure Key Vault Secrets client lib
 
 ## Troubleshooting
 
-If your Key Vault is running on an different Microsoft account than the one you're logged in to Visual Studio (for example, the Key Vault is running on your work account, but Visual Studio is using your private account) you get an error in your Program.cs file, that Visual Studio can't get access to the Key Vault. To fix this issue:
+If your Key Vault is running on a different Microsoft account than the one you're logged in to Visual Studio (for example, the Key Vault is running on your work account, but Visual Studio is using your private account) you get an error in your Program.cs file, that Visual Studio can't get access to the Key Vault. To fix this issue:
 
 1. Go to the [Azure portal](https://portal.azure.com) and open your Key Vault.
 
@@ -130,4 +130,4 @@ Affects the project file .NET references and `packages.config` (NuGet references
 
 If you followed this tutorial, your Key Vault permissions are set up to run with your own Azure subscription, but that might not be desirable for a production scenario. You can create a managed identity to manage Key Vault access for your app. See [How to Authenticate to Key Vault](./authentication.md) and [Assign a Key Vault access policy](./assign-access-policy-portal.md).
 
-Learn more about Key Vault development by reading the [Key Vault Developer's Guide](developers-guide.md).
+Learn more about Key Vault development by reading the [Key Vault Developer's Guide](developers-guide.md).