added legacy hc

Author: marciocloudflare

src/content/docs/magic-transit/how-to/bgp-peering.mdx

@@ -13,5 +13,6 @@ import { Render } from "~/components"
 	params={{
 		productName: "Magic Transit",
 		productPath: "/magic-transit/reference/tunnel-health-checks/",
+		legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-health-checks-system"
 	}}
 />

src/content/docs/magic-wan/configuration/manually/how-to/bgp-peering.mdx

@@ -13,5 +13,6 @@ import { Render } from "~/components"
 	params={{
 		productName: "Magic WAN",
 		productPath: "/magic-wan/reference/tunnel-health-checks/",
+		legacyHCs: "/magic-wan/reference/tunnel-health-checks/#legacy-health-checks-system"
 	}}
 />

src/content/partials/network-interconnect/bgp-peering.mdx

@@ -18,7 +18,6 @@ With this functionality, customers can:
 - Secure the session by MD5 authentication to prevent misconfigurations.
 - Exchange routes dynamically between their devices and their Magic routing table.
 
-
 ## Route distribution and convergence
 
 Routes received from the customer device will be redistributed into the Magic routing table, which is used by both Magic WAN and Magic Transit.