Address PR review team's comment

lilinvictorms · lilinvictorms · commit 657e2ed8e080 · 2022-06-03T00:03:42.000-07:00
diff --git a/articles/batch/batch-account-create-portal.md b/articles/batch/batch-account-create-portal.md
@@ -54,7 +54,7 @@ Once the account has been created, select the account to access its settings and
 > [!NOTE]
 > The name of the Batch account is its ID and can't be changed. If you need to change the name of a Batch account, you'll need to delete the account and create a new one with the intended name.
 
-:::image type="content" source="media/batch-account-create-portal/batch_blade.png" alt-text="Screenshot of the Batch account page in the Azure portal.":::
+:::image type="content" source="media/batch-account-create-portal/batch-blade.png" alt-text="Screenshot of the Batch account page in the Azure portal.":::
 
 When you develop an application with the [Batch APIs](batch-apis-tools.md#azure-accounts-for-batch-development), you need an account URL and key to access your Batch resources. (Batch also supports Azure Active Directory authentication.) To view the Batch account access information, select **Keys**.
 
diff --git a/articles/batch/batch-pool-no-public-ip-address.md b/articles/batch/batch-pool-no-public-ip-address.md
@@ -16,7 +16,7 @@ ms.custom: references_regions
 
 When you create an Azure Batch pool, you can provision the virtual machine configuration pool without a public IP address. This article explains how to set up a Batch pool without public IP addresses.
 
-## Why use a pool without public IP Addresses?
+## Why use a pool without public IP addresses?
 
 By default, all the compute nodes in an Azure Batch virtual machine configuration pool are assigned a public IP address. This address is used by the Batch service to schedule tasks and for communication with compute nodes, including outbound access to the internet.
 
diff --git a/articles/batch/manage-private-endpoint-connections.md b/articles/batch/manage-private-endpoint-connections.md
@@ -13,17 +13,17 @@ You can query and manage all existing private endpoint connections for your Batc
 - Reject a connection (either in pending or approved state).
 - Remove a connection, which will remove the connection from Batch account and mark the associated private endpoint resource as Disconnected state.
 
-## Azure Portal
+## Azure portal
 
 1. Go to your Batch account in Azure portal.
 1. In **Settings**, select **Networking** and go to tab **Private Access**.
 1. Select the private connection, then perform the Approve/Reject/Remove operation.
 
-   :::image type="content" source="media/private-connectivity/manage-private-connections.png" alt-text="Manage private endpoint connections":::
+   :::image type="content" source="media/private-connectivity/manage-private-connections.png" alt-text="Screenshot of managing private endpoint connections.":::
 
-## Az PowerShell
+## Az PowerShell module
 
-Examples using [Az PowerShell Networking module](/powershell/module/az.network#networking):
+Examples using Az PowerShell module [`Az.Network`](/powershell/module/az.network#networking):
 
 ```PowerShell
 $accountResourceId = "/subscriptions/<subscription>/resourceGroups/<rg>/providers/Microsoft.Batch/batchAccounts/<account>"
@@ -47,7 +47,7 @@ Remove-AzPrivateEndpointConnection -ResourceId $pecResourceId
 
 ## Azure CLI
 
-Examples using Azure CLI ([az network private-endpoint](/cli/azure/network/private-endpoint)):
+Examples using Azure CLI ([`az network private-endpoint`](/cli/azure/network/private-endpoint)):
 
 ```sh
 accountResourceId="/subscriptions/<subscription>/resourceGroups/<rg>/providers/Microsoft.Batch/batchAccounts/<account>"
diff --git a/articles/batch/media/batch-account-create-portal/batch-blade.png b/articles/batch/media/batch-account-create-portal/batch-blade.png
diff --git a/articles/batch/private-connectivity.md b/articles/batch/private-connectivity.md
@@ -34,11 +34,11 @@ Use the following steps to create a private endpoint with your Batch account usi
 
 1. Go to your Batch account in the Azure portal.
 2. In **Settings**, select **Networking** and go to the tab **Private Access**. Then, select **+ Private endpoint**.
-   :::image type="content" source="media/private-connectivity/private-endpoint-connections.png" alt-text="Private endpoint connections":::
+   :::image type="content" source="media/private-connectivity/private-endpoint-connections.png" alt-text="Screenshot of private endpoint connections.":::
 3. In the **Basics** pane, enter or select the subscription, resource group, private endpoint resource name and region details, then select **Next: Resource**.
-   :::image type="content" source="media/private-connectivity/create-private-endpoint-basics.png" alt-text="Create a private endpoint - Basics pane":::
+   :::image type="content" source="media/private-connectivity/create-private-endpoint-basics.png" alt-text="Screenshot of creating a private endpoint - Basics pane.":::
 4. In the **Resource** pane, set the **Resource type** to **Microsoft.Batch/batchAccounts**. Select the Batch account you want to access, select the target sub-resource, then select **Next: Configuration**.
-   :::image type="content" source="media/private-connectivity/create-private-endpoint.png" alt-text="Create a private endpoint - Resource pane":::
+   :::image type="content" source="media/private-connectivity/create-private-endpoint.png" alt-text="Screenshot of creating a private endpoint - Resource pane.":::
 5. In the **Configuration** pane, enter or select this information:
    - For **Virtual network**, select your virtual network.
    - For **Subnet**, select your subnet.
@@ -105,7 +105,7 @@ For details on costs related to private endpoints, see [Azure Private Link prici
 
 ## Current limitations and best practices
 
-When creating private endpoint with your Batch account, keep in mind the following:
+When creating a private endpoint with your Batch account, keep in mind the following:
 
 - Private endpoint resources with the sub-resource **batchAccount** must be created in the same subscription as the Batch account.
 - Resource movement is not supported for private endpoints with Batch accounts.
diff --git a/articles/batch/public-network-access.md b/articles/batch/public-network-access.md
@@ -9,7 +9,7 @@ ms.date: 05/26/2022
 
 By default, [Azure Batch accounts](accounts.md) have public endpoints and are publicly accessible. This article shows how to configure your Batch account to allow access from only specific public IP addresses or IP address ranges.
 
-IP network rules are configured on the public endpoints. IP network rules do not apply to private endpoints configured with [Private Link](private-connectivity.md).
+IP network rules are configured on the public endpoints. IP network rules don't apply to private endpoints configured with [Private Link](private-connectivity.md).
 
 Each endpoint supports a maximum of 200 IP network rules.
 
@@ -22,7 +22,7 @@ Batch accounts have two public endpoints:
 
 You can check both endpoints in account properties when you query the Batch account with [Batch Management REST API](/rest/api/batchmanagement/batch-account/get). You can also check them in the overview for your Batch account in the Azure portal:
 
-   :::image type="content" source="media/public-access/batch-account-endpoints.png" alt-text="Batch account endpoints":::
+   :::image type="content" source="media/public-access/batch-account-endpoints.png" alt-text="Screenshot of Batch account endpoints.":::
 
 You can configure public network access to Batch account endpoints with the following options:
 
@@ -36,7 +36,7 @@ You can configure public network access to Batch account endpoints with the foll
 1. Under **Settings**, select **Networking**.
 1. On the **Public access** tab, select to allow public access from **Selected networks**.
 1. Under access for each endpoint, enter a public IP address or address range in CIDR notation one by one.
-   :::image type="content" source="media/public-access/configure-public-access.png" alt-text="Configure public access with Batch account":::
+   :::image type="content" source="media/public-access/configure-public-access.png" alt-text="Screenshot of public access with Batch account.":::
 1. Select **Save**.
 
 > [!NOTE]
@@ -47,7 +47,7 @@ You can configure public network access to Batch account endpoints with the foll
 
 ## Disable public network access
 
-Optionally, disable public public network access to Batch account endpoints. Disabling the public network access overrides all IP network rules configurations. For example, you might want to disable public access to a Batch account secured in a virtual network using [Private Link](private-connectivity.md).
+Optionally, disable public network access to Batch account endpoints. Disabling the public network access overrides all IP network rules configurations. For example, you might want to disable public access to a Batch account secured in a virtual network using [Private Link](private-connectivity.md).
 
 1. In the portal, navigate to your Batch account and select **Settings > Networking**.
 1. On the **Public access** tab, select **Disabled**.
diff --git a/articles/batch/simplified-compute-node-communication.md b/articles/batch/simplified-compute-node-communication.md
@@ -1,8 +1,9 @@
 ---
 title: Use simplified compute node communication
-description: Learn how the Azure Batch service is simplifying the way Batch pool infrastructure is managed and how to opt in or out of the .
+description: Learn how the Azure Batch service is simplifying the way Batch pool infrastructure is managed and how to opt in or out of the feature.
 ms.topic: how-to
-ms.date: 10/21/2021
+ms.date: 06/02/2022
+ms.custom: references_regions
 ---
 
 # Use simplified compute node communication
@@ -15,7 +16,7 @@ This document describes forthcoming changes with how the Azure Batch service com
 > Support for simplified compute node communication in Azure Batch is currently in public preview. This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-Opting in is not required at this time. However, in the future, using simplified compute node communication will be required for all Batch accounts. At that time, an official retirement notice will be provided, with an opportunity to migrate your Batch pools before that happens.
+Opting in isn't required at this time. However, in the future, using simplified compute node communication will be required for all Batch accounts. At that time, an official retirement notice will be provided, with an opportunity to migrate your Batch pools before that happens.
 
 ## Supported regions
 
@@ -58,11 +59,11 @@ Simplified compute node communication helps reduce security risks by removing th
 
 The new model also provides more fine-grained data exfiltration control, since outbound communication to Storage.*region* is no longer required. You can explicitly lock down outbound communication to Azure Storage if required for your workflow (such as AppPackage storage accounts, other storage accounts for resource files or output files, or other similar scenarios).
 
-Even if your workloads are not currently impacted by the changes (as described in the next section), you may still want to [opt in to use simplified compute node communication](#opt-your-batch-account-in-or-out-of-simplified-compute-node-communication) now. This will ensure your Batch workloads are ready for any future improvements enabled by this model.
+Even if your workloads aren't currently impacted by the changes (as described in the next section), you may still want to [opt in to use simplified compute node communication](#opt-your-batch-account-in-or-out-of-simplified-compute-node-communication) now. This will ensure your Batch workloads are ready for any future improvements enabled by this model.
 
 ## Scope of impact
 
-In many cases, this new communication model will not directly affect your Batch workloads. However, simplified compute node communication will have an impact for the following cases:
+In many cases, this new communication model won't directly affect your Batch workloads. However, simplified compute node communication will have an impact for the following cases:
 
 - Users who specify a Virtual Network as part of creating a Batch pool and do one or both of the following:
    - Explicitly disable outbound network traffic rules that are incompatible with simplified compute node communication.
@@ -73,15 +74,15 @@ If either of these cases applies to you, and you would like to opt in to the pre
 
 ### Required network configuration changes
 
-For impacted users, the following set of steps are required to migrate to the new communication model:
+For impacted users, the following set of steps is required to migrate to the new communication model:
 
 1. Ensure your networking configuration as applicable to Batch pools (NSGs, UDRs, firewalls, etc.) includes a union of the models (that is, the network rules prior to simplified compute node communication and after). At a minimum, these rules would be:
    - Inbound:
      - Destination ports 29876, 29877 over TCP from BatchNodeManagement.*region*
    - Outbound:
      - Destination port 443 over TCP to Storage.*region*
      - Destination port 443 over TCP to BatchNodeManagement.*region*
-1. If you have any additional inbound or outbound scenarios required by your workflow, you will need to ensure that your rules reflect these requirements.
+1. If you have any additional inbound or outbound scenarios required by your workflow, you'll need to ensure that your rules reflect these requirements.
 1. [Opt in to simplified compute node communication](#opt-your-batch-account-in-or-out-of-simplified-compute-node-communication) as described below.
 1. Use one of the following options to update your workloads to use the new communication model. Whichever method you use, keep in mind that pools without public IP addresses are unaffected and can't currently use simplified compute node communication. Please see the [Current limitations](#current-limitations) section.
    1. Create new pools and validate that the new pools are working correctly. Migrate your workload to the new pools and delete any earlier pools.
@@ -119,11 +120,11 @@ Use the following options when creating your request.
 1. For **Problem type**, select **Batch Accounts**.
 1. For **Problem subtype**, select **Other issues with Batch Accounts**.
 1. Select **Next**, then select **Next** again to go to the **Additional details** page.
-1. In **Additional details**, you can optionally specify that you want to enable all of the Batch accounts in your subscription, or across multiple subscription. If you do so, be sure to include the subscription IDs here.
+1. In **Additional details**, you can optionally specify that you want to enable all of the Batch accounts in your subscription, or across multiple subscriptions. If you do so, be sure to include the subscription IDs here.
 1. Make any other required selections on the page, then select **Next**.
 1. Review your request details, then select **Create** to submit your support request.
 
-After your request has been submitted, you will be notified once the account has been opted in (or out).
+After your request has been submitted, you'll be notified once the account has been opted in (or out).
 
 ## Current limitations
 
diff --git a/articles/batch/simplified-node-communication-pool-no-public-ip.md b/articles/batch/simplified-node-communication-pool-no-public-ip.md
@@ -18,7 +18,7 @@ ms.custom: references_regions
 
 When you create an Azure Batch pool, you can provision the virtual machine (VM) configuration pool without a public IP address. This article explains how to set up a Batch pool without public IP addresses.
 
-## Why use a pool without public IP Addresses?
+## Why use a pool without public IP addresses?
 
 By default, all the compute nodes in an Azure Batch VM configuration pool are assigned a public IP address. This address is used by the Batch service to support outbound access to the internet, as well inbound access to compute nodes from the internet.
 
diff --git a/articles/private-link/private-endpoint-dns.md b/articles/private-link/private-endpoint-dns.md
