Merge pull request #280686 from Akhilesh-microsoft/ACA/Connect_apps

[ACA: Connect-apps]: Verified the article for links and freshness, reviewed the content, verified all the editorial parameters. Article seems good. Updated ms.date

Author: prmerger-automator[bot]

articles/container-apps/connect-apps.md

@@ -5,15 +5,15 @@ services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.topic: conceptual
-ms.date: 11/02/2021
+ms.date: 07/12/2024
 ms.author: cshoe
 ---
 
 # Connect applications in Azure Container Apps
 
-Azure Container Apps exposes each container app through a domain name if [ingress](ingress-overview.md) is enabled. Ingress endpoints can be exposed either publicly to the world and to other container apps in the same environment, or ingress can be limited to only other container apps in the same [environment](environment.md).
+Azure Container Apps exposes each container app through a domain name if [ingress](ingress-overview.md) is enabled. You can expose ingress endpoints either publicly to the world or to the other container apps in the same environment. Alternatively, you can limit ingress to only other container apps in the same [environment](environment.md).
 
-You can call other container apps in the same environment from your application code using one of the following methods: 
+Application code can call other container apps in the same environment using one of the following methods: 
 
 - default fully qualified domain name (FQDN)
 - a custom domain name
@@ -41,7 +41,7 @@ The following diagram shows how these values are used to compose a container app
 
 ## Dapr location
 
-Developing microservices often requires you to implement patterns common to distributed architecture. Dapr allows you to secure microservices with mutual TLS (client certificates), trigger retries when errors occur, and take advantage of distributed tracing when Azure Application Insights is enabled.
+Developing microservices often requires you to implement patterns common to distributed architecture. Dapr allows you to secure microservices with mutual Transport Layer Security (TLS) (client certificates), trigger retries when errors occur, and take advantage of distributed tracing when Azure Application Insights is enabled.
 
 A microservice that uses Dapr is available through the following URL pattern: