Merge pull request #296908 from johndowns/reliability-small-edits

Reliability Hub - Small edits

Author: Stacyrch140

articles/reliability/TOC.yml

@@ -65,7 +65,7 @@
       - name: Azure Database for MySQL - Flexible Server
         href: migrate-database-mysql-flex.md
       - name: Azure Database for PostgreSQL
-        href: /azure/postgresql/flexible-server/how-to-manage-high-availability-portal#enable-high-availability-during-server-creation
+        href: /azure/postgresql/flexible-server/how-to-manage-high-availability-portal?toc=/azure/reliability#enable-high-availability-during-server-creation
       - name: Azure Elastic SAN
         href: reliability-elastic-san.md#availability-zone-migration
       - name: Azure HDInsight
@@ -84,10 +84,10 @@
         href: /azure/service-bus-messaging/service-bus-outages-disasters#availability-zones?toc=/azure/reliability
       - name: Azure SQL Database
         href: migrate-sql-database.md
+      - name: Azure SQL Managed Instance
+        href: /azure/azure-sql/managed-instance/instance-zone-redundancy-configure
       - name: Azure Storage accounts
         href: migrate-storage.md
-      - name: Azure SQL managed instance
-        href: /azure/azure-sql/managed-instance/instance-zone-redundancy-configure
       - name: Azure Virtual Machines and Virtual Machine Scale Sets
         href: migrate-vm.md
       - name: Workload - Azure Kubernetes and MySQL

articles/reliability/regions-paired.md

@@ -27,7 +27,7 @@ Some Azure services use paired regions to build their multi-region geo-replicati
 If you're in a region with a pair, then using its pair as a secondary region provides several benefits:
 
 - **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.
-- **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.
+- **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.
 - **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).
 
 > [!IMPORTANT]