Clarify Realtime TURN service network details (#26520)

Updated description of the Realtime TURN service to clarify its operation on Cloudflare's global network and added a link for anycast routing.

Author: renandincer

src/content/docs/realtime/turn/index.mdx

@@ -24,9 +24,9 @@ Use of alternate port 53 only by itself is not recommended. Port 53 is blocked b
 
 ## Regions
 
-Realtime TURN service is available in every Cloudflare data center.
+Cloudflare Realtime TURN service runs on [Cloudflare's global network](https://www.cloudflare.com/network) - a growing global network of thousands of machines distributed across hundreds of locations, with the notable exception of the Cloudflare's [China Network](/china-network/).
 
-When a client tries to connect to `turn.cloudflare.com`, it _automatically_ connects to the Cloudflare location closest to them. We achieve this using anycast routing.
+When a client tries to connect to `turn.cloudflare.com`, it _automatically_ connects to the Cloudflare location closest to them. We achieve this using [anycast routing](https://www.cloudflare.com/learning/cdn/glossary/anycast-network/).
 
 To learn more about the architecture that makes this possible, read this [technical deep-dive about Realtime](https://blog.cloudflare.com/cloudflare-calls-anycast-webrtc).
 
@@ -64,4 +64,4 @@ Each limit is for a single TURN allocation (single TURN user) and not account wi
 
 :::
 
-These limits are suitable for high-demand applications and also have burst rates higher than those documented above. Hitting these limits will result in packet drops.
+These limits are suitable for high-demand applications and also have burst rates higher than those documented above. Hitting these limits will result in packet drops.