Merge pull request #197977 from tomvcassidy/availabilityZoneReferences

ACI Availability Zones References

Author: PRMerger6

articles/container-instances/availability-zones.md

@@ -8,13 +8,15 @@ ms.custom: devx-track-js, devx-track-azurecli
 
 # Deploy an Azure Container Instances (ACI) container group in an availability zone (preview)
 
-An [availability zone][availability-zone-overview] is a physically separate zone in an Azure region. You can use availability zones to protect your containerized applications from an unlikely failure or loss of an entire data center. Azure Container Instances (ACI) supports zonal container group deployments, meaning the instance is pinned to a specific, self-selected availability zone. The availability zone is specified at the container group level. Containers within a container group cannot have unique availability zones. To change your container group's availability zone, you must delete the container group and create another container group with the new availability zone.
+An [availability zone][availability-zone-overview] is a physically separate zone in an Azure region. You can use availability zones to protect your containerized applications from an unlikely failure or loss of an entire data center. Three types of Azure services support availability zones: *zonal*, *zone-redundant*, and *always-available* services. You can learn more about these types of services and how they promote resiliency in the [Highly available services section of Azure services that support availability zones](/azure/availability-zones/az-region#highly-available-services).
+
+Azure Container Instances (ACI) supports *zonal* container group deployments, meaning the instance is pinned to a specific, self-selected availability zone. The availability zone is specified at the container group level. Containers within a container group can't have unique availability zones. To change your container group's availability zone, you must delete the container group and create another container group with the new availability zone.
 
 > [!IMPORTANT]
 > This feature is currently in preview. Previews are made available to you on the condition that you agree to the supplemental terms of use.
 
 > [!IMPORTANT]
-> Zonal container group deployments are supported in most regions where ACI is available for Linux and Windows Sever 2019 container groups. For details, see [Regions and resource availability][container-regions].
+> Zonal container group deployments are supported in most regions where ACI is available for Linux and Windows Server 2019 container groups. For details, see [Regions and resource availability][container-regions].
 
 > [!NOTE]
 > Examples in this article are formatted for the Bash shell. If you prefer another shell, adjust the line continuation characters accordingly.
@@ -24,9 +26,9 @@ An [availability zone][availability-zone-overview] is a physically separate zone
 > [!IMPORTANT]
 > This feature is currently not available for Azure portal.
 
-* Container groups with GPU resources do not support availability zones at this time.
-* Virtual Network injected container groups do not support availability zones at this time.
-* Windows Sever 2016 container groups do not support availability zones at this time.
+* Container groups with GPU resources don't support availability zones at this time.
+* Virtual Network injected container groups don't support availability zones at this time.
+* Windows Server 2016 container groups don't support availability zones at this time.
 
 ### Version requirements
 
@@ -186,6 +188,10 @@ To verify the container group deployed successfully into an availability zone, v
 az containershow --name acilinuxcontainergroup --resource-group myResourceGroup
 ```
 
+## Next steps
+
+Learn about building fault-tolerant applications using zonal container groups from the [Azure Architecture Center's guide on availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability).
+
 <!-- LINKS - Internal -->
 [az-container-create]: /cli/azure/container#az_container_create
 [container-regions]: container-instances-region-availability.md