Merge branch 'sql-database-batch2' of https://github.com/paulth1/azure-docs-pr into sql-database-batch2

Author: paulth1

articles/azure-sql/database/elastic-scale-data-dependent-routing.md

@@ -12,10 +12,10 @@ ms.author: sstein
 ms.reviewer:
 ms.date: 01/25/2019
 ---
-# Use Data-dependent routing to route a query to an appropriate database
+# Use data-dependent routing to route a query to an appropriate database
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-**Data-dependent routing** is the ability to use the data in a query to route the request to an appropriate database. Data-dependent routing is a fundamental pattern when working with sharded databases. The request context may also be used to route the request, especially if the sharding key is not part of the query. Each specific query or transaction in an application using data-dependent routing is restricted to accessing one database per request. For the Azure SQL Database Elastic tools, this routing is accomplished with the **ShardMapManager** ([Java](/java/api/com.microsoft.azure.elasticdb.shard.mapmanager.shardmapmanager), [.NET](https://docs.microsoft.com/dotnet/api/microsoft.azure.sqldatabase.elasticscale.shardmanagement.shardmapmanager)) class.
+**Data-dependent routing** is the ability to use the data in a query to route the request to an appropriate database. Data-dependent routing is a fundamental pattern when working with sharded databases. The request context may also be used to route the request, especially if the sharding key is not part of the query. Each specific query or transaction in an application using data-dependent routing is restricted to accessing one database per request. For the Azure SQL Database elastic tools, this routing is accomplished with the **ShardMapManager** ([Java](/java/api/com.microsoft.azure.elasticdb.shard.mapmanager.shardmapmanager), [.NET](https://docs.microsoft.com/dotnet/api/microsoft.azure.sqldatabase.elasticscale.shardmanagement.shardmapmanager)) class.
 
 The application does not need to track various connection strings or DB locations associated with different slices of data in the sharded environment. Instead, the [Shard Map Manager](elastic-scale-shard-map-management.md) opens connections to the correct databases when needed, based on the data in the shard map and the value of the sharding key that is the target of the application’s request. The key is typically the *customer_id*, *tenant_id*, *date_key*, or some other specific identifier that is a fundamental parameter of the database request.
 
@@ -171,6 +171,6 @@ Transactional properties are guaranteed for all operations local to a shard. For
 
 ## Next steps
 
-To detach a shard, or to reattach a shard, see [Using the RecoveryManager class to fix shard map problems](elastic-database-recovery-manager.md)
+To detach a shard, or to reattach a shard, see [Using the RecoveryManager class to fix shard map problems](elastic-database-recovery-manager.md).
 
 [!INCLUDE [elastic-scale-include](../../../includes/elastic-scale-include.md)]

articles/azure-sql/database/elastic-scale-working-with-dapper.md

@@ -1,6 +1,6 @@
 ---
-title: Using elastic database client library with Dapper
-description: Using elastic database client library with Dapper.
+title: Using the elastic database client library with Dapper
+description: Using the elastic database client library with Dapper.
 services: sql-database
 ms.service: sql-database
 ms.subservice: scale-out
@@ -12,7 +12,7 @@ ms.author: sstein
 ms.reviewer:
 ms.date: 12/04/2018
 ---
-# Using elastic database client library with Dapper
+# Using the elastic database client library with Dapper
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
 This document is for developers that rely on Dapper to build applications, but also want to embrace [elastic database tooling](elastic-scale-introduction.md) to create applications that implement sharding to scale out their data tier.  This document illustrates the changes in Dapper-based applications that are necessary to integrate with elastic database tools. Our focus is on composing the elastic database shard management and data-dependent routing with Dapper.