From 65434c30a42d3fcaa2b2c032077f5b0e46d0f0cd Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Mon, 6 May 2024 16:37:44 -0400
Subject: [PATCH] Update configure-workers.mdx (#4772) (#4774)

Co-authored-by: soly-hashicorp <106975916+soly-hashicorp@users.noreply.github.com>
---
 website/content/docs/install-boundary/configure-workers.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/install-boundary/configure-workers.mdx b/website/content/docs/install-boundary/configure-workers.mdx
index 1ddf19adc5..2e856857bb 100644
--- a/website/content/docs/install-boundary/configure-workers.mdx
+++ b/website/content/docs/install-boundary/configure-workers.mdx
@@ -50,7 +50,7 @@ The worker-auth storage KMS key is used by a Worker for the encrypted storage of
 This is recommended Workers using controller-led or worker-led methods. If it is not specified, the authentication keys are not encrypted on disk.
 Optionally, if you deploy KMS authentication-driven Boundary workers, an additional KMS key must be generated to authenticate the Boundary worker with the controller.
 
-HashiCorp strongly recommends using the Key Management Ssytem (KMS) of the cloud provider where you deploy your Boundary workers.
+HashiCorp strongly recommends using the Key Management System (KMS) of the cloud provider where you deploy your Boundary workers.
 Keep in mind that Boundary workers must have the correct level of permissions for interacting with the cloud provider's KMS.
 Refer to your cloud provider's documentation, for more information.