From 2bf279cf05f2998ed427900ff8b62edfcd3e9a0c Mon Sep 17 00:00:00 2001
From: Danny Knights <48058211+dannyjknights@users.noreply.github.com>
Date: Thu, 21 Mar 2024 20:27:39 +0000
Subject: [PATCH] backport of commit 4b3a2211c9aea87a585613d48fbf9ff9cfc6e4de

---
 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 ffb269f41a..7d1262b68a 100644
--- a/website/content/docs/integrations/vault/index.mdx
+++ b/website/content/docs/integrations/vault/index.mdx
@@ -57,7 +57,7 @@ When you connect to a target that uses Vault for dynamic SSH certificates, a new
 
 # Vault clients
 
-## Boundary and Vault for secrets management
+## Secrets management
 
 Within Boundary, you can configure one or more credential stores. This could be a dedicated credential store per Boundary project, and/or multiple credential stores within the same Boundary project. You can either configure the credential store as static, which is Boundary's native store, or by integrating it with HashiCorp Vault. The purpose of the credential store that is integrated with Vault is to fetch secrets from Vault on behalf of Boundary users.