Apply suggestions from code review

Author: johndowns

articles/reliability/overview-reliability-guidance.md

@@ -12,15 +12,13 @@ ms.subservice: azure-reliability
 
 # Reliability guides by service
 
-While Azure provides a set of reliability features, the resiliency of your workload is a [shared responsibility between you and Microsoft](./concept-shared-responsibility.md) and depends on how you have designed your business continuity plan to define your expectations for reliability. For this reason, it's important that you understand the reliability features of each service you use, and how to best implement them in your workload. This document provides links to the reliability guidance for each Azure service, detailing how each services supports your reliability requirements through its features and design.
+While Azure provides a set of reliability features, the resiliency of your workload is a [shared responsibility between you and Microsoft](./concept-shared-responsibility.md) and depends on how you have designed your business continuity plan to define your expectations for reliability. For this reason, it's important that you understand the reliability features of each service you use, and how to best implement them in your workload. This document provides links to the reliability guidance for each Azure service, detailing how each service supports your reliability requirements through its features and design.
 
 Each service guide generally contains information on how the service supports:
 
 - *Availability zones* such as zonal and zone-redundant deployment options, traffic routing and data replication between zones, what happens if a zone experiences an outage, failback, and how to configure your resources for availability zone support.
 - *Multi-region support* such as how to configure multi-region or geo-disaster support, traffic routing and data replication between regions, region-down experience, failover and failback support, alternative multi-region support.
-- *Backup support* such as who controls backups, where they are stored,how they can be recovered, and whether they are accessible only within a region or across regions.
-
-This document provides links to the reliability guidance for each Azure service, detailing how each services supports or does not support specific reliability features. The guidance includes information about the service's architecture, availability, and disaster recovery options.
+- *Backup support* such as who controls backups, where they are stored, how they can be recovered, and whether they are accessible only within a region or across regions.
 
 
 >[!NOTE]

articles/reliability/regions-overview.md

@@ -61,7 +61,7 @@ When you select regions that are geographically far apart, the latency of networ
 
 ## Non-regional services
 
-Most Azure services are deployed to a specific regions or regions. However, there are some services that aren't tied to a specific Azure region. It's important to recognize how *non-regional* services operate in the case of a regional failure, and to take them into account when you design your solutions and business continuity plan.
+Most Azure services are deployed to a specific region. However, there are some services that aren't tied to a single Azure region. It's important to recognize how *non-regional* services operate in the case of a regional failure, and to take them into account when you design your solutions and business continuity plan.
 
 Non-regional services are deployed by Microsoft across two or more regions. If there's a regional failure, the instance of the service in a healthy region can continues servicing requests. For example, [Azure DNS](https://azure.microsoft.com/products/dns) is a non-regional service.