From ba0c7d00f8ee8022b1fcb644be4600db309014ec Mon Sep 17 00:00:00 2001
From: Danny Knights <48058211+dannyjknights@users.noreply.github.com>
Date: Thu, 21 Mar 2024 20:23:01 +0000
Subject: [PATCH] backport of commit 356838d73525725f7ffc16336885b1fceb359eba

---
 website/content/docs/integrations/vault/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/integrations/vault/index.mdx b/website/content/docs/integrations/vault/index.mdx
index c20c6631bb..8252bd0f8f 100644
--- a/website/content/docs/integrations/vault/index.mdx
+++ b/website/content/docs/integrations/vault/index.mdx
@@ -53,7 +53,7 @@ Vault is configured to act as the certificate authority (CA), to ensure that the
 
 `/sign` - The Boundary controllers generate the key pair and then send it to Vault to sign.
 
-When you connect to a target, which uses Vault for dynamic SSH certificates, a new certificate is generated for every target connection. As long as the target trusts the CA, then access is granted without you having any visibility into the credentials involved.
+When you connect to a target that uses Vault for dynamic SSH certificates, a new certificate is generated for every target connection. As long as the target trusts the CA, then access is granted without you having any visibility into the credentials involved.
 
 # Vault clients