proof project

Author: Ja-Dunn

articles/azure-sql/database/application-authentication-get-client-id-keys.md

@@ -96,5 +96,5 @@ Write-Output "_applicationSecret:" $secret
 
 ## See also
 
-[Create an Azure SQL Database with C#](design-first-database-csharp-tutorial.md)  
-[Connecting to Azure SQL Database By Using Azure Active Directory Authentication](authentication-aad-overview.md)
+[Create a database in Azure SQL Database with C#](design-first-database-csharp-tutorial.md)  
+[Connect to Azure SQL Database by using Azure Active Directory Authentication](authentication-aad-overview.md)

articles/azure-sql/database/designing-cloud-solutions-for-disaster-recovery.md

@@ -39,7 +39,7 @@ The following diagram shows this configuration before an outage:
 
 ![Scenario 1. Configuration before the outage.](./media/designing-cloud-solutions-for-disaster-recovery/scenario1-a.png)
 
-After an outage in the primary region, the SQL Database service detects that the primary database is not accessible and triggers failover to the secondary region based on the parameters of the automatic failover policy (1). Depending on your application SLA, you can configure a grace period that controls the time between the detection of the outage and the failover itself. It is possible that  traffic manager initiates the endpoint failover before the failover group triggers the failover of the database. In that case the web application cannot immediately reconnect to the database. But the reconnections will automatically succeed as soon as the database failover completes. When the failed region is restored and back online, the old primary automatically reconnects as a new secondary. The diagram below illustrates the configuration after failover.
+After an outage in the primary region, SQL Database detects that the primary database is not accessible and triggers failover to the secondary region based on the parameters of the automatic failover policy (1). Depending on your application SLA, you can configure a grace period that controls the time between the detection of the outage and the failover itself. It is possible that  traffic manager initiates the endpoint failover before the failover group triggers the failover of the database. In that case the web application cannot immediately reconnect to the database. But the reconnections will automatically succeed as soon as the database failover completes. When the failed region is restored and back online, the old primary automatically reconnects as a new secondary. The diagram below illustrates the configuration after failover.
 
 > [!NOTE]
 > All transactions committed after the failover are lost during the reconnection. After the failover is completed, the application in region B is able to reconnect and restart processing the user requests. Both the  web application and the primary database are now in region B and remain co-located.

articles/azure-sql/database/service-tiers-general-purpose-business-critical.md

@@ -42,7 +42,7 @@ The following table describes the key differences between service tiers for the
 | **Database size** | SQL Database | 5 GB – 4 TB | Up to 100 TB | 5 GB – 4 TB |
 | | SQL Managed Instance  | 32 GB – 8 TB | N/A | 32 GB – 4 TB |
 | **Storage size** | SQL Database | 5 GB – 4 TB | Up to 100 TB | 5 GB – 4 TB |
-| | SQL Managed instance  | 32 GB – 8 TB | N/A | 32 GB – 4 TB |
+| | SQL Managed Instance  | 32 GB – 8 TB | N/A | 32 GB – 4 TB |
 | **TempDB size** | SQL Database | [32 GB per vCore](resource-limits-vcore-single-databases.md#general-purpose---provisioned-compute---gen4) | [32 GB per vCore](resource-limits-vcore-single-databases.md#hyperscale---provisioned-compute---gen5) | [32 GB per vCore](resource-limits-vcore-single-databases.md#business-critical---provisioned-compute---gen4) |
 | | SQL Managed Instance  | [24 GB per vCore](../managed-instance/resource-limits.md#service-tier-characteristics) | N/A | Up to 4 TB - [limited by storage size](../managed-instance/resource-limits.md#service-tier-characteristics) |
 | **Log write throughput** | SQL Database | [1.875 MB/s per vCore (max 30 MB/s)](resource-limits-vcore-single-databases.md#general-purpose---provisioned-compute---gen4) | 100 MB/s | [6 MB/s per vCore (max 96 MB/s)](resource-limits-vcore-single-databases.md#business-critical---provisioned-compute---gen4) |
@@ -95,6 +95,6 @@ Storage for database backups is allocated to support the point-in-time restore (
 For details about the specific compute and storage sizes available in the general purpose and business critical service tiers, see: 
 
 - [vCore-based resource limits for Azure SQL Database](resource-limits-vcore-single-databases.md).
-- [vCore-based resource limits for pooled Azure SQL Databases](resource-limits-vcore-elastic-pools.md).
+- [vCore-based resource limits for pooled databases in Azure SQL Database](resource-limits-vcore-elastic-pools.md).
 - [vCore-based resource limits for Azure SQL Managed Instance](../managed-instance/resource-limits.md).