added conditional rendering

Author: marciocloudflare

src/content/partials/networking-services/reference/traffic-steering.mdx

@@ -160,7 +160,12 @@ The following table exemplifies how to use geographic scoping for routes:
 
 When there are multiple routes to the same prefix with equal priority, and those routes are assigned to different geographic regions (like WNAM and ENAM), traffic entering the network in a specific region — for example, WNAM — will egress through the route associated with that same region.
 
-<Render file="routing/anycast-warning" product="networking-services" />
+{ props.magicWord === "Magic Transit" && (
+  <>
+		<Render file="routing/anycast-warning" product="networking-services" />
+	</>
+)
+}
 
 ### Region codes and associated regions
 

src/content/partials/networking-services/routing/configure-routes.mdx

@@ -19,7 +19,12 @@ Refer to <a href={props.trafficSteeringPage}>Traffic Steering</a> for more infor
 - Regional scoping of traffic to reduce latency
 - BGP peering
 
-<Render file="routing/anycast-warning" product="networking-services" />
+{ props.magicWord === "Magic Transit" && (
+  <>
+		<Render file="routing/anycast-warning" product="networking-services" />
+	</>
+)
+}
 
 ## Configure static routes
 

src/content/partials/networking-services/routing/configure-tunnels.mdx

@@ -43,7 +43,12 @@ To configure the tunnels between Cloudflare and your locations, you must provide
 
 You can use GRE or IPsec tunnels to onboard your traffic to {props.productName}, and set them up via the Cloudflare dashboard or the API. However, if you want to use the API, be sure to have your [account ID](/fundamentals/account/find-account-and-zone-ids/) and [API key](/fundamentals/api/get-started/keys/#view-your-global-api-key) ready before you begin.
 
-<Render file="routing/anycast-warning" product="networking-services" />
+{ props.magicWord === "Magic Transit" && (
+  <>
+		<Render file="routing/anycast-warning" product="networking-services" />
+	</>
+)
+}
 
 #### IPsec supported ciphers