From e7f044ca34c8992cf5612f7ca9aef42eb0547836 Mon Sep 17 00:00:00 2001
From: marciocloudflare <marcio@cloudflare.com>
Date: Thu, 19 Dec 2024 09:44:57 +0000
Subject: [PATCH] refined text

---
 src/content/partials/network-interconnect/bgp-peering.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/partials/network-interconnect/bgp-peering.mdx b/src/content/partials/network-interconnect/bgp-peering.mdx
index 7b1a188281c3233..fa4b7f7548ab5cc 100644
--- a/src/content/partials/network-interconnect/bgp-peering.mdx
+++ b/src/content/partials/network-interconnect/bgp-peering.mdx
@@ -39,7 +39,7 @@ BGP support currently has the following limitations:
 
 ## Tunnel health checks
 
-{props.productName} customers need to enable legacy <a href={props.legacyHCs}>bidirectional health checks</a> alongside BGP. This is essential to determine if a specific Cloudflare datacenter is reachable from a customer device or not. <a href={props.productPath}>Tunnel health checks</a> will modify the route's priorities for dynamically learned BGP routes.
+{props.productName} customers need to enable legacy <a href={props.legacyHCs}>health checks</a> alongside BGP. This is essential to determine if a specific Cloudflare data center is reachable from a customer device or not. <a href={props.productPath}>Tunnel health checks</a> will modify the route's priorities for dynamically learned BGP routes.
 
 ## How to choose an ASN for BGP peering