* Docs fixed product naming - KeyVault vs Key Vault

* Docs fixed product naming - KeyVault vs Key Vault

Author: benkelly

docs/content/en/deep-dives/cmk.md

@@ -40,7 +40,7 @@ For these cases, a [Managed HSM](https://docs.microsoft.com/en-us/azure/key-vaul
 This can support importing KEKs from an [onsite HSM](https://docs.microsoft.com/en-us/azure/key-vault/managed-hsm/hsm-protected-keys-byok) that ensures the import
 never leaves a HSM boundary, while allowing customers to have secure external backups of the key.
 
-As Managed HSMs use a similar API to KeyVault, any changes needed to  use a Managed HSM would be minimal.
+As Managed HSMs use a similar API to Key Vault, any changes needed to  use a Managed HSM would be minimal.
 
 For lower security requirements, software backed encryption keys can also be used for CMK, for reduced cost, and easier, but less secure backup.
 

docs/content/en/deep-dives/key-vault.md

@@ -20,19 +20,19 @@ For more information on Azure Key Vault RBAC please refer to the [product docume
 
 ### Azure Spring PropertySource
 
-Each of the upstream Spring based applications has been configured to use a Azure KeyVault Spring PropertySource. This allows the applications to load certain Spring properties from KeyVault, however it requires us to use a specific naming pattern for the KeyVault items. The table below shows which naming pattern is used for each key.
+Each of the upstream Spring based applications has been configured to use a Azure Key Vault Spring PropertySource. This allows the applications to load certain Spring properties from Key Vault, however it requires us to use a specific naming pattern for the KeyVault items. The table below shows which naming pattern is used for each key.
 
 See the [Azure Key Vault Secrets Spring Boot starter client library for Java documentation](https://github.com/Azure/azure-sdk-for-java/tree/3f31d68eed6fbe11516ca3afe3955c8840a6e974/sdk/spring/azure-spring-boot-starter-keyvault-secrets) and [algorithm](https://github.com/Azure/azure-sdk-for-java/blob/3f31d68eed6fbe11516ca3afe3955c8840a6e974/sdk/spring/azure-spring-boot/src/main/java/com/azure/spring/keyvault/KeyVaultOperation.java#L165-L177) for more details.
 
 ### Azure Key Vault Provider for Secrets Store CSI Driver (AKS)
 
 The Azure Key Vault provider for Secrets Store CSI driver allows us to get secret contents stored in an Azure Key Vault instance and use the Secrets Store CSI driver interface to mount them into Kubernetes Pods.
 
-This reference architecture uses this CSI Driver to mount the various certificates into the approperiate Kubernetes Pod's filesystem. This method was chosen as it reduced the number of upstream code changes necessary, however, ideally this would be replaced with direct integration with KeyVault, discussed in the next section below.
+This reference architecture uses this CSI Driver to mount the various certificates into the approperiate Kubernetes Pod's filesystem. This method was chosen as it reduced the number of upstream code changes necessary, however, ideally this would be replaced with direct integration with Key Vault, discussed in the next section below.
 
 For more information on this CSI driver please refer to the [upstream documentation](https://github.com/Azure/secrets-store-csi-driver-provider-azure).
 
-### Future: Direct integration of KeyVault into the upstream applications
+### Future: Direct integration of Key Vault into the upstream applications
 
 Ideally, each of the upstream applications would never require access to read the various certificate private keys from Key Vault and they would instead integrate directly with the Key Vault sigining APIs. This would significantly reduce the risk of accidentally exposing private keys in the event of a misconfigration, malware, breach or other security incident by storing the Private Keys in a non-exportable HSM backed key.
 

docs/content/en/terraform/ie.md

@@ -107,7 +107,7 @@ description: >
 | <a name="input_tenant_id"></a> [tenant\_id](#input\_tenant\_id) | Tenant to deploy into | `string` | n/a | yes |
 | <a name="input_businessrule_service_version"></a> [businessrule\_service\_version](#input\_businessrule\_service\_version) | Version Number of the Business Rules Service | `string` | `"1.1.2-b0be8f4-azure-0.0.1-1293959"` | no |
 | <a name="input_enable_log_analytics_workspace"></a> [enable\_log\_analytics\_workspace](#input\_enable\_log\_analytics\_workspace) | Enable the creation of azurerm\_log\_analytics\_workspace and azurerm\_log\_analytics\_solution or not | `bool` | `false` | no |
-| <a name="input_generation"></a> [generation](#input\_generation) | Generation number to be appended to certain resource names (e.g. Purge Protected KeyVault's). Changing this value can only be done during a fresh deployment. | `number` | `1` | no |
+| <a name="input_generation"></a> [generation](#input\_generation) | Generation number to be appended to certain resource names (e.g. Purge Protected Key Vault's). Changing this value can only be done during a fresh deployment. | `number` | `1` | no |
 | <a name="input_issuance_service_version"></a> [issuance\_service\_version](#input\_issuance\_service\_version) | Version Number of the Issuance Service | `string` | `"1.0.5-7408b55-azure-0.0.1-1293959"` | no |
 | <a name="input_issuance_web_version"></a> [issuance\_web\_version](#input\_issuance\_web\_version) | Version Number of the Issuance Web | `string` | `"1.1.2-45daa28-azure-0.0.1-1293959"` | no |
 | <a name="input_log_analytics_cluster_id"></a> [log\_analytics\_cluster\_id](#input\_log\_analytics\_cluster\_id) | Enable the sending of Azure Log Workspace to Log Analytics Analytics Custer ID supplied | `string` | `null` | no |

docs/content/en/terraform/variables.md

@@ -45,7 +45,7 @@ enable_log_analytics_workspace = false
 # Version Number of the Gateway
 gateway_version = "1.1.3-44c8778-azure-0.0.1-5f09fbf"
 
-# Generation number to be appended to certain resource names (e.g. Purge Protected KeyVault's). Changing this value can only be done during a fresh deployment.
+# Generation number to be appended to certain resource names (e.g. Purge Protected Key Vault's). Changing this value can only be done during a fresh deployment.
 generation = 1
 
 # GitHub Container Registry Password
@@ -103,7 +103,7 @@ businessrule_service_version = "1.1.2-b0be8f4-azure-0.0.1-1293959"
 # Enable the creation of azurerm_log_analytics_workspace and azurerm_log_analytics_solution or not
 enable_log_analytics_workspace = false
 
-# Generation number to be appended to certain resource names (e.g. Purge Protected KeyVault's). Changing this value can only be done during a fresh deployment.
+# Generation number to be appended to certain resource names (e.g. Purge Protected Key Vault's). Changing this value can only be done during a fresh deployment.
 generation = 1
 
 # GitHub Container Registry Password