Merge branch 'patch-11' of https://github.com/Harikrishnan-M-B/azure-docs-pr into afdbest

Author: duongau

articles/frontdoor/best-practices.md

@@ -15,13 +15,15 @@ This article summarizes best practices for using Azure Front Door.
 
 ## General best practices
 
-### Avoid combining Traffic Manager and Front Door
+### Avoid combining Traffic Manager and Front Door unless absolutely needed
 
-For most solutions, you should use *either* Front Door *or* [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md), but not both. Traffic Manager is a DNS-based load balancer. It sends traffic directly to your origin's endpoints. In contrast, Front Door terminates connections at points of presence (PoPs) near to the client and establishes separate long-lived connections to the origins. The products work differently and are intended for different use cases.
+For most solutions, it is recommended use *either* Front Door *or* [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md), but not both. Traffic Manager is a DNS-based load balancer. It sends traffic directly to your origin's endpoints. In contrast, Front Door terminates connections at points of presence (PoPs) near to the client and establishes separate long-lived connections to the origins. The products work differently and are intended for different use cases.
 
 If you need content caching and delivery (CDN), TLS termination, advanced routing capabilities, or a web application firewall (WAF), consider using Front Door. For simple global load balancing with direct connections from your client to your endpoints, consider using Traffic Manager. For more information about selecting a load balancing option, see [Load-balancing options](/azure/architecture/guide/technology-choices/load-balancing-overview).
 
-However, as part of a complex architecture, you might choose to use Traffic Manager in front of Front Door. In the unlikely event that Front Door is unavailable, Traffic Manager can route traffic to an alternative destination, such as Azure Application Gateway or a partner content delivery network (CDN). These architectures are difficult to implement and most customers don't need them.
+However, as part of a complex architecture that requires high availability, you can put use Traffic Manager in front of Front Door. In the unlikely event that Front Door is unavailable, Traffic Manager can then route traffic to an alternative destination, such as Azure Application Gateway or a partner content delivery network (CDN). Such architectures are difficult to implement and most customers don't need them. Refer to [mission-critical-content-delivery](/azure/architecture/guide/networking/global-web-applications/mission-critical-content-delivery) for more info. 
+
+Do not put Traffic Manager behind Front Door. Traffic Managers should be kept always in front of Front Door.
 
 ### Restrict traffic to your origins