Updating considerations

Can now have distribution database in AG

Author: briancarrig

docs/database-engine/availability-groups/windows/replicate-track-change-data-capture-always-on-availability.md

@@ -211,7 +211,7 @@ If Change Data Capture needs to be disabled on a database which is part of an Al
 
 ### Considerations  
 
--   The distribution database is not supported for use with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] or database mirroring. Replication configuration is coupled to the SQL Server instance where the Distributor is configured; therefore the distribution database cannot be mirrored or replicated. To provide high availability for the Distributor, use a SQL Server failover cluster. For more information, see [Always On Failover Cluster Instances (SQL Server)](../../../sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server.md).  
+-   The distribution database is not supported for use with database mirroring but is supported with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] subject to certain limitations, see [Configure Distribution Availability Group](../../../relational-databases/replication/configure-distribution-availability-group.md#Limitations-or-exclusions). Replication configuration is coupled to the SQL Server instance where the Distributor is configured; therefore the distribution database cannot be mirrored or replicated. It is also possible to provide high availability for the Distributor using a SQL Server failover cluster. For more information, see [Always On Failover Cluster Instances (SQL Server)](../../../sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server.md).  
 
 -   Subscriber failover to a secondary database, while supported, is a manual procedure for merge replication subscribers. The procedure is essentially identical to the method used to fail over a mirrored subscriber database. Transactional replication subscribers do not need special handling while participating in [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. Subscribers must be running [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)] or later to participate in an availability group.  For more information, see [Replication Subscribers and Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/replication-subscribers-and-always-on-availability-groups-sql-server.md)