From 9615482157a79d2cabe04d4ad3dbc69bc927a90d Mon Sep 17 00:00:00 2001
From: Rachel Culpepper <84159930+rculpepper@users.noreply.github.com>
Date: Tue, 21 Jun 2022 15:13:30 +0000
Subject: [PATCH] backport of commit f9532fed61bfe952c1c77c44df31ee2fd795dc89

---
 website/content/docs/secrets/transit.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/secrets/transit.mdx b/website/content/docs/secrets/transit.mdx
index ec19e6b9f568..451dfd29809e 100644
--- a/website/content/docs/secrets/transit.mdx
+++ b/website/content/docs/secrets/transit.mdx
@@ -257,11 +257,11 @@ as described below. In the below, the target key refers to the key being importe
 If the key is being imported from an HSM that supports PKCS#11, there are
 two possible scenarios:
 
-- If the HSM supports the CKM_AES_KEY_WRAP_KWP mechanism, that can be used to wrap the
+- If the HSM supports the CKM_RSA_AES_KEY_WRAP mechanism, that can be used to wrap the
 target key using the wrapping key.
 
 - Otherwise, two mechanisms can be combined to wrap the target key. First, an AES key should
-be generated and then used to wrap the target key using the CKM_AES_KEY_WRAP_PAD mechanism.
+be generated and then used to wrap the target key using the CKM_AES_KEY_WRAP_KWP mechanism.
 Then the AES key should be wrapped under the wrapping key using the CKM_RSA_PKCS_OAEP mechanism
 using MGF1 and either SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512.