Fixed capping for availability zones

Author: rolyon

articles/availability-zones/az-overview.md

@@ -1,6 +1,6 @@
 ---
-title: Regions and availability zones in Azure
-description: Learn about regions and availability zones in Azure to meet your technical and regulatory requirements.
+title: Regions and Availability Zones in Azure
+description: Learn about regions and Availability Zones in Azure to meet your technical and regulatory requirements.
 author: cynthn
 ms.service: azure
 ms.topic: article
@@ -9,21 +9,21 @@ ms.author: cynthn
 ms.custom: fasttrack-edit, mvc
 ---
 
-# Regions and availability zones in Azure
+# Regions and Availability Zones in Azure
 
 Microsoft Azure services are available globally to drive your cloud operations at an optimal level. You can choose the best region for your needs based on technical and regulatory considerations: service capabilities, data residency, compliance requirements, and latency.
 
 ## Terminology
 
-To better understand regions and availability zones in Azure, it helps to understand key terms or concepts.
+To better understand regions and Availability Zones in Azure, it helps to understand key terms or concepts.
 
 | Term or concept | Description |
 | --- | --- |
 | region | A set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. |
 | geography | An area of the world containing at least one Azure region. Geographies define a discrete market that preserve data residency and compliance boundaries. Geographies allow customers with specific data-residency and compliance needs to keep their data and applications close. Geographies are fault-tolerant to withstand complete region failure through their connection to our dedicated high-capacity networking infrastructure. |
-| availability zone | Unique physical locations within a region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. |
-| recommended region | A region that provides the broadest range of service capabilities and is designed to support availability zones now, or in the future. These are designated in the Azure portal as **Recommended**. |
-| alternate (other) region | A region that extends Azure's footprint within a data residency boundary where a recommended region also exists. Alternate regions help to optimize latency and provide a second region for disaster recovery needs. They are not designed to support availability zones (although Azure conducts regular assessment of these regions to determine if they should become recommended regions). These are designated in the Azure portal as **Other**. |
+| Availability Zone | Unique physical locations within a region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. |
+| recommended region | A region that provides the broadest range of service capabilities and is designed to support Availability Zones now, or in the future. These are designated in the Azure portal as **Recommended**. |
+| alternate (other) region | A region that extends Azure's footprint within a data residency boundary where a recommended region also exists. Alternate regions help to optimize latency and provide a second region for disaster recovery needs. They are not designed to support Availability Zones (although Azure conducts regular assessment of these regions to determine if they should become recommended regions). These are designated in the Azure portal as **Other**. |
 | foundational service | A core Azure service that is available in all regions when the region is generally available. |
 | mainstream service | An Azure service that is available in all recommended regions within 12 months of the region/service general availability or demand-driven availability in alternate regions. |
 | specialized service | An Azure service that is demand-driven availability across regions backed by customized/specialized hardware. |
@@ -34,30 +34,30 @@ To better understand regions and availability zones in Azure, it helps to unders
 
 A region is a set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. Azure gives you the flexibility to deploy applications where you need to, including across multiple regions to deliver cross-region resiliency. For more information, see [Overview of the resiliency pillar](https://docs.microsoft.com/azure/architecture/framework/resiliency/overview).
 
-## Availability zones
+## Availability Zones
 
-An availability zone is a high-availability offering that protects your applications and data from datacenter failures. Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there's a minimum of three separate zones in all enabled regions. The physical separation of availability zones within a region protects applications and data from datacenter failures. Zone-redundant services replicate your applications and data across availability zones to protect from single-points-of-failure. With availability zones, Azure offers industry best 99.99% VM uptime SLA. The full [Azure SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/) explains the guaranteed availability of Azure as a whole.
+An Availability Zone is a high-availability offering that protects your applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there's a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone-redundant services replicate your applications and data across Availability Zones to protect from single-points-of-failure. With Availability Zones, Azure offers industry best 99.99% VM uptime SLA. The full [Azure SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/) explains the guaranteed availability of Azure as a whole.
 
-An availability zone in an Azure region is a combination of a fault domain and an update domain. For example, if you create three or more VMs across three zones in an Azure region, your VMs are effectively distributed across three fault domains and three update domains. The Azure platform recognizes this distribution across update domains to make sure that VMs in different zones are not updated at the same time.
+An Availability Zone in an Azure region is a combination of a fault domain and an update domain. For example, if you create three or more VMs across three zones in an Azure region, your VMs are effectively distributed across three fault domains and three update domains. The Azure platform recognizes this distribution across update domains to make sure that VMs in different zones are not updated at the same time.
 
-Build high-availability into your application architecture by co-locating your compute, storage, networking, and data resources within a zone and replicating in other zones. Azure services that support availability zones fall into two categories:
+Build high-availability into your application architecture by co-locating your compute, storage, networking, and data resources within a zone and replicating in other zones. Azure services that support Availability Zones fall into two categories:
 
 - **Zonal services** – where a resource is pinned to a specific zone (for example, virtual machines, managed disks, Standard IP addresses), or
 - **Zone-redundant services** – when the Azure platform replicates automatically across zones (for example, zone-redundant storage, SQL Database).
 
-To achieve comprehensive business continuity on Azure, build your application architecture using the combination of availability zones with Azure region pairs. You can synchronously replicate your applications and data using availability zones within an Azure region for high-availability and asynchronously replicate across Azure regions for disaster recovery protection.
+To achieve comprehensive business continuity on Azure, build your application architecture using the combination of Availability Zones with Azure region pairs. You can synchronously replicate your applications and data using Availability Zones within an Azure region for high-availability and asynchronously replicate across Azure regions for disaster recovery protection.
 
 ![conceptual view of one zone going down in a region](./media/az-overview/az-graphic-two.png)
 
 > [!IMPORTANT]
-> The availability zone identifiers (the numbers 1, 2 and 3 in the picture above) are logically mapped to the actual physical zones for each subscription independently. That means that availability zone 1 in a given subscription might refer to a different physical zone than availability zone 1 in a different subscription. As a consequence, it's recommended to not rely on availability zone IDs across different subscriptions for virtual machine placement.
+> The Availability Zone identifiers (the numbers 1, 2 and 3 in the picture above) are logically mapped to the actual physical zones for each subscription independently. That means that Availability Zone 1 in a given subscription might refer to a different physical zone than Availability Zone 1 in a different subscription. As a consequence, it's recommended to not rely on Availability Zone IDs across different subscriptions for virtual machine placement.
 
 ## Region and service categories
 
 Azure's approach on availability of Azure services across regions is best described by expressing services made available in recommended regions and alternate regions.
 
-- **Recommended region** - A region that provides the broadest range of service capabilities and is designed to support availability zones now, or in the future. These are designated in the Azure portal as **Recommended**.
-- **Alternate (other) region** - A region that extends Azure's footprint within a data residency boundary where a recommended region also exists. Alternate regions help to optimize latency and provide a second region for disaster recovery needs. They are not designed to support availability zones (although Azure conducts regular assessment of these regions to determine if they should become recommended regions). These are designated in the Azure portal as **Other**.
+- **Recommended region** - A region that provides the broadest range of service capabilities and is designed to support Availability Zones now, or in the future. These are designated in the Azure portal as **Recommended**.
+- **Alternate (other) region** - A region that extends Azure's footprint within a data residency boundary where a recommended region also exists. Alternate regions help to optimize latency and provide a second region for disaster recovery needs. They are not designed to support Availability Zones (although Azure conducts regular assessment of these regions to determine if they should become recommended regions). These are designated in the Azure portal as **Other**.
 
 ### Comparing region types
 
@@ -71,7 +71,7 @@ To see which services are deployed in a given region, as well as the future road
 
 If a service offering is not available in a specific region, you can share your interest by contacting your Microsoft sales representative.
 
-| Region type | Non-regional | Foundational | Mainstream | Specialized | Availability zones | Data residency |
+| Region type | Non-regional | Foundational | Mainstream | Specialized | Availability Zones | Data residency |
 | --- | --- | --- | --- | --- | --- | --- |
 | Recommended | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | Demand-driven | :heavy_check_mark: | :heavy_check_mark: |
 | Alternate | :heavy_check_mark: | :heavy_check_mark: | Demand-driven | Demand-driven | N/A | :heavy_check_mark: |
@@ -149,13 +149,13 @@ As mentioned previously, Azure classifies services into three categories: founda
 
 ###  Services resiliency
 
-All Azure management services are architected to be resilient from region-level failures. In the spectrum of failures, one or more availability zone failures within a region have a smaller failure radius compared to an entire region failure. Azure can recover from a zone-level failure of management services within the region or from another Azure region. Azure performs critical maintenance one zone at a time within a region, to prevent any failures impacting customer resources deployed across availability zones within a region.
+All Azure management services are architected to be resilient from region-level failures. In the spectrum of failures, one or more Availability Zone failures within a region have a smaller failure radius compared to an entire region failure. Azure can recover from a zone-level failure of management services within the region or from another Azure region. Azure performs critical maintenance one zone at a time within a region, to prevent any failures impacting customer resources deployed across Availability Zones within a region.
 
-### Pricing for VMs in availability zones
+### Pricing for VMs in Availability Zones
 
-There is no additional cost for virtual machines deployed in an availability zone. 99.99% VM uptime SLA is offered when two or more VMs are deployed across two or more availability zones within an Azure region. There will be additional inter-availability zone VM-to-VM data transfer charges. For more information, review the [Bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/) page.
+There is no additional cost for virtual machines deployed in an Availability Zone. 99.99% VM uptime SLA is offered when two or more VMs are deployed across two or more Availability Zones within an Azure region. There will be additional inter-Availability Zone VM-to-VM data transfer charges. For more information, review the [Bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/) page.
 
-### Get started with availability zones
+### Get started with Availability Zones
 
 - [Create a virtual machine](../virtual-machines/windows/create-portal-availability-zone.md)
 - [Add a Managed Disk using PowerShell](../virtual-machines/windows/attach-disk-ps.md#add-an-empty-data-disk-to-a-virtual-machine)