From 96c35b3ab75a8a44f285a06abb7c7067fc93944e Mon Sep 17 00:00:00 2001
From: hc-github-team-secure-vault-core
 <82990506+hc-github-team-secure-vault-core@users.noreply.github.com>
Date: Tue, 25 Jul 2023 14:59:24 -0400
Subject: [PATCH] backport of commit df05956e2bc8907c7c1d36d64875362e60457778
 (#22054)

Co-authored-by: carlosvilleg <136353783+carlosvilleg@users.noreply.github.com>
---
 website/content/docs/enterprise/hsm/behavior.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/enterprise/hsm/behavior.mdx b/website/content/docs/enterprise/hsm/behavior.mdx
index f7496413c..a512a4de3 100644
--- a/website/content/docs/enterprise/hsm/behavior.mdx
+++ b/website/content/docs/enterprise/hsm/behavior.mdx
@@ -46,7 +46,7 @@ encryption key are supported when using an HSM.
 
 ## Performance and availability
 
-When an HSM is used for generating various CSPs or for entropy augmentation,
+When an HSM is used for generating various Critical Security Parameters (CSPs) or for entropy augmentation,
 interaction with the HSM becomes part of the request processing for
 functionality using it. This means the HSM must be online and available for
 those requests to succeed. Additionally, some operations are performed much