debuglevel
diff --git a/‎azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md‎
Lines changed: 4 additions & 2 deletions b/‎azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md‎
Lines changed: 4 additions & 2 deletions
diff --git a/‎azure-sql/database/designing-cloud-solutions-for-disaster-recovery.md‎
Lines changed: 2 additions & 3 deletions b/‎azure-sql/database/designing-cloud-solutions-for-disaster-recovery.md‎
Lines changed: 2 additions & 3 deletions
diff --git a/‎azure-sql/database/disaster-recovery-drills.md‎
Lines changed: 3 additions & 2 deletions b/‎azure-sql/database/disaster-recovery-drills.md‎
Lines changed: 3 additions & 2 deletions
@@ -103,7 +103,7 @@ Use auto-failover groups if your application meets any of these criteria:
 
 You may choose to use a combination of database backups and active geo-replication depending upon your application requirements. For a discussion of design considerations for stand-alone databases and for elastic pools using these business continuity features, see [Design an application for cloud disaster recovery](designing-cloud-solutions-for-disaster-recovery.md) and [Elastic pool disaster recovery strategies](disaster-recovery-strategies-for-applications-with-elastic-pool.md).
 
-The following sections provide an overview of the steps to recover using either database backups or active geo-replication. For detailed steps including planning requirements, post recovery steps, and information about how to simulate an outage to perform a disaster recovery drill, see [Recover a database in SQL Database from an outage](disaster-recovery-guidance.md).
+The following sections provide an overview of the steps to recover using either database backups or active geo-replication. For detailed steps including planning requirements, post recovery steps, and information about how to simulate an outage to perform a disaster recovery drill, see [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md).
 
 ### Prepare for an outage
 
@@ -124,7 +124,7 @@ If you are using active geo-replication or auto-failover groups as your recovery
 
 ### Perform a geo-restore
 
-If you are using the automated backups with geo-redundant storage (enabled by default), you can recover the database using [geo-restore](disaster-recovery-guidance.md#recover-using-geo-restore). Recovery usually takes place within 12 hours - with data loss of up to one hour determined by when the last log backup was taken and replicated. Until the recovery completes, the database is unable to record any transactions or respond to any queries. Note, geo-restore only restores the database to the last available point in time.
+If you are using the automated backups with geo-redundant storage (enabled by default), you can recover the database using [geo-restore](recovery-using-backups.md#geo-restore). Recovery usually takes place within 12 hours - with data loss of up to one hour determined by when the last log backup was taken and replicated. Until the recovery completes, the database is unable to record any transactions or respond to any queries. Note, geo-restore only restores the database to the last available point in time.
 
 > [!NOTE]
 > If the datacenter comes back online before you switch your application over to the recovered database, you can cancel the recovery.
@@ -149,3 +149,5 @@ Sometimes an application must be taken offline because of planned maintenance su
 ## Next steps
 
 For a discussion of application design considerations for single databases and for elastic pools, see [Design an application for cloud disaster recovery](designing-cloud-solutions-for-disaster-recovery.md) and [Elastic pool disaster recovery strategies](disaster-recovery-strategies-for-applications-with-elastic-pool.md).
+
+Review the [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md) and [Azure SQL Database high availability and disaster recovery checklist](high-availability-disaster-recovery-checklist.md).
@@ -52,13 +52,12 @@ After an outage in the primary region, SQL Database detects that the primary dat
 If an outage happens in region B, the replication process between the primary and the secondary database gets suspended but the link between the two remains intact (1). Traffic Manager detects that connectivity to Region B is broken and marks the endpoint web app 2 as Degraded (2). The application's performance is not impacted in this case, but the database becomes exposed and therefore at higher risk of data loss in case region A fails in succession.
 
 > [!NOTE]
-> For disaster recovery, we recommend the configuration with application deployment limited to two regions. This is because most of the Azure geographies have only two regions. This configuration does not protect your application from a simultaneous catastrophic failure of both regions. In an unlikely event of such a failure, you can recover your databases in a third region using [geo-restore operation](disaster-recovery-guidance.md#recover-using-geo-restore).
->
+> For disaster recovery, we recommend the configuration with application deployment limited to two regions. This is because most of the Azure geographies have only two regions. This configuration does not protect your application from a simultaneous catastrophic failure of both regions. In an unlikely event of such a failure, you can recover your databases in a third region using [geo-restore operation](recovery-using-backups.md#geo-restore). For more information, see [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md).
 
  Once the outage is mitigated, the secondary database automatically resynchronizes with the primary. During synchronization, performance of the primary can be impacted. The specific impact depends on the amount of data the new primary acquired since the failover. 
 
 > [!NOTE]
-> After the outage is mitigated, Traffic  Manager will start routing the connections to the application in Region A as a higher priority end-point. If you intend to keep the primary in Region B for a while, you should change the priority table in the Trafic Manager profile accordingly. 
+> After the outage is mitigated, Traffic  Manager will start routing the connections to the application in Region A as a higher priority end-point. If you intend to keep the primary in Region B for a while, you should change the priority table in the Traffic Manager profile accordingly. 
 >
  
  The following diagram illustrates an outage in the secondary region:
 
@@ -32,8 +32,8 @@ To simulate the outage, you can rename the source database. This name change cau
 
 ### Recovery
 
-* Perform the geo-restore of the database into a different server as described [here](disaster-recovery-guidance.md).
-* Change the application configuration to connect to the recovered database and follow the [Configure a database after recovery](disaster-recovery-guidance.md) guide to complete the recovery.
+* Perform the geo-restore of the database into a different server as described in [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md).
+* Change the application configuration to connect to the recovered database and follow the [Configure a database after recovery](disaster-recovery-guidance.md#configure-your-database-after-recovery) guide to complete the recovery.
 
 ### Validation
 
@@ -63,3 +63,4 @@ Complete the drill by verifying the application integrity post recovery (includi
 * To learn about Azure SQL Database automated backups, see [SQL Database automated backups](automated-backups-overview.md)
 * To learn about using automated backups for recovery, see [restore a database from the service-initiated backups](recovery-using-backups.md).
 * To learn about faster recovery options, see [Active geo-replication](active-geo-replication-overview.md) and [Auto-failover groups](auto-failover-group-sql-db.md).
+* Review [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md) and the [Azure SQL Database high availability and disaster recovery checklist](high-availability-disaster-recovery-checklist.md).