Update website/content/docs/k8s/deployment-configurations/vault/data-…

…integration/index.mdx Co-authored-by: Jeff Boruszak <[email protected]>
hashicorp · Jan 5, 2024 · 7f4d59e · 7f4d59e
1 parent edbe09b
commit 7f4d59e
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/...ite/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx b/...ite/content/docs/k8s/deployment-configurations/vault/data-integration/index.mdx
@@ -93,7 +93,7 @@ For example, if your Consul on Kubernetes servers need access to [Consul Server
     1. Enterprise License
 
       <Note>
-      When using Vault Key-Value Version 2 secrets engines, the `data` field is implicitly required for Vault API calls in the form of "vault-kv2-mount-path/**data**/secret-path". In this example, the key-value data in `consul-kv/secret/enterpriselicense` is accessible for API calls via the `consul-kv/data/secret/enterpriselicense` path.
+      Vault API calls to version 2 of the Key-Value secrets engine require the `data` field in the path configuration. In the following example, the key-value data in `consul-kv/secret/enterpriselicense` becomes accessible for Vault API calls on the `consul-kv/data/secret/enterpriselicense` path.
       </Note>
 
       <CodeBlockConfig filename="license-policy.hcl">