From af8aef88a50a09ef4462a7d7745162d29ecc26d3 Mon Sep 17 00:00:00 2001
From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com>
Date: Wed, 29 Nov 2023 11:06:51 -0800
Subject: [PATCH] Update website/content/docs/enterprise/fips.mdx

Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
---
 website/content/docs/enterprise/fips.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/enterprise/fips.mdx b/website/content/docs/enterprise/fips.mdx
index f2ce41cf6a..542f0b5b79 100644
--- a/website/content/docs/enterprise/fips.mdx
+++ b/website/content/docs/enterprise/fips.mdx
@@ -32,7 +32,7 @@ The FIPS 140-2 variant of Consul uses separate binaries that are available from
 
 The above naming conventions, which append `.fips1402` to binary names and tags, and `-fips` to registry names, also apply to `consul-k8s`, `consul-k8s-control-plane`, `consul-dataplane`, and `consul-ecs`, which are packaged separately from Consul Enterprise.
 
-### Cluster Peering support
+### Cluster peering support
 
 A Consul cluster running FIPS variants of Consul can peer with any combination of standard (non-FIPS) Consul clusters and FIPS Consul clusters. All peering-related features are supported between FIPS clusters and non-FIPS clusters.