Apply suggestions from code review

Author: johndowns

articles/reliability/availability-zones-overview.md

@@ -39,7 +39,7 @@ There are two ways that Azure services use availability zones:
 
 Azure services support one or both of these approaches. Platform as a service (PaaS) services typically support zone-redundant deployments. Infrastructure as a service (IaaS) services typically support zonal deployments. For more information about how Azure services work with availability zones, see [Azure regions with availability zone support](availability-zones-region-support.md).
 
-If you don't configure availability zones on a service, it's called a *non-zonal* or *regional* deployment. Resources configured in this way might be placed in any availabilty zone in the region, and might be moved. If any availability zone in the region experiences an outage, non-zonal resources might be affected.
+Some services don't use availability zones until you configure them to do so. If you don't explicitly configure a service for availability zone support, it's called a *non-zonal* or *regional* deployment. Resources configured in this way might be placed in any availability zone in the region, and might be moved. If any availability zone in the region experiences an outage, non-zonal resources might be in the affected zone and could experience downtime.
 
 For information on service-specific reliability support using availability zones as well as recommended disaster recovery guidance see [Reliability guidance overview](./reliability-guidance-overview.md).
 

articles/reliability/availability-zones-service-support.md

@@ -26,7 +26,7 @@ Azure services can provide two types of availability zone support: *zonal* and *
 
 - **Zone-redundant services**: Resources are replicated or distributed across zones automatically. For example, zone-redundant services replicate the data across multiple zones so that a failure in one zone doesn't affect the high availability of the data. 
 
-If you don't configure availability zones on a service, it's called a *non-zonal* or *regional* deployment. Resources configured in this way might be placed in any availabilty zone in the region, and might be moved. If any availability zone in the region experiences an outage, non-zonal resources might be affected.
+Some services don't use availability zones until you configure them to do so. If you don't explicitly configure a service for availability zone support, it's called a *non-zonal* or *regional* deployment. Resources configured in this way might be placed in any availability zone in the region, and might be moved. If any availability zone in the region experiences an outage, non-zonal resources might be in the affected zone and could experience downtime.
 
 >[!IMPORTANT]
 >Some services may have limited support for availability zones. For example, some may only support availability zones for certain tiers, regions, or SKUs. To get more information on service limitations for availability zone support, select that service in the table.