diff --git a/website/content/docs/connect/proxies/integrate.mdx b/website/content/docs/connect/proxies/integrate.mdx
index ba72f1c6f0..c4c7765cd5 100644
--- a/website/content/docs/connect/proxies/integrate.mdx
+++ b/website/content/docs/connect/proxies/integrate.mdx
@@ -7,14 +7,14 @@ description: >-
 
 # Custom Proxy Configuration for Service Mesh
 
-~> **Note:** The Native App Integration does not support many of the Consul's service
- mesh features, and is not under active development.
- The [Envoy proxy](/consul/docs/connect/proxies/envoy) should be used for most production
- environments. The Connect Native Golang SDK and `v1/agent/connect/authorize`, `v1/agent/connect/ca/leaf`, 
+~> **Note:** The Connect Native Golang SDK and `v1/agent/connect/authorize`, `v1/agent/connect/ca/leaf`, 
  and `v1/agent/connect/ca/roots` APIs are deprecated and will be removed in a future release. Although Connect Native 
  is still supported we discourage new users from adopting this feature at this time, as we plan to remove the feature
  when a future long term replacement such as proxyless GRPC via XDS is delivered (see [GH-10339](https://github.com/hashicorp/consul/issues/10339)).
 
+ The Native App Integration does not support many of the Consul's service mesh features, and is not under active development.
+ The [Envoy proxy](/consul/docs/connect/proxies/envoy) should be used for most production environments. 
+
 This topic describes the process and API endpoints you can use to extend proxies for integration with Consul.
 
 ## Overview