Last look fixes.

TimShererWithAquent · TimShererWithAquent · commit 888aca8ee10d · 2023-03-21T09:27:05.000-07:00
diff --git a/articles/networking/troubleshoot-failed-state.md b/articles/networking/troubleshoot-failed-state.md
@@ -30,21 +30,21 @@ The provisioning state is the status of a user-initiated, control-plane operatio
 
 These states are metadata properties of the resource. They're independent from the functionality of the resource itself. Being in the failed state doesn't necessarily mean that the resource isn't functional. In most cases, it can continue operating and serving traffic without issues.
 
-In several scenarios, if the resource is in the failed state, further operations on the resource or on other resources that depend on it might fail. The state needs to be reverted back to succeeded before executing other operations.
+In several scenarios, if the resource is in the failed state, further operations on the resource or on other resources that depend on it might fail. You need to revert the state back to succeeded before running other operations.
 
 For example, you can't run an operation on a `VirtualNetworkGateway` if it has a dependent `VirtualNetworkGatewayConnection` object in failed state.
 
 ## Restoring succeeded state through a PUT operation
 
-The correct way to restore succeeded state is to execute another write (`PUT`) operation on the resource.
+To restore succeeded state, run another write (`PUT`) operation on the resource.
 
 The issue that caused the previous operation might no longer be current. The newer write operation should be successful and restore the provisioning state.
 
-The easiest way to achieve this task is to use Azure PowerShell. Issue a resource-specific *Get* command that fetches all the current configuration for the impacted resource as it is deployed. Next, run a *Set* command, or equivalent, to commit to Azure a write operation that contains all the resource properties as currently configured.
+The easiest way to achieve this task is to use Azure PowerShell. Issue a resource-specific *Get* command that fetches all the current configuration for the resource. Next, run a *Set* command, or equivalent, to commit to Azure a write operation that contains all the resource properties as currently configured.
 
 > [!IMPORTANT]
 >
-> - Running a `Set` command on the resource without first running a `Get` results in overwriting the resource with default settings. Those settings might be different from the ones you currently have configured. Don't just run a `Set` command unless resetting settings is intentional.
+> - Running a `Set` command on the resource without first running a `Get` results in overwriting the resource with default settings. Those settings might be different from the ones you currently have configured. Don't just run a `Set` command unless you intend to reset to default.
 > - Running a `Get` and `Set` operation using third party software or any tool using older API version might also result in loss of some settings. Those settings might not be present in the API version with which you run the command.
 >
 ## Azure PowerShell cmdlets to restore succeeded provisioning state
@@ -123,7 +123,7 @@ Get-AzExpressRouteGateway -Name "your_resource_name" -ResourceGroupName "your_re
 ```
 
 > [!NOTE]
-> `Microsoft.Network/expressRouteGateways` are those gateways deployed within a Virtual WAN. If you have a standalone ExpressRoute gateway in your Virtual Network, run the commands related to [Microsoft.Network/virtualNetworkGateways](#microsoftnetworkvirtualnetworkgateways).
+> `Microsoft.Network/expressRouteGateways` are deployed within a Virtual WAN. If you have a standalone ExpressRoute gateway in your virtual network, run the commands related to [Microsoft.Network/virtualNetworkGateways](#microsoftnetworkvirtualnetworkgateways).
 
 ### Microsoft.Network/expressRoutePorts
 
@@ -174,7 +174,7 @@ Get-AzNetworkVirtualAppliance -Name "your_resource_name" -ResourceGroupName "you
 ```
 
 > [!NOTE]
-> Most Virtual WAN related resources such as networkVirtualAppliances use the `Update` cmdlet, not the `Set`, for write operations.
+> Most Virtual WAN related resources, such as networkVirtualAppliances, use the `Update` cmdlet, not the `Set`, for write operations.
 
 ### Microsoft.Network/privateDnsZones
 
@@ -250,7 +250,7 @@ Get-AzVpnGateway -Name "your_resource_name" -ResourceGroupName "your_resource_gr
 
 > [!NOTE]
 >
-> - `Microsoft.Network/vpnGateways` are those gateways deployed within a Virtual WAN. If you have a standalone VPN gateway in your virtual network, run the commands related to [Microsoft.Network/virtualNetworkGateways](#microsoftnetworkvirtualnetworkgateways).
+> - `Microsoft.Network/vpnGateways` are deployed within a Virtual WAN. If you have a standalone VPN gateway in your virtual network, run the commands related to [Microsoft.Network/virtualNetworkGateways](#microsoftnetworkvirtualnetworkgateways).
 > - Most Virtual WAN related resources, such as vpnGateways, use the `Update` cmdlet, not the `Set` for write operations.
 
 ### Microsoft.Network/vpnSites
@@ -260,11 +260,11 @@ Get-AzVpnSite -Name "your_resource_name" -ResourceGroupName "your_resource_group
 ```
 
 > [!NOTE]
-> Most Virtual WAN related resources, such as vpnSites, use the `Update` cmdlet, not the `Set` for write operations.
+> Most Virtual WAN related resources, such as vpnSites, use the `Update` cmdlet, not the `Set`, for write operations.
 
 ## Next steps
 
-If the command that you ran didn't fix the failed state, it should return an error code.
+If the command that you ran didn't resolve the failed state, it should return an error code.
 Most error codes contain a detailed description of what the problem might be and offer hints to solve it.
 
-If you're still experiencing issues, open a support ticket with [Microsoft support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade). Make sure you specify to the support agent both the error code you received in the latest operation and the timestamp when you ran the operation.
+If you're still experiencing issues, open a support ticket with [Microsoft support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade). Specify to the support agent both the error code that you received in the latest operation and the timestamp when you ran the operation.
diff --git a/articles/virtual-network/nat-gateway/manage-nat-gateway.md b/articles/virtual-network/nat-gateway/manage-nat-gateway.md
@@ -13,7 +13,7 @@ ms.custom: template-how-to, devx-track-azurecli, devx-track-azurepowershell
 
 # Manage NAT gateway
 
-Learn how to create and remove a NAT gateway resource from a virtual network subnet. A NAT gateway enables outbound connectivity for resources in an Azure Virtual Network. You might want to change the IP address or prefix that your resources use for outbound connectivity to the internet. The public IP address and public IP address prefix associated with the NAT gateway can be changed after deployment.
+Learn how to create and remove a NAT gateway resource from a virtual network subnet. A NAT gateway enables outbound connectivity for resources in an Azure Virtual Network. You can change the public IP addresses and public IP address prefixes associated with the NAT gateway changed after deployment.
 
 This article explains how to manage the following aspects of NAT gateway:
 
@@ -45,7 +45,7 @@ To use Azure PowerShell for this article, you need:
 
 - Ensure that your `Az.Network` module is 4.3.0 or later. To verify the installed module, use the command `Get-InstalledModule -Name "Az.Network"`. If the module requires an update, use the command `Update-Module -Name Az.Network`.
 
-- Sign in to Azure PowerShell and select the subscription with which you want to use this feature. For more information, see [Sign in with Azure PowerShell](/powershell/azure/authenticate-azureps).
+- Sign in to Azure PowerShell and select the subscription that you want to use. For more information, see [Sign in with Azure PowerShell](/powershell/azure/authenticate-azureps).
 
 To use Azure CLI for this article, you need:
 
@@ -67,16 +67,12 @@ You can create a NAT gateway resource and add it to an existing subnet by using
 
 1. Enter the following information in the **Basics** tab of **Create network address translation (NAT) gateway**.
 
-    | Setting | Value |
-    | ------- | ----- |
-    | **Project details** |   |
-    | Subscription | Select your subscription. |
-    | Resource group | Select your resource group or select **Create new** to create a new resource group. |
-    | **Instance details** |   |
-    | NAT gateway name | Enter **myNATgateway**. |
-    | Region | Select your region. This example uses **East US 2**. |
-    | Availability zone | Select an availability zone. This example uses **No Zone**. For more information about NAT gateway availability, see [NAT gateway and availability zones](nat-availability-zones.md). |
-    | TCP idle timeout (minutes) | Select an idle timeout. This example uses the default of **4**. |
+   - Select your **Subscription**.
+   - Select your resource group or select **Create new** to create a new resource group.
+   - **NAT gateway name**. Enter *myNATgateway*.
+   - Select your **Region**. This example uses **East US 2**.
+   - Select an **Availability zone**. This example uses **No Zone**. For more information about NAT gateway availability, see [NAT gateway and availability zones](nat-availability-zones.md). |
+   - Select a **TCP idle timeout (minutes)**. This example uses the default of **4**.
 
 1. Select the **Outbound IP** tab, or select **Next: Outbound IP**.
 
@@ -149,6 +145,7 @@ $sub = @{
     Name = 'mySubnet'
     VirtualNetwork = $vnet
     NatGateway = $natGateway
+    AddressPrefix = '10.0.2.0/24'
 }
 Set-AzVirtualNetworkSubnetConfig @sub
 
@@ -300,7 +297,7 @@ To remove a NAT gateway from an existing subnet, complete the following steps.
 
 1. Select **myNATgateway**.
 
-1. Select **Subnets** in **Settings**.
+1. Under **Settings**, select **Subnets**.
 
 1. Select **Disassociate** to remove the NAT gateway from the configured subnet.
 
@@ -357,17 +354,16 @@ Complete the following steps to add or remove a public IP address from a NAT gat
 
 1. Enter the following information in **Create public IP address**.
 
-    | Setting | Value |
-    | ------- | ----- |
-    | Subscription | Select your subscription. |
-    | Resource group | Select your resource group. The example uses **myResourceGroup**. |
-    | Region | Select a region. This example uses **East US 2**. |
-    | Name | Enter *myPublicIP-NAT2*. |
-    | IP version | Select **IPv4**. |
-    | SKU | Select **Standard**. |
-    | Availability zone | Select the default of **Zone-redundant**. |
-    | Tier | Select **Regional**. |
-    | Routing preference | Leave the default of **Microsoft network**. |
+   | Setting | Value |
+   | ------- | ----- |
+   | Subscription | Select your subscription. |
+   | Resource group | Select your resource group. The example uses **myResourceGroup**. |
+   | Region | Select a region. This example uses **East US 2**. |
+   | Name | Enter *myPublicIP-NAT2*. |
+   | IP version | Select **IPv4**. |
+   | SKU | Select **Standard**. |
+   | Availability zone | Select the default of **Zone-redundant**. |
+   | Tier | Select **Regional**. |
 
 1. Select **Review + create** and then select **Create**.
 
@@ -533,17 +529,17 @@ Complete the following steps to add or remove a public IP prefix from a NAT gate
 
 1. Enter the following information in the **Basics** tab of **Create a public IP prefix**.
 
-    | Setting | Value |
-    | ------- | ----- |
-    | **Project details** |  |
-    | Subscription | Select your subscription. |
-    | Resource group | Select your resource group. This example uses **myResourceGroup**. |
-    | **Instance details** |   |
-    | Name | Enter *myPublicIPPrefix-NAT*. |
-    | Region | Select your region. This example uses **East US 2**. |
-    | IP version | Select **IPv4**. |
-    | Prefix ownership | Select **Microsoft owned**. |
-    | Prefix size | Select a prefix size. This example uses **/28 (16 addresses)**. |
+   | Setting | Value |
+   | ------- | ----- |
+   | **Project details** |  |
+   | Subscription | Select your subscription. |
+   | Resource group | Select your resource group. This example uses **myResourceGroup**. |
+   | **Instance details** |   |
+   | Name | Enter *myPublicIPPrefix-NAT*. |
+   | Region | Select your region. This example uses **East US 2**. |
+   | IP version | Select **IPv4**. |
+   | Prefix ownership | Select **Microsoft owned**. |
+   | Prefix size | Select a prefix size. This example uses **/28 (16 addresses)**. |
 
 1. Select **Review + create**, then select **Create**.
 
diff --git a/articles/virtual-network/update-virtual-network-peering-address-space.md b/articles/virtual-network/update-virtual-network-peering-address-space.md
@@ -17,14 +17,14 @@ In this article, you learn how to update a peered virtual network by modifying,
 ## Prerequisites
 
 - An existing peered virtual network with two virtual networks
-- If adding address space, ensure it doesn't overlap other address spaces
+- If you add an address space, ensure that it doesn't overlap other address spaces
 
 ## Modify the address range prefix of an existing address range
 
 In this section, you modify the address range prefix for an existing address range within your peered virtual network.
 
-1. In the search box at the top of the Azure portal, enter *virtual networks*. Select **Virtual networks** in the search results.
-1. From the list of virtual networks, select the virtual network where you're modifying an address range.
+1. In the search box at the top of the Azure portal, enter *virtual networks*. Select **Virtual networks** from the search results.
+1. From the list of virtual networks, select the virtual network to modify.
 1. Under **Settings**, select **Address space**.
 1. On the **Address space** page, change the address range prefix per your requirements, and select **Save**.
 
@@ -41,7 +41,7 @@ In this section, you modify the address range prefix for an existing address ran
     :::image type="content" source="media/update-virtual-network-peering-address-space/verify-address-space-thumb.png" alt-text="Screenshot of the Address Space page where you verify the address space has changed." lightbox="media/update-virtual-network-peering-address-space/verify-address-space-full.png":::
 
 > [!NOTE]
-> When you update the address space for a virtual network, you need to sync the virtual network peer for each remote peered virtual network to learn of the new address space updates. We recommend that you run sync after every resize address space operation instead of performing multiple resizing operations and then running the sync operation.
+> When you update the address space for a virtual network, you need to sync the virtual network peer for each remote peered virtual network. We recommend that you run sync after every resize address space operation instead of performing multiple resizing operations and then running the sync operation.
 >
 > The following actions require you to sync:
 >
@@ -53,7 +53,7 @@ In this section, you modify the address range prefix for an existing address ran
 
 In this section, you add an IP address range to the IP address space of a peered virtual network.
 
-1. In the search box at the top of the Azure portal, enter *virtual networks*. When **Virtual networks** appears in the search results, select it.
+1. In the search box at the top of the Azure portal, enter *virtual networks*. Select **Virtual networks** from the search results.
 1. From the list of virtual networks, select the virtual network where you're adding an address range.
 1. Under **Settings**, select **Address space**.
 1. On the **Address space** page, add the address range per your requirements, and select **Save** when finished.
