Calls: Add note near TURN limits clarifying that limits are per allocation (#19747)

Author: renandincer

src/content/docs/calls/turn/faq.mdx

@@ -11,9 +11,9 @@ sidebar:
 
 Cloudflare TURN pricing is based on the data sent from the Cloudflare edge to the TURN client, as described in [RFC 8656 Figure 1](https://datatracker.ietf.org/doc/html/rfc8656#fig-turn-model). This means data sent from the TURN server to the TURN client and captures all data, including TURN overhead, following successful authentication.
 
-Pricing for Cloudflare Calls Serverless SFU and TURN services is $0.05 per GB of data used.
+Pricing for Cloudflare Calls TURN service is $0.05 per GB of data used.
 
-There is a free tier of 1,000 GB before any charges start. This free tier includes both Serverless SFU and TURN services. Cloudflare Calls billing appears as a single line item on your Cloudflare bill, covering both SFU and TURN.
+There is a free tier of 1,000 GB before any charges start. Cloudflare Calls billing appears as a single line item on your Cloudflare bill, covering both SFU and TURN.
 
 Traffic between Cloudflare Calls TURN and Cloudflare Calls SFU or Cloudflare Stream (WHIP/WHEP) does not incur any charges.
 

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

@@ -26,7 +26,7 @@ Use of alternate port 53 only by itself is not reccomended. Port 53 is blocked b
 
 Calls TURN service is available in every Cloudflare data center.
 
-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.
 
 To learn more about the architecture that makes this possible, read this [technical deep-dive about Calls](https://blog.cloudflare.com/cloudflare-calls-anycast-webrtc).
 
@@ -36,15 +36,15 @@ TLS versions supported include TLS 1.1, TLS 1.2, and TLS 1.3.
 
 | OpenSSL Name                  | TLS 1.1 | TLS 1.2 | TLS 1.3 |
 | ----------------------------- | ------- | ------- | ------- |
-| AEAD-AES128-GCM-SHA256        | No      | No      | ✅       |
-| AEAD-AES256-GCM-SHA384        | No      | No      | ✅       |
-| AEAD-CHACHA20-POLY1305-SHA256 | No      | No      | ✅       |
-| ECDHE-ECDSA-AES128-GCM-SHA256 | No      | ✅       | No      |
-| ECDHE-RSA-AES128-GCM-SHA256   | No      | ✅       | No      |
-| ECDHE-RSA-AES128-SHA          | ✅       | ✅       | No      |
-| AES128-GCM-SHA256             | No      | ✅       | No      |
-| AES128-SHA                    | ✅       | ✅       | No      |
-| AES256-SHA                    | ✅       | ✅       | No      |
+| AEAD-AES128-GCM-SHA256        | No      | No      | ✅      |
+| AEAD-AES256-GCM-SHA384        | No      | No      | ✅      |
+| AEAD-CHACHA20-POLY1305-SHA256 | No      | No      | ✅      |
+| ECDHE-ECDSA-AES128-GCM-SHA256 | No      | ✅      | No      |
+| ECDHE-RSA-AES128-GCM-SHA256   | No      | ✅      | No      |
+| ECDHE-RSA-AES128-SHA          | ✅      | ✅      | No      |
+| AES128-GCM-SHA256             | No      | ✅      | No      |
+| AES128-SHA                    | ✅      | ✅      | No      |
+| AES256-SHA                    | ✅      | ✅      | No      |
 
 ## MTU
 
@@ -54,10 +54,14 @@ There is no specific MTU limit for Cloudflare Calls TURN service.
 
 Cloudflare Calls TURN service places limits on:
 
-* Unique IP address you can communicate with per relay allocation (>5 new IP/sec)
-* Packet rate outbound and inbound to the relay allocation (>5-10 kpps)
-* Data rate outbound and inbound to the relay allocation (>50-100 Mbps)
+- Unique IP address you can communicate with per relay allocation (>5 new IP/sec)
+- Packet rate outbound and inbound to the relay allocation (>5-10 kpps)
+- Data rate outbound and inbound to the relay allocation (>50-100 Mbps)
 
-A relay allocation often represents a single TURN client connection with the TURN server, not all connections for a single customer.
+:::note[Limits apply to each TURN allocation independently]
+
+Each limit is for a single TURN allocation (single TURN user) and not account wide. Same limit will apply to each user regardless of the number of unique TURN users.
+
+:::
 
 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.