edits

Author: Court72

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -34,7 +34,7 @@ When adding a region, you configure:
 
 ## Prerequisites
 
-* Thoroughly understand all requirements and considerations for enabling multi-region deployment in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+* Thoroughly understand all [requirements and considerations for enabling multi-region deployment in API Management](../reliability/reliability-api-management.md).
 
 * If you haven't created an API Management service instance, see [Create an API Management service instance](get-started-create-service-instance.md). Select the Premium service tier.
 
@@ -64,7 +64,7 @@ By default, each API routes requests to a single back-end service URL. Even if y
 
 To take advantage of geographical distribution of your system, you should deploy back-end services in the same regions as API Management instances. Then, by using policies and the `@(context.Deployment.Region)` property, you can route the traffic to local instances of your back end.
 
-1. Navigate to your API Management instance and select **APIs** from the left menu.
+1. Go to your API Management instance and select **APIs** from the left menu.
 2. Select your desired API.
 3. On the **Design** tab, in the **Inbound processing** section, select **Code editor**.
 
@@ -115,7 +115,7 @@ You can also front your back-end services with [Azure Traffic Manager](https://a
 API Management routes the requests to a regional gateway based on [the lowest latency](../traffic-manager/traffic-manager-routing-methods.md#performance). Although it isn't possible to override this setting in API Management, you can use your own Traffic Manager with custom routing rules.
 
 1. Create your own [Traffic Manager](https://azure.microsoft.com/services/traffic-manager/).
-1. If you use a custom domain, [use it with the Traffic Manager](../traffic-manager/traffic-manager-point-internet-domain.md) instead of the API Management service.
+1. If you use a custom domain, [use it with Traffic Manager](../traffic-manager/traffic-manager-point-internet-domain.md) instead of the API Management service.
 1. [Configure the API Management regional endpoints in Traffic Manager](../traffic-manager/traffic-manager-manage-endpoints.md). The regional endpoints follow the URL pattern of `https://<service-name>-<region>-01.regional.azure-api.net`, for example `https://contoso-westus2-01.regional.azure-api.net`.
 1. [Configure the API Management regional status endpoints in Traffic Manager](../traffic-manager/traffic-manager-monitoring.md). The regional status endpoints follow the URL pattern of `https://<service-name>-<region>-01.regional.azure-api.net/status-0123456789abcdef`, for example `https://contoso-westus2-01.regional.azure-api.net/status-0123456789abcdef`.
 1. Specify [the routing method](../traffic-manager/traffic-manager-routing-methods.md) of the Traffic Manager.
@@ -168,7 +168,7 @@ This section provides considerations for multi-region deployments when the API M
 * Configure each regional network independently. The [connectivity requirements](virtual-network-reference.md), such as required network security group rules for a virtual network in an added region, are generally the same as the requirements for a network in the primary region.
 * Virtual networks in the different regions don't need to be peered.
 > [!IMPORTANT]
-> When you configure regional gateways in internal virtual network mode, each gateway must also have outbound connectivity on port 1433 to the Azure SQL database configured for your API Management instance, which is only in the *primary* region. Ensure that you allow connectivity to the fully qualified domain name (FQDN) or IP address of this Azure SQL database in any routes or firewall rules you configure for networks in your secondary regions; the Azure SQL service endpoint can't be used in this scenario. To find the Azure SQL database name in the primary region, go to the **Network** > **Network status** page of your API Management instance in the portal. 
+> When you configure your API Management instance to use internal virtual network mode, each regional gateway must also have outbound connectivity on port 1433 to the Azure SQL database configured for your API Management instance, which is only in the *primary* region. Ensure that you allow connectivity to the fully qualified domain name (FQDN) or IP address of this Azure SQL database in any routes or firewall rules you configure for networks in your secondary regions; the Azure SQL service endpoint can't be used in this scenario. To find the Azure SQL database name in the primary region, go to the **Network** > **Network status** page of your API Management instance in the portal. 
 
 ### IP addresses
 

articles/api-management/enable-availability-zone-support.md

@@ -16,7 +16,7 @@ ms.custom: references_regions, subject-reliability
 
 This how-to guide describes how to enable and configure availability zones on an Azure API Management instance.
 
-For more detailed information about reliability features of API Management, such as availability zones and multiple-region deployments, see [Reliability in API Management](../reliability/reliability-api-management.md).
+For more detailed information about reliability features of API Management, such as availability zones and multi-region deployments, see [Reliability in API Management](../reliability/reliability-api-management.md).
 
 [!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
 
@@ -30,7 +30,7 @@ For more detailed information about reliability features of API Management, such
 
 ## Default availability zone support
 
-When you create a new API Management instance in the **Premium** tier in a region that supports availability zones, or you [deploy API Management to an additional region](api-management-howto-deploy-multi-region.md), API Management provides two types of availability zone support:
+When you create a new API Management instance in the **Premium** tier in a region that supports availability zones, or you [deploy API Management to multiple regions](api-management-howto-deploy-multi-region.md), API Management provides two types of availability zone support:
 
 - **Automatic:** API Management provides automatic availability zone support when you don't specify which availability zones to use.
 
@@ -51,53 +51,53 @@ We recommend automatic availability zone configuration, but you can manually con
 
 ### Instance not injected in a virtual network
 
-To manually configure availability zone support on an existing location of an API Management instance:
+To manually configure availability zone support on an existing location of an API Management instance, follow these steps:
 
-1. Thoroughly understand all requirements and considerations for availability zones in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+1. Thoroughly understand all [requirements and considerations for availability zones in API Management](../reliability/reliability-api-management.md).
 
 1. In the Azure portal, go to your API Management instance.
 
 1. On the **Deployment + infrastructure** menu, select **Locations**.
 
-1. In the **Location** box, select the location that you want to enable. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
+1. Select the location that you want to enable. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
 
-1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
+1. Under **Units**, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
 
-1. In the **Availability zones** box, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you select must distribute evenly across the availability zones. For example, if you select three units, you must select three zones so that each zone hosts one unit. 
+1. Under **Availability zones**, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you select must distribute evenly across the availability zones. For example, if you select three units, you must select three zones so that each zone hosts one unit. 
 
 1. Select **Apply**, and then select **Save**.
 
 :::image type="content" alt-text="Screenshot that shows availability zone configuration for an existing location of an API Management instance that's not injected in a virtual network." source ="media/enable-availability-zone-support/option-one-not-injected-in-vnet.png" lightbox="media/enable-availability-zone-support/option-one-not-injected-in-vnet.png":::
 
 ### Instance injected in a virtual network
 
-To manually configure availability zone support on an existing location of an API Management instance that's injected in a virtual network:
+To manually configure availability zone support on an existing location of an API Management instance that's injected in a virtual network, follow these steps:
 
-1. Thoroughly understand all requirements and considerations for enabling zone redundancy in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+1. Thoroughly understand all [requirements and considerations for enabling zone redundancy in API Management](../reliability/reliability-api-management.md).
 
 1. Create a public IP address in the location to enable availability zones. For detailed requirements, see the [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
 
 1. In the Azure portal, go to your API Management instance.
 
 1. On the **Deployment + infrastructure** menu, select **Locations**.
 
-1. In the **Location** box, select the location that you want to enable. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
+1. Select the location that you want to enable. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
 
-1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
+1. Under **Units**, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
 
-1. In the **Availability zones** box, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you select must distribute evenly across the availability zones. For example, if you select three units, you must select three zones so that each zone hosts one unit.
+1. Under **Availability zones**, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you select must distribute evenly across the availability zones. For example, if you select three units, you must select three zones so that each zone hosts one unit.
 
-1. In the **Public IP Address** box, select a public IP address in the location.
+1. Under **Public IP Address**, select a public IP address in the location.
 
 1. Select **Apply**, and then select **Save**.
 
-:::image type="content" alt-text="Screenshot that shows availability zone configuration for an existing location of an API Management instance that's injected in a virtual network." source ="media/enable-availability-zone-support/option-three-stv2-injected-in-vnet.png":::
+:::image type="content" alt-text="Screenshot that shows availability zone configuration for an existing location of an API Management instance that's injected in a virtual network." source ="media/enable-availability-zone-support/option-three-stv2-injected-in-vnet.png" lightbox="media/enable-availability-zone-support/option-three-stv2-injected-in-vnet.png":::
 
 ## New gateway location
 
-To add a new location to your API Management instance and to configure availability zones in that location:
+To add a new location to your API Management instance and to configure availability zones in that location, follow these steps:
 
-1. Thoroughly understand all requirements and considerations for enabling availability zones in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+1. Thoroughly understand all [requirements and considerations for enabling availability zones in API Management](../reliability/reliability-api-management.md).
 
 1. If your API Management instance is deployed in a virtual network in the primary location, set up a [virtual network](../api-management/api-management-using-with-vnet.md), subnet, and optional public IP address in the new location where you plan to enable availability zones.
 
@@ -107,15 +107,15 @@ To add a new location to your API Management instance and to configure availabil
 
 1. Select **+ Add** to add a new location. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
 
-1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
+1. Under **Units**, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
 
-1. In the **Availability zones** box, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you select must distribute evenly across the availability zones. For example, if you select three units, you must select three zones so that each zone hosts one unit.
+1. Under **Availability zones**, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you select must distribute evenly across the availability zones. For example, if you select three units, you must select three zones so that each zone hosts one unit.
 
-1. If your API Management instance is deployed in a virtual network, use the boxes under **Network** to select the virtual network, subnet, and public IP address that are available in the location.
+1. If your API Management instance is deployed in a virtual network, under **Network**, select the virtual network, subnet, and public IP address that are available in the location.
 
 1. Select **Add**, and then select **Save**.
 
-:::image type="content" alt-text="Screenshot that shows selections for adding a new location for an API Management instance with or without a virtual network." source ="media/enable-availability-zone-support/option-four-add-new-location.png":::
+:::image type="content" alt-text="Screenshot that shows selections for adding a new location for an API Management instance with or without a virtual network." source ="media/enable-availability-zone-support/option-four-add-new-location.png" lightbox="media/enable-availability-zone-support/option-four-add-new-location.png":::
 
 ## Related content