Merge pull request #113031 from dimitri-furman/dimitri-furman

Disambiguated "replication"

Author: PRMerger7

articles/sql-database/replication-to-sql-database.md

@@ -10,13 +10,16 @@ ms.topic: conceptual
 author: stevestein
 ms.author: sstein
 ms.reviewer: mathoma
-ms.date: 01/25/2019
+ms.date: 04/28/2020
 ---
 # Replication to SQL Database single and pooled databases
 
 SQL Server replication can be configured to single and pooled databases on a [SQL Database server](sql-database-servers.md) in Azure SQL Database.  
 
-## **Supported Configurations:**
+> [!NOTE]
+> This article describes the use of [transactional replication](https://docs.microsoft.com/sql/relational-databases/replication/transactional/transactional-replication) in Azure SQL Database. It is unrelated to [active geo-replication](https://docs.microsoft.com/azure/sql-database/sql-database-active-geo-replication), an Azure SQL Database feature that allows you to create complete readable replicas of individual databases.
+
+## Supported Configurations
 
 - The SQL Server can be an instance of SQL Server running on-premises or an instance of SQL Server running in an Azure virtual machine in the cloud. For more information, see [SQL Server on Azure Virtual Machines overview](https://azure.microsoft.com/documentation/articles/virtual-machines-sql-server-infrastructure-services/).  
 - The Azure SQL database must be a push subscriber of a SQL Server publisher.  

articles/sql-database/replication-with-sql-database-managed-instance.md

@@ -10,11 +10,14 @@ ms.topic: conceptual
 author: MashaMSFT
 ms.author: ferno
 ms.reviewer: mathoma
-ms.date: 02/07/2019
+ms.date: 04/28/2020
 ---
 # Configure replication in an Azure SQL Database managed instance database
 
-Transactional replication enables you to replicate data into an Azure SQL Database managed instance database from a SQL Server database or another instance database. 
+Transactional replication enables you to replicate data into an Azure SQL Database managed instance database from a SQL Server database or another instance database.
+
+> [!NOTE]
+> This article describes the use of [transactional replication](https://docs.microsoft.com/sql/relational-databases/replication/transactional/transactional-replication) in Azure SQL Managed Instance. It is unrelated to active geo-replication or [failover groups](https://docs.microsoft.com/azure/sql-database/sql-database-auto-failover-group), an Azure SQL Managed Instance feature that allows you to create complete readable replicas of individual instances.
 
 This article shows how to configure replication between a managed instance publisher/distributor and a managed instance subscriber. 
 

articles/sql-database/sql-database-active-geo-replication.md

@@ -10,7 +10,7 @@ ms.topic: conceptual
 author: anosov1960
 ms.author: sashan
 ms.reviewer: mathoma, carlrab
-ms.date: 04/06/2020
+ms.date: 04/28/2020
 ---
 
 # Creating and using active geo-replication
@@ -20,7 +20,12 @@ Active geo-replication is an Azure SQL Database feature that allows you to creat
 > [!NOTE]
 > Active geo-replication is not supported by managed instance. For geographic failover of managed instances, use [Auto-failover groups](sql-database-auto-failover-group.md).
 
-Active geo-replication is designed as a business continuity solution that allows the application to perform quick disaster recovery of individual databases in case of a regional disaster or large scale outage. If geo-replication is enabled, the application can initiate failover to a secondary database in a different Azure region. Up to four secondaries are supported in the same or different regions, and the secondaries can also be used for read-only access queries. The failover must be initiated manually by the application or the user. After failover, the new primary has a different connection end point. The following diagram illustrates a typical configuration of a geo-redundant cloud application using Active geo-replication.
+Active geo-replication is designed as a business continuity solution that allows the application to perform quick disaster recovery of individual databases in case of a regional disaster or large scale outage. If geo-replication is enabled, the application can initiate failover to a secondary database in a different Azure region. Up to four secondaries are supported in the same or different regions, and the secondaries can also be used for read-only access queries. The failover must be initiated manually by the application or the user. After failover, the new primary has a different connection end point. 
+
+> [!NOTE]
+> Active geo-replication replicates changes by streaming database transaction log. It is unrelated to [transactional replication](https://docs.microsoft.com/sql/relational-databases/replication/transactional/transactional-replication), which replicates changes by executing DML (INSERT, UPDATE, DELETE) commands.
+
+The following diagram illustrates a typical configuration of a geo-redundant cloud application using Active geo-replication.
 
 ![active geo-replication](./media/sql-database-active-geo-replication/geo-replication.png )