diff --git a/CHANGELOG.md b/CHANGELOG.md
index eaab2a723f..b1a39cdd94 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -70,7 +70,7 @@ BUG FIXES:
 
 KNOWN ISSUES:
 
-* connect: A not-consistently-reproducible issue can cause some service instances to lose their ability to communicate in the mesh after 72 hours (LeafCertTTL) due to a problem with leaf certificate rotation. We are working to address this issue in an upcoming patch release. To err on the side of caution, service mesh deployments should not upgrade to Consul 1.15 at this time. Refer to [[GH-16779](https://github.com/hashicorp/consul/issues/16779)] for the latest information.
+* connect: An issue with leaf certificate rotation can cause some service instances to lose their ability to communicate in the mesh after 72 hours (LeafCertTTL). This issue is not consistently reproducible. We are working to address this issue in an upcoming patch release. To err on the side of caution, service mesh deployments should not upgrade to Consul v1.15 at this time. Refer to [[GH-16779](https://github.com/hashicorp/consul/issues/16779)] for the latest information.
 
 BREAKING CHANGES:
 
diff --git a/website/content/docs/release-notes/consul/v1_15_x.mdx b/website/content/docs/release-notes/consul/v1_15_x.mdx
index cc12b9292a..5611caf33c 100644
--- a/website/content/docs/release-notes/consul/v1_15_x.mdx
+++ b/website/content/docs/release-notes/consul/v1_15_x.mdx
@@ -66,7 +66,7 @@ For more detailed information, please refer to the [upgrade details page](/consu
 
 ## Known Issues
 
-The following issues are known to exist in the v1.15 release:
+The following issues are known to exist in the v1.15.x releases:
 
 - All current 1.15.x versions are under investigation for a not-consistently-reproducible
   issue that can cause some service instances to lose their ability to communicate in the mesh after
@@ -74,7 +74,7 @@ The following issues are known to exist in the v1.15 release:
   due to a problem with leaf certificate rotation.
   We will update this section with more information as our investigation continues,
   including the target availability for a fix.
-  Refer to [Github#16779](https://github.com/hashicorp/consul/issues/16779)
+  Refer to [GH-16779](https://github.com/hashicorp/consul/issues/16779)
   for the latest information.
 
 - For v1.15.0, Consul is reporting newer releases of Envoy (for example, v1.25.1) as not supported, even though these versions are listed as valid in the [Envoy compatilibity matrix](/consul/docs/connect/proxies/envoy#envoy-and-consul-client-agent). The following error would result for newer versions of Envoy:
diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx
index c87f2d2eb8..936a4cec49 100644
--- a/website/content/docs/upgrading/upgrade-specific.mdx
+++ b/website/content/docs/upgrading/upgrade-specific.mdx
@@ -19,7 +19,7 @@ upgrade flow.
 #### Service mesh known issue
 
 To err on the side of caution,
-service mesh deployments should not upgrade to Consul 1.15 at this time.
+service mesh deployments should not upgrade to Consul v1.15 at this time.
 
 We are currently investigating a not-consistently-reproducible issue that can cause
 some service instances to lose their ability to communicate in the mesh after
@@ -28,8 +28,8 @@ due to a problem with leaf certificate rotation.
 We will update this section with more information as our investigation continues,
 including the target availability for a fix.
 
-If you are already operating Consul 1.15, refer to discussion of this issue on
-[Github#16779](https://github.com/hashicorp/consul/issues/16779)
+If you are already operating Consul v1.15, refer to discussion of this issue on
+[GH-16779](https://github.com/hashicorp/consul/issues/16779)
 for potential workarounds and to share your observations.
 
 #### Removing configuration options