Skip to content

Commit 01566b1

Browse files
authored
Update availability-zones-baseline.md
1 parent cdfa638 commit 01566b1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/reliability/availability-zones-baseline.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: references_regions, subject-reliability
1212

1313
# Azure availability zone migration baseline
1414

15-
This article shows you how to assess the availability-zone readiness of your application for the purposes of migrating from non-availability zone to availability zone support. We'll take you through the steps you'll need to determine how you can take advantage of availability zone support in alignment with your application and regional requirements. For more detailed information on availability zones and the regions that support them, see [What are Azure regions and availability zones](availability-zones-overview.md).
15+
This article shows you how to assess the availability-zone readiness of your application for the purposes of migrating from non-availability zone to availability zone support. Understand how you can take advantage of availability zone support, and how to meet your application and resiliency requirements. For more detailed information on availability zones and the regions that support them, see [What are Azure regions and availability zones](availability-zones-overview.md).
1616

1717
When creating reliable workloads, you can choose at least one of the following availability zone configurations:
1818

@@ -92,7 +92,7 @@ With a zonal deployment, you must:
9292
If the Azure service supports availability zones, we highly recommend that you use zone-redundancy by spreading nodes across the zones to get higher uptime SLA and protection against zonal outages.
9393

9494

95-
For a 3-tier application it is important to understand the application, business, and data tiers; as well as their state (stateful or stateless) to architect in alignment with the best practices and guidance according to the type of workload.
95+
For a 3-tier application it's important to understand the application, business, and data tiers; as well as their state (stateful or stateless) to architect in alignment with the best practices and guidance according to the type of workload.
9696

9797
For specialized workloads on Azure as below examples, please refer to the respective landing zone architecture guidance and best practices.
9898

0 commit comments

Comments
 (0)