Merge pull request #232206 from anaharris-ms/docs-editor/overview-1679928490

Update overview.md

Author: prmerger-automator[bot]

articles/reliability/overview.md

@@ -8,12 +8,11 @@ ms.author: anaharris
 ms.service: reliability
 ms.subservice: availability-zones
 ms.custom: subject-reliability
-
 ---
 
 # Azure reliability documentation
 
-Reliability consists of two principles: resiliency and availability. The goal of reliability is to return your application to a fully functioning state after a failure occurs. The goal of availability is to provide consistent access to your application or workload be users as they need to.
+Reliability consists of two principles: resiliency and availability. The goal of resiliency is to return your application to a fully functioning state after a failure occurs. The goal of availability is to provide consistent access to your application or workload be users as they need to.
 
 Azure includes built-in reliability services that you can use and manage based on your business needs. Whether it’s a single hardware node failure, a rack level failure, a datacenter outage, or a large-scale regional outage, Azure provides solutions that improve reliability. For example, availability sets ensure that the virtual machines deployed on Azure are distributed across multiple isolated hardware nodes in a cluster. Availability zones protect customers’ applications and data from datacenter failures across multiple physical locations within a region. **Regions** and **availability zones** are central to your application design and resiliency strategy and are discussed in greater detail later in this article.