Update streaming-endpoint-concept.md

Author: Juliako

articles/media-services/latest/streaming-endpoint-concept.md

@@ -135,7 +135,11 @@ A single streaming endpoint can stream both live and on-demand videos and most c
 * To handle case of the streaming endpoint (origin) not being available or not having the requested content.
 * Each reserved unit allows for 200 Mbps of bandwidth. If you need more than 2,000 Mbps (2 Gbps) of bandwidth, you could use the second streaming endpoint and load balance to give you additional bandwidth.
 
-    However, CDN is the best way to achieve scale out for streaming content but if you are delivering so much content that the CDN is pulling more than 2 Gbps then you can add additional streaming endpoints (origins). In this case you would need to hand out content URLs that are balanced across the two streaming endpoints. This approach gives better caching than trying to send requests to each origin randomly (for example, via a traffic manager).
+    However, CDN is the best way to achieve scale out for streaming content but if you are delivering so much content that the CDN is pulling more than 2 Gbps then you can add additional streaming endpoints (origins). In this case you would need to hand out content URLs that are balanced across the two streaming endpoints. This approach gives better caching than trying to send requests to each origin randomly (for example, via a traffic manager). 
+    
+    > [!TIP]
+    > Usually if the CDN is pulling more than 2 Gbps then something might be misconfigured (for example, no origin shielding).
+    
 * Load balancing different CDN providers. For example, you could set up the default streaming endpoint to use the Verizon CDN and create a second one to use Akamai. Then add some load balancing between the two to achieve multi-CDN balancing. 
 
     However, customer often do load balancing across multiple CDN providers using a single origin.