Skip to content

Commit d25731f

Browse files
committed
Learn Editor: Update overview.md
1 parent eff5167 commit d25731f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/reliability/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: subject-reliability
1212

1313
# Azure reliability documentation
1414

15-
Reliability consists of two principles: resiliency and availability. The goal of [reliability ](/azure/reliability/overview)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.
15+
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.
1616

1717
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.
1818

0 commit comments

Comments
 (0)