Merge pull request #281173 from Akhilesh-microsoft/ACA/environment_custom_dns_suffix

[ACA: Environment-custom-suffix]: 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/environment-custom-dns-suffix.md

@@ -5,19 +5,19 @@ services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.topic: how-to
-ms.date: 10/13/2022
+ms.date: 07/18/2024
 ms.author: cshoe
 ---
 
 # Custom environment DNS Suffix in Azure Container Apps
 
-By default, an Azure Container Apps environment provides a DNS suffix in the format `<UNIQUE_IDENTIFIER>.<REGION_NAME>.azurecontainerapps.io`. Each container app in the environment generates a domain name based on this DNS suffix. You can configure a custom DNS suffix for your environment.
+Azure Container Apps environment provides a default DNS suffix in the format `<UNIQUE_IDENTIFIER>.<REGION_NAME>.azurecontainerapps.io`. Each container app in the environment generates a domain name based on this DNS suffix. You can configure a custom DNS suffix for your environment.
 
 > [!NOTE]
 > 
 > To configure a custom domain for individual container apps, see [Custom domain names and certificates in Azure Container Apps](custom-domains-certificates.md).
 >
-> If you configure a custom DNS suffix for your environment, traffic to FQDNs that use this suffix will resolve to the environment. FQDNs that use this suffix outside the environment will be unreachable from the environment.
+> If you configure a custom DNS suffix for your environment, traffic to FQDNs (Fully Qualified Domain Names) that use this suffix will resolve to the environment. FQDNs that use this suffix outside of the environment are unreachable.
 
 ## Add a custom DNS suffix and certificate
 
@@ -27,7 +27,7 @@ By default, an Azure Container Apps environment provides a DNS suffix in the for
 
 1. In **DNS suffix**, enter the custom DNS suffix for the environment.
 
-    For example, if you enter `example.com`, the container app domain names will be in the format `<APP_NAME>.example.com`.
+    For example, if you enter `example.com`, the container app domain names are in the format `<APP_NAME>.example.com`.
 
 1. In a new browser window, go to your domain provider's website and add the DNS records shown in the *Domain validation* section to your domain.
 
@@ -36,7 +36,7 @@ By default, an Azure Container Apps environment provides a DNS suffix in the for
     | A | `*.<DNS_SUFFIX>` | Environment inbound IP address | Wildcard record configured to the IP address of the environment. |
     | TXT | `asuid.<DNS_SUFFIX>` | Validation token | TXT record with the value of the validation token (not required for Container Apps environment with internal load balancer). |
 
-1. Back in the *Custom DNS suffix* window, in **Certificate file**, browse and select a certificate for the TLS binding.
+1. Back in the *Custom DNS suffix* windows, in Certificate file, browse, and select a certificate for the TLS binding.
 
     > [!IMPORTANT]
     > You must use an existing wildcard certificate that's valid for the custom DNS suffix you provided.
@@ -45,7 +45,7 @@ By default, an Azure Container Apps environment provides a DNS suffix in the for
 
 1. Select **Save**.
 
-Once the save operation is complete, the environment is updated with the custom DNS suffix and TLS certificate.
+Once the saved operation is complete, the environment is updated with the custom DNS suffix and TLS certificate.
 
 ## Next steps