Update backend pool members description for clarity

Changed as suggested by Jaesoni.

Author: riturajc

articles/application-gateway/application-gateway-components.md

@@ -132,7 +132,7 @@ A backend pool routes request to backend servers, which serve the request. Backe
 - Internal IP addresses
 - FQDN (fully qualified domain names) or short names (single-label domain names), provided your DNS server can resolve them
 - Multitenant backends (such as App Service)
-- Azure Container Apps (see [Protect Container Apps with Application Gateway and WAF](../container-apps/waf-app-gateway.md))
+- Multitenant backends (such as Azure App Service, Azure Container Apps). (see [Protect Container Apps with Application Gateway and WAF](../container-apps/waf-app-gateway.md))
 
 Application Gateway backend pool members aren't tied to an availability set. An application gateway can communicate with instances outside of the virtual network that it's in. As a result, the members of the backend pools can be across clusters, across datacenters, or outside Azure, as long as there's IP connectivity.