Merge pull request #298133 from Harikrishnan-M-B/patch-35

Update front-door-faq.yml

Author: v-ccolin

articles/frontdoor/front-door-faq.yml

@@ -150,14 +150,14 @@ sections:
           To use Azure Front Door, you must have a public VIP or a DNS name that is publicly accessible. Azure Front Door uses the public IP to route the traffic to your origin. A common scenario is to deploy an Azure Load Balancer behind Front Door. You can also use Private Link with Azure Front Door Premium to connect to an internal load balancer. For more information, see [enable Private Link with internal load balancer](standard-premium/how-to-enable-private-link-internal-load-balancer.md).
 
       - question: |
-          Is it possible to configure Azure CDN behind my Front Door profile or the other way around?
+          Is it possible to configure Azure CDN behind my Front Door profile/endpoint or the other way around?
         answer:  |
           Azure Front Door and Azure CDN are two services that provide fast and reliable web delivery for your applications. However, they aren't compatible with each other, because they share the same network of Azure edge sites to deliver content to your users. This shared network causes conflicts between their routing and caching policies. Therefore, you have to choose either Azure Front Door or Azure CDN for your application, depending on your performance and security requirements.
 
       - question: |
-          Is it possible to configure Azure Front Door behind another Front Door profile or the other way around?
+          Is it possible to configure a Azure Front Door profile/endpoint behind another Front Door profile/endpoint or the other way around?
         answer:  |
-          The fact that both profiles would use the same Azure edge sites to handle incoming requests causes this limitation that prevents you from nesting one Azure Front Door profile behind another. This setup would cause routing conflicts and performance issues. Therefore, you should ensure that your Azure Front Door profiles are independent and not chained together, if you need to use multiple profiles for your applications.
+          The fact that both profiles/endpoints would use the same Azure edge POP to handle incoming requests causes a limitation that prevents you from nesting one Azure Front Door profile/endpoint behind another. This setup would cause routing conflicts and performance issues. Therefore, you should ensure that your Azure Front Door profiles/endpoints are  not chained together, if you need to use multiple profiles/endpoints for your applications.
 
   - name: Front Door IP addresses and service tags
     questions: