From b1ed910da74f64f459524664b8e6237b1dc29ae4 Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Tue, 6 Aug 2024 13:41:11 -0400
Subject: [PATCH] docs: Fix broken anchor link in Credential management

---
 website/content/docs/concepts/credential-management.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/concepts/credential-management.mdx b/website/content/docs/concepts/credential-management.mdx
index aa27958b8b..ed9a73d253 100644
--- a/website/content/docs/concepts/credential-management.mdx
+++ b/website/content/docs/concepts/credential-management.mdx
@@ -10,7 +10,7 @@ description: |-
 When users connect to a remote machine, they typically need a set of credentials for authentication.
 After they connect to the machine, they may also require another set of credentials to access services or other machines within the network.
 
-There are two credential management paradigms in Boundary, [credential brokering](#credential-brokering) and [credential injection](#credential-injection-hcp-only).
+There are two credential management paradigms in Boundary, [credential brokering](#credential-brokering) and [credential injection](#credential-injection).
 
 To configure credential brokering or credential injection with static credentials, refer to [Manage static credentials with Boundary](/boundary/docs/configuration/credential-management/static-cred-boundary) and [Manage static credentials with Vault](/boundary/docs/configuration/credential-management/static-cred-vault).