From 4ff9fb3fd3909b12fa8889a5939e7f6ba43f5a7c Mon Sep 17 00:00:00 2001
From: ssurana90 <88379993+ssurana90@users.noreply.github.com>
Date: Fri, 18 Aug 2023 01:00:38 +0200
Subject: [PATCH] adding explanation for allow_store_key flag , based on
 internal engineering conversation. (#17258)

---
 website/content/api-docs/system/managed-keys.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/api-docs/system/managed-keys.mdx b/website/content/api-docs/system/managed-keys.mdx
index 9fac46db2c..4e6e867b8a 100644
--- a/website/content/api-docs/system/managed-keys.mdx
+++ b/website/content/api-docs/system/managed-keys.mdx
@@ -87,8 +87,8 @@ $ curl \
   a key into the configured backend even if a key is present, if set to false those operations are forbidden
   if a key exists.
 
-- `allow_store_key` `(string: "false")` - Controls the ability for Vault to import a key
-  to the configured backend, if "false" those operations will be forbidden.
+- `allow_store_key` `(string: "false")` - Controls the ability for Vault to export a Vault private key
+  to the configured HSM, if "false" those operations will be forbidden.
 
 - `any_mount` `(string: "false")` - Allow usage from any mount point within the namespace if "true". If "false"
   specific mount points will need their `allowed_managed_keys` parameter to be updated with the key name to