Skip to content

Commit 869a4c7

Browse files
committed
Update paired regions doc
1 parent 8d56a28 commit 869a4c7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/reliability/regions-paired.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Some Azure services use paired regions to build their multi-region geo-replicati
2727
If you're in a region with a pair, then using its pair as a secondary region provides several benefits:
2828

2929
- **Region recovery sequence**. In the unlikely event of a geography-wide outage, the recovery of one region is prioritized out of every region pair. Components that are deployed across paired regions have one of the regions prioritized for recovery.
30-
- **Sequential updating**. Planned Azure system updates are staggered across region pairs to minimize downtime, impact of bugs, and any logical failures in the rare event of a faulty update.
30+
- **Sequential updating**. Planned Azure system updates are staggered across region pairs to minimize the impact of bugs or logical failures in the rare event of a faulty update, and to prevent downtime to solutions that have been designed to use paired regions together for resiliency.
3131
- **Data residency**. To meet data residency requirements, almost all regions reside within the same geography as their pair. To learn about the exceptions, see the [list of Azure regions](./regions-list.md).
3232

3333
> [!IMPORTANT]

0 commit comments

Comments
 (0)