From 3d5ed417c6734bf35fb677ce9249a85a561beb1c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Florin=20C=C4=83t=C4=83lin=20=C8=9Aiucra-Popa?=
 <106736683+FlorinTP@users.noreply.github.com>
Date: Fri, 2 Sep 2022 18:01:29 +0200
Subject: [PATCH] Update pkcs11.mdx (#16994)

---
 website/content/docs/configuration/seal/pkcs11.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/configuration/seal/pkcs11.mdx b/website/content/docs/configuration/seal/pkcs11.mdx
index 74d4321573b9..c743cd3d42b0 100644
--- a/website/content/docs/configuration/seal/pkcs11.mdx
+++ b/website/content/docs/configuration/seal/pkcs11.mdx
@@ -8,7 +8,7 @@ description: |-
 
 # `pkcs11` Seal
 
--> **Note:** The Seal Wrap functionality is enabled by default. For this reason, HSM must be available throughout Vault's runtime and not just during the unseal process. Refer to the [Seal Wrap](/docs/enterprise/sealwrap) documenation for more information.
+-> **Note:** The Seal Wrap functionality is enabled by default. For this reason, HSM must be available throughout Vault's runtime and not just during the unseal process. Refer to the [Seal Wrap](/docs/enterprise/sealwrap) documentation for more information.
 
 The PKCS11 seal configures Vault to use an HSM with PKCS11 as the seal wrapping
 mechanism. Vault Enterprise's HSM PKCS11 support is activated by one of the