fixing warnings and more casing

MashaMSFT · MashaMSFT · commit 659642df9e79 · 2022-01-21T14:34:47.000-08:00
diff --git a/azure-sql/database/purchasing-models.md b/azure-sql/database/purchasing-models.md
@@ -18,7 +18,7 @@ ms.date: 01/31/2022
 
 Azure SQL Database lets you easily purchase a fully managed platform as a service (PaaS) database engine that fits your performance and cost needs. Depending on the deployment model you've chosen for Azure SQL Database, you can select the purchasing model that works for you:
 
-- [Virtual core (vCore)-based purchasing model](service-tiers-sql-database-vcore.md) (recommended). This purchasing model provides a choice between a provisioned compute tier and a serverless compute tier. With the provisioned compute tier, you choose the exact amount of compute resources that are always provisioned for your workload. With the serverless compute tier, you specify the autoscaling of the compute resources over a configurable compute range. The serverless compute tier automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns. The vCore unit price per unit of time is lower in the provisioned compute tier than it is in the serverless compute tier. The [Hyperscale service tier](service-tier-Hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
+- [Virtual core (vCore)-based purchasing model](service-tiers-sql-database-vcore.md) (recommended). This purchasing model provides a choice between a provisioned compute tier and a serverless compute tier. With the provisioned compute tier, you choose the exact amount of compute resources that are always provisioned for your workload. With the serverless compute tier, you specify the autoscaling of the compute resources over a configurable compute range. The serverless compute tier automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns. The vCore unit price per unit of time is lower in the provisioned compute tier than it is in the serverless compute tier. The [Hyperscale service tier](service-tier-hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
 - [Database transaction unit (DTU)-based purchasing model](service-tiers-dtu.md). This purchasing model provides bundled compute and storage packages balanced for common workloads.
 
 ## Purchasing models
@@ -43,7 +43,7 @@ The following table and chart compares and contrasts the vCore-based and the DTU
 
 A virtual core (vCore) represents a logical CPU and offers you the option to choose between generations of hardware and the physical characteristics of the hardware (for example, the number of cores, the memory, and the storage size). The vCore-based purchasing model gives you flexibility, control, transparency of individual resource consumption, and a straightforward way to translate on-premises workload requirements to the cloud. This model allows you to choose compute, memory, and storage resources based on your workload needs.
 
-In the vCore-based purchasing model for SQL Database, you can choose between the General Purpose and Business Critical service tiers. Review [service tiers](service-tiers-sql-database-vcore.md#service-tiers) to learn more.  For single databases, you can also choose the [Hyperscale service tier](service-tier-Hyperscale.md).
+In the vCore-based purchasing model for SQL Database, you can choose between the General Purpose and Business Critical service tiers. Review [service tiers](service-tiers-sql-database-vcore.md#service-tiers) to learn more.  For single databases, you can also choose the [Hyperscale service tier](service-tier-hyperscale.md).
 
 In the vCore-based purchasing model, you pay for:
 
diff --git a/azure-sql/database/resource-limits-logical-server.md b/azure-sql/database/resource-limits-logical-server.md
@@ -185,7 +185,7 @@ Log rate governor traffic shaping is surfaced via the following wait types (expo
 
 When encountering a log rate limit that is hampering desired scalability, consider the following options:
 
-- Scale up to a higher service level in order to get the maximum log rate of a service tier, or switch to a different service tier. The [Hyperscale](service-tier-Hyperscale.md) service tier provides 100 MB/s log rate regardless of chosen service level.
+- Scale up to a higher service level in order to get the maximum log rate of a service tier, or switch to a different service tier. The [Hyperscale](service-tier-hyperscale.md) service tier provides 100 MB/s log rate regardless of chosen service level.
 - If data being loaded is transient, such as staging data in an ETL process, it can be loaded into tempdb (which is minimally logged).
 - For analytic scenarios, load into a clustered [columnstore](/sql/relational-databases/indexes/columnstore-indexes-overview) table, or a table with indexes that use [data compression](/sql/relational-databases/data-compression/data-compression). This reduces the required log rate. This technique does increase CPU utilization and is only applicable to data sets that benefit from clustered columnstore indexes or data compression.
 
diff --git a/azure-sql/database/service-tier-business-critical.md b/azure-sql/database/service-tier-business-critical.md
@@ -1,5 +1,5 @@
 ---
-title: Business critical service tier
+title: Business Critical service tier
 titleSuffix:  Azure SQL Database & Azure SQL Managed Instance
 description: Learn about the Business Critical service tier for Azure SQL Database and Azure SQL Managed Instance. 
 services: sql-database
@@ -13,7 +13,7 @@ ms.author: danil
 ms.reviewer: kendralittle, mathoma, urmilano
 ms.date: 01/31/2022
 ---
-# Business critical tier - Azure SQL Database and Azure SQL Managed Instance 
+# Business Critical tier - Azure SQL Database and Azure SQL Managed Instance 
 [!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 Azure SQL Database and Azure SQL Managed Instance are both based on the SQL Server database engine architecture adjusted for the cloud environment in order to ensure default SLA availability even in cases of infrastructure failures. 
@@ -71,6 +71,6 @@ To learn more, review [single database resource limits](resource-limits-vcore-si
 ## Next steps
 
 - Find resource characteristics (number of cores, I/O, memory) of Business Critical tier in [SQL Managed Instance](../managed-instance/resource-limits.md#service-tier-characteristics), Single database in [vCore model](resource-limits-vcore-single-databases.md) or [DTU model](resource-limits-dtu-single-databases.md#premium-service-tier), or Elastic pool in [vCore model](resource-limits-vcore-elastic-pools.md) and [DTU model](resource-limits-dtu-elastic-pools.md#premium-elastic-pool-limits).
-- Learn about [General Purpose](service-tier-general-purpose.md) and [Hyperscale](service-tier-Hyperscale.md) service tiers.
+- Learn about [General Purpose](service-tier-general-purpose.md) and [Hyperscale](service-tier-hyperscale.md) service tiers.
 - Learn about [Service Fabric](../../service-fabric/service-fabric-overview.md).
 - For more options for high availability and disaster recovery, see [Business Continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md).
diff --git a/azure-sql/database/service-tier-general-purpose.md b/azure-sql/database/service-tier-general-purpose.md
@@ -1,5 +1,5 @@
 ---
-title: General purpose service tier
+title: General Purpose service tier
 titleSuffix: Azure SQL Database & Azure SQL Managed Instance 
 description: Learn about the General Purpose service tier for Azure SQL Database and Azure SQL Managed Instance. 
 services: sql-database
@@ -13,7 +13,7 @@ ms.author: danil
 ms.reviewer: kendralittle, mathoma, urmilano
 ms.date: 01/31/2022
 ---
-# General purpose service tier - Azure SQL Database and Azure SQL Managed Instance
+# General Purpose service tier - Azure SQL Database and Azure SQL Managed Instance
 [!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 Azure SQL Database and Azure SQL Managed Instance are based on the SQL Server database engine architecture adapted for the cloud environment in order to ensure default availability even in the cases of infrastructure failures. 
@@ -66,6 +66,6 @@ To learn more, review [single database resource limits](resource-limits-vcore-si
 ## Next steps
 
 - Find resource characteristics (number of cores, I/O, memory) of the General Purpose/standard tier in [SQL Managed Instance](../managed-instance/resource-limits.md#service-tier-characteristics), single database in [vCore model](resource-limits-vcore-single-databases.md) or [DTU model](resource-limits-dtu-single-databases.md#single-database-storage-sizes-and-compute-sizes), or elastic pool in [vCore model](resource-limits-vcore-elastic-pools.md) and [DTU model](resource-limits-dtu-elastic-pools.md#standard-elastic-pool-limits).
-- Learn about [Business Critical](service-tier-business-critical.md) and [Hyperscale](service-tier-Hyperscale.md) service tiers.
+- Learn about [Business Critical](service-tier-business-critical.md) and [Hyperscale](service-tier-hyperscale.md) service tiers.
 - Learn about [Service Fabric](../../service-fabric/service-fabric-overview.md).
 - For more options for high availability and disaster recovery, see [Business Continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md).
diff --git a/azure-sql/database/service-tier-hyperscale.md b/azure-sql/database/service-tier-hyperscale.md
@@ -37,7 +37,7 @@ The Hyperscale service tier in Azure SQL Database provides the following additio
 - Nearly instantaneous database backups (based on file snapshots stored in Azure Blob storage) regardless of size with no IO impact on compute resources  
 - Fast database restores (based on file snapshots) in minutes rather than hours or days (not a size of data operation)
 - Higher overall performance due to higher transaction log throughput and faster transaction commit times regardless of data volumes
-- Rapid scale out - you can provision one or more [read-only replicas](service-tier-Hyperscale-replicas.md) for offloading your read workload and for use as hot-standbys
+- Rapid scale out - you can provision one or more [read-only replicas](service-tier-hyperscale-replicas.md) for offloading your read workload and for use as hot-standbys
 - Rapid Scale up - you can, in constant time, scale up your compute resources to accommodate heavy workloads when needed, and then scale the compute resources back down when not needed.
 
 The Hyperscale service tier removes many of the practical limits traditionally seen in cloud databases. Where most other databases are limited by the resources available in a single node, databases in the Hyperscale service tier have no such limits. With its flexible storage architecture, storage grows as needed. In fact, Hyperscale databases aren't created with a defined max size. A Hyperscale database grows as needed - and you're billed only for the capacity you use. For read-intensive workloads, the Hyperscale service tier provides rapid scale-out by provisioning additional replicas as needed for offloading read workloads.
@@ -105,7 +105,7 @@ Azure Storage contains all data files in a database. Page servers keep data file
 
 Backups are file-snapshot based and hence they're nearly instantaneous. Storage and compute separation enables pushing down the backup/restore operation to the storage layer to reduce the processing burden on the primary compute replica. As a result, database backup doesn't impact performance of the primary compute node. Similarly, point in time recovery (PITR) is done by reverting to file snapshots, and as such is not a size of data operation. Restore of a Hyperscale database in the same Azure region is a constant-time operation, and even multiple-terabyte databases can be restored in minutes instead of hours or days. Creation of new databases by restoring an existing backup also takes advantage of this feature: creating database copies for development or testing purposes, even of multi-terabyte databases, is doable in minutes.
 
-For geo-restore of Hyperscale databases, see [Restoring a Hyperscale database to a different region](#restoring-a-Hyperscale-database-to-a-different-region).
+For geo-restore of Hyperscale databases, see [Restoring a Hyperscale database to a different region](#restoring-a-hyperscale-database-to-a-different-region).
 
 ## Scale and performance advantages
 
@@ -115,7 +115,7 @@ With the ability to rapidly spin up/down additional read-only compute nodes, the
 
 A Hyperscale database can be created using the [Azure portal](https://portal.azure.com), [T-SQL](/sql/t-sql/statements/create-database-transact-sql), [PowerShell](/powershell/module/azurerm.sql/new-azurermsqldatabase), or [CLI](/cli/azure/sql/db#az_sql_db_create). Hyperscale databases are available only using the [vCore-based purchasing model](service-tiers-vcore.md).
 
-The following T-SQL command creates a Hyperscale database. You must specify both the edition and service objective in the `CREATE DATABASE` statement. Refer to the [resource limits](./resource-limits-vcore-single-databases.md#Hyperscale---provisioned-compute---gen4) for a list of valid service objectives.
+The following T-SQL command creates a Hyperscale database. You must specify both the edition and service objective in the `CREATE DATABASE` statement. Refer to the [resource limits](./resource-limits-vcore-single-databases.md#hyperscale---provisioned-compute---gen4) for a list of valid service objectives.
 
 ```sql
 -- Create a Hyperscale Database
@@ -191,7 +191,7 @@ These are the current limitations to the Hyperscale service tier as of GA.  We'r
 
 ## Next steps
 
-- For an FAQ on Hyperscale, see [Frequently asked questions about Hyperscale](service-tier-Hyperscale-frequently-asked-questions-faq.yml).
+- For an FAQ on Hyperscale, see [Frequently asked questions about Hyperscale](service-tier-hyperscale-frequently-asked-questions-faq.yml).
 - For information about service tiers, see [Service tiers](purchasing-models.md)
 - See [Overview of resource limits on a server](resource-limits-logical-server.md) for information about limits at the server and subscription levels.
 - For purchasing model limits for a single database, see [Azure SQL Database vCore-based purchasing model limits for a single database](resource-limits-vcore-single-databases.md).
diff --git a/azure-sql/database/service-tiers-sql-database-vcore.md b/azure-sql/database/service-tiers-sql-database-vcore.md
@@ -40,7 +40,7 @@ Service tier options in the vCore purchasing model include General Purpose, Busi
 
 For greater details, review resource limits for [logical server](resource-limits-logical-server.md), [single databases](resource-limits-vcore-single-databases.md), and [pooled databases](resource-limits-vcore-elastic-pools.md). 
 
-|**Use case**|**General purpose**|**Business critical**|**Hyperscale**|
+|**Use case**|**General Purpose**|**Business Critical**|**Hyperscale**|
 |---|---|---|---|
 |**Best for**|Most business workloads. Offers budget-oriented, balanced, and scalable compute and storage options. |Offers business applications the highest resilience to failures by using several isolated replicas, and provides the highest I/O performance per database replica.|Most business workloads with highly scalable storage and read-scale requirements.  Offers higher resilience to failures by allowing configuration of more than one isolated database replica. |
 |**Availability**|1 replica, no read-scale replicas, <br/>zone-redundant high availability (HA) (preview)|3 replicas, 1 [read-scale replica](read-scale-out.md),<br/>zone-redundant high availability (HA)|
@@ -58,7 +58,7 @@ For information on selecting a service tier for your particular workload, see th
 
 - [When to choose the General Purpose service tier](service-tier-general-purpose.md#when-to-choose-this-service-tier)
 - [When to choose the Business Critical service tier](service-tier-business-critical.md#when-to-choose-this-service-tier)
-- [When to choose the Hyperscale service tier](service-tier-Hyperscale.md#who-should-consider-the-Hyperscale-service-tier)
+- [When to choose the Hyperscale service tier](service-tier-hyperscale.md#who-should-consider-the-Hyperscale-service-tier)
 
 ## Resource limits
 
diff --git a/azure-sql/database/sql-database-paas-overview.md b/azure-sql/database/sql-database-paas-overview.md
@@ -45,7 +45,7 @@ SQL Database delivers predictable performance with multiple resource types, serv
 ## Scalable performance and pools
 
 You can define the amount of resources assigned. 
-- With single databases, each database is isolated from others and is portable. Each has its own guaranteed amount of compute, memory, and storage resources. The amount of the resources assigned to the database is dedicated to that database, and isn't shared with other databases in Azure. You can dynamically [scale single database resources](single-database-scale.md) up and down. The single database option provides different compute, memory, and storage resources for different needs. For example, you can get 1 to 80 vCores, or 32 GB to 4 TB. The [Hyperscale service tier](service-tier-Hyperscale.md) for single databases enables you to scale to 100 TB, with fast backup and restore capabilities.
+- With single databases, each database is isolated from others and is portable. Each has its own guaranteed amount of compute, memory, and storage resources. The amount of the resources assigned to the database is dedicated to that database, and isn't shared with other databases in Azure. You can dynamically [scale single database resources](single-database-scale.md) up and down. The single database option provides different compute, memory, and storage resources for different needs. For example, you can get 1 to 80 vCores, or 32 GB to 4 TB. The [Hyperscale service tier](service-tier-hyperscale.md) for single databases enables you to scale to 100 TB, with fast backup and restore capabilities.
 - With elastic pools, you can assign resources that are shared by all databases in the pool. You can create a new database, or move the existing single databases into a resource pool to maximize the use of resources and save money. This option also gives you the ability to dynamically [scale elastic pool resources](elastic-pool-scale.md) up and down.
 
 You can build your first app on a small, single database at a low cost per month in the general-purpose service tier. You can then change its service tier manually or programmatically at any time to the business-critical service tier, to meet the needs of your solution. You can adjust performance without downtime to your app or to your customers. Dynamic scalability enables your database to transparently respond to rapidly changing resource requirements. You pay for only the resources that you need when you need them.
@@ -64,7 +64,7 @@ SQL Database offers the following purchasing models:
 Azure SQL Database offers three service tiers that are designed for different types of applications:
 - [General Purpose/Standard](service-tier-general-purpose.md) service tier designed for common workloads. It offers budget-oriented balanced compute and storage options.
 - [Business Critical/Premium](service-tier-business-critical.md) service tier designed for OLTP applications with high transaction rate and lowest-latency I/O. It offers the highest resilience to failures by using several isolated replicas.
-- [Hyperscale](service-tier-Hyperscale.md) service tier designed for very large OLTP database and the ability to autoscale storage and scale compute fluidly.    
+- [Hyperscale](service-tier-hyperscale.md) service tier designed for very large OLTP database and the ability to autoscale storage and scale compute fluidly.    
 
 ### Elastic pools to maximize resource utilization
 
diff --git a/azure-sql/managed-instance/frequently-asked-questions-faq.yml b/azure-sql/managed-instance/frequently-asked-questions-faq.yml
@@ -257,7 +257,7 @@ sections:
         answer: |
           ### What is the maximum storage size for SQL Managed Instance?
           
-          Storage size for SQL Managed Instance depends on the selected service tier (general purpose or business critical). For storage limitations of these service tiers, see [Service tier characteristics](../database/service-tiers-sql-database-vcore.md#service-tiers).
+          Storage size for SQL Managed Instance depends on the selected service tier (General Purpose or Business Critical). For storage limitations of these service tiers, see [Service tier characteristics](../database/service-tiers-sql-database-vcore.md#service-tiers).
           
           ### What is the minimum storage size available for a managed instance?
           
diff --git a/azure-sql/managed-instance/resource-limits.md b/azure-sql/managed-instance/resource-limits.md
diff --git a/azure-sql/managed-instance/service-tiers-managed-instance-vcore.md b/azure-sql/managed-instance/service-tiers-managed-instance-vcore.md
