edit pass: configure-bcdr-azure-ssis-integration-runtime

Author: ShawnJackson

articles/data-factory/configure-bcdr-azure-ssis-integration-runtime.md

@@ -54,7 +54,7 @@ If you want the Azure-SSIS IR to point to a read/write listener endpoint, you ne
 
 #### Solution
 
-When failover occurs:
+When failover occurs, take the following steps:
 
 1. Stop the Azure-SSIS IR in the primary region.
 
@@ -75,7 +75,7 @@ This scenario is suitable if the Azure-SSIS IR is pointing to a primary server e
 
 #### Solution
 
-When failover occurs:
+When failover occurs, take the following steps:
 
 1. Stop the Azure-SSIS IR in the primary region.
 
@@ -92,13 +92,13 @@ When failover occurs:
 
 3. Restart the Azure-SSIS IR.
 
-### Scenario 3: Azure-SSIS IR is pointing to a public endpoint of an Azure SQL Database managed instance
+### Scenario 3: Azure-SSIS IR is pointing to a public endpoint of a SQL Database managed instance
 
 This scenario is suitable if the Azure-SSIS IR is pointing to a public endpoint of an Azure SQL Database managed instance and it doesn't join to a virtual network. The only difference from scenario 2 is that you don't need to edit virtual network information for the Azure-SSIS IR after failover.
 
 #### Solution
 
-When failover occurs:
+When failover occurs, take the following steps:
 
 1. Stop the Azure-SSIS IR in the primary region.
 
@@ -119,7 +119,7 @@ This scenario is suitable if you want to provision a new Azure-SSIS IR in a seco
 
 #### Solution
 
-When failover occurs:
+When failover occurs, take the following steps.
 
 > [!NOTE]
 > Use PowerShell for step 4 (creation of the IR). If you don't, the Azure portal will report an error that says SSISDB already exists.
@@ -190,7 +190,7 @@ This scenario is suitable if the Azure-SSIS IR is pointing to a primary server e
 
 #### Solution
 
-When failover occurs:
+When failover occurs, take the following steps:
 
 1. Stop the Azure-SSIS IR in the primary region.
 
@@ -213,6 +213,8 @@ This scenario is suitable if you want to provision a new Azure-SSIS IR in a seco
 
 #### Solution
 
+When failover occurs, take the following steps.
+
 > [!NOTE]
 > Use PowerShell for step 4 (creation of the IR). If you don't, the Azure portal will report an error that says SSISDB already exists.