Skip to content

Commit b4e104b

Browse files
authored
Merge pull request #206369 from SwathiDhanwada-MSFT/patch-32
(AzureCXP) fixes MicrosoftDocs/azure-docs#96423
2 parents c8aaaa3 + 673cba4 commit b4e104b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/availability-zones/cross-region-replication-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ For applications that support multiple active regions, we recommend that you use
3232

3333
## Benefits of cross-region replication
3434

35-
Architecting cross-regional replication for your services and data can be decided on a per-service basis. You'll necessarily take a cost-benefit analysis approach based on your organization's strategic and business requirements. Primary and ripple benefits of cost-region replication are complex, extensive, and deserve elaboration. These benefits include:
35+
Architecting cross-regional replication for your services and data can be decided on a per-service basis. You'll necessarily take a cost-benefit analysis approach based on your organization's strategic and business requirements. Primary and ripple benefits of cross-region replication are complex, extensive, and deserve elaboration. These benefits include:
3636

3737
- **Region recovery sequence**: If a geography-wide outage occurs, recovery of one region is prioritized out of every enabled set of regions. Applications that are deployed across enabled region sets are guaranteed to have one of the regions prioritized for recovery. If an application is deployed across regions, any of which isn't enabled for cross-regional replication, recovery can be delayed.
3838
- **Sequential updating**: Planned Azure system updates for your enabled regions are staggered chronologically to minimize downtime, impact of bugs, and any logical failures in the rare event of a faulty update.

0 commit comments

Comments
 (0)