Merge pull request #115914 from Ja-Dunn/proof-jd-1

edit pass: proof-jd-1

Author: ShawnJackson

articles/azure-sql/database/clustering-model-build-tutorial.md

@@ -72,7 +72,7 @@ In the following R script, you'll use the function **rxKmeans**, which is the K-
 return_cluster = RxSqlServerData(table = "return_cluster", connectionString = connStr);
 # Set the seed for the random number generator for predictability
 set.seed(10);
-# Generate clusters using rxKmeans and output key / cluster to a table in SQL database
+# Generate clusters using rxKmeans and output key / cluster to a table in a database in SQL Database
 # called return_cluster
 clust <- rxKmeans( ~ orderRatio + itemsRatio + monetaryRatio + frequency,
                    customer_returns,

articles/azure-sql/database/resource-limits-vcore-elastic-pools.md

@@ -25,7 +25,7 @@ For DTU purchasing model limits, see [SQL Database DTU resource limits - elastic
 You can set the service tier, compute size, and storage amount using the [Azure portal](elastic-pool-manage.md#azure-portal), [PowerShell](elastic-pool-manage.md#powershell), the [Azure CLI](elastic-pool-manage.md#azure-cli), or the [REST API](elastic-pool-manage.md#rest-api).
 
 > [!IMPORTANT]
-> For scaling guidance and considerations, see [Scale an elastic pool](elastic-pool-scale.md)
+> For scaling guidance and considerations, see [Scale an elastic pool](elastic-pool-scale.md).
 
 ## General purpose - provisioned compute - Gen4
 
@@ -365,7 +365,7 @@ You can set the service tier, compute size, and storage amount using the [Azure
 
 <sup>3</sup> For the max concurrent workers (requests) for any individual database, see [Single database resource limits](resource-limits-vcore-single-databases.md). For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200.  If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
 
-If all vCores of an elastic pool are busy, then each database in the pool receives an equal amount of compute resources to process queries. The SQL Database service provides resource sharing fairness between databases by ensuring equal slices of compute time. Elastic pool resource sharing fairness is in addition to any amount of resource otherwise guaranteed to each database when the vCore min per database is set to a non-zero value.
+If all vCores of an elastic pool are busy, then each database in the pool receives an equal amount of compute resources to process queries. Azure SQL Database provides resource sharing fairness between databases by ensuring equal slices of compute time. Elastic pool resource sharing fairness is in addition to any amount of resource otherwise guaranteed to each database when the vCore min per database is set to a non-zero value.
 
 ## Database properties for pooled databases
 

articles/azure-sql/database/resource-limits-vcore-single-databases.md

@@ -1,6 +1,6 @@
 ---
 title: Single database vCore resource limits 
-description: This page describes some common vCore resource limits for a single Azure SQL Database. 
+description: This page describes some common vCore resource limits for a single database in Azure SQL Database. 
 services: sql-database
 ms.service: sql-database
 ms.subservice: single-database
@@ -480,6 +480,6 @@ The [serverless compute tier](serverless-tier-overview.md) is currently availabl
 - For DTU resource limits for a single database, see [resource limits for single databases using the DTU purchasing model](resource-limits-dtu-single-databases.md)
 - For vCore resource limits for elastic pools, see [resource limits for elastic pools using the vCore purchasing model](resource-limits-vcore-elastic-pools.md)
 - For DTU resource limits for elastic pools, see [resource limits for elastic pools using the DTU purchasing model](resource-limits-dtu-elastic-pools.md)
-- For resource limits for SQL Managed Instances, see [SQL Managed Instance resource limits](../managed-instance/resource-limits.md).
+- For resource limits for SQL Managed Instance, see [SQL Managed Instance resource limits](../managed-instance/resource-limits.md).
 - For information about general Azure limits, see [Azure subscription and service limits, quotas, and constraints](../../azure-resource-manager/management/azure-subscription-service-limits.md).
 - For information about resource limits on a server, see [overview of resource limits on a server](resource-limits-logical-server.md) for information about limits at the server and subscription levels.