diff --git a/website/content/docs/concepts/security/data-encryption.mdx b/website/content/docs/concepts/security/data-encryption.mdx
index 87518900b..09dbafd2c 100644
--- a/website/content/docs/concepts/security/data-encryption.mdx
+++ b/website/content/docs/concepts/security/data-encryption.mdx
@@ -86,7 +86,7 @@ with the exception of resources that cannot themselves be deleted. (This
 consists of built-in anonymous (`u_anon`), authenticated (`u_auth`), and
 recovery (`u_recovery`) users and the `global` scope.). By initializing Boundary
 with the options to skip creating default resources, Terraform can be used to
-create the specfic resources needed instead, with the `recovery` KMS used to
+create the specific resources needed instead, with the `recovery` KMS used to
 authenticate setting up the initial auth method(s).
 
 ## The `config` KMS Key
@@ -98,4 +98,4 @@ configuration file, run `boundary config encrypt` to encrypt the file, and then
 safely pass the file to a change control system. Only another operator or system
 with access to that KMS can decrypt the values. Boundary will check for a
 `config` KMS block on startup, and if it exists, will use it to decrypt any
-encrypted values found at startup time.
\ No newline at end of file
+encrypted values found at startup time.