Merge pull request #32108 from rwestMSFT/rw-1017-fix-an-sql

[SCOPED] SQL is "sequel", not "ess-que-ell"

Author: MikeRayMSFT

azure-sql/database/active-geo-replication-configure-portal.md

@@ -1,6 +1,6 @@
 ---
 title: "Tutorial: Geo-replication & failover in portal"
-description: Learn how to configure geo-replication for an SQL database using the Azure portal or Azure CLI, and initiate failover.
+description: Learn how to configure geo-replication for a SQL database using the Azure portal or Azure CLI, and initiate failover.
 author: rajeshsetlem
 ms.author: rsetlem
 ms.reviewer: wiassaf, mathoma, randolphwest

azure-sql/database/authentication-aad-directory-readers-role-tutorial.md

@@ -78,7 +78,7 @@ For subsequent steps, the Global Administrator or Privileged Role Administrator
 
 1. Go to the **Microsoft Entra ID** resource. Under **Managed**, go to **Groups**. Select the group that you created. Under the **Managed** setting of your group, select **Members**. Select **Add members** and add your SQL Managed Instance service principal as a member of the group by searching for the name found above.
 
-   :::image type="content" source="media/authentication-aad-directory-readers-role/azure-ad-add-managed-instance-service-principal.png" alt-text="Screenshot of the Members page for a Microsoft Entra resource with the options highlighted for adding an SQL Managed instance as a new member.":::
+   :::image type="content" source="media/authentication-aad-directory-readers-role/azure-ad-add-managed-instance-service-principal.png" alt-text="Screenshot of the Members page for a Microsoft Entra resource with the options highlighted for adding a SQL Managed instance as a new member.":::
 
 > [!NOTE]
 > It can take a few minutes to propagate the service principal permissions through the Azure system, and allow access to Microsoft Graph API. You may have to wait a few minutes before you provision a Microsoft Entra admin for SQL Managed Instance.

azure-sql/database/az-cli-script-samples-content-guide.md

@@ -46,7 +46,7 @@ The following table includes links to Azure CLI script examples to manage single
 |Area|Description|
 |---|---|
 |**Create databases**||
-| [Create a single database](scripts/create-and-configure-database-cli.md) | Creates an SQL Database and configures a server-level firewall rule. |
+| [Create a single database](scripts/create-and-configure-database-cli.md) | Creates a SQL Database and configures a server-level firewall rule. |
 | [Create pooled databases](scripts/move-database-between-elastic-pools-cli.md) | Creates elastic pools, moves pooled databases, and changes compute sizes. |
 |**Scale databases**||
 | [Scale a single database](scripts/monitor-and-scale-database-cli.md) | Scales single database. |

azure-sql/database/connect-query-java.md

@@ -156,7 +156,7 @@ password=$AZ_SQL_SERVER_PASSWORD
 - Replace the two `$AZ_DATABASE_NAME` variables with the value that you configured at the beginning of this article.
 - Replace the `$AZ_SQL_SERVER_PASSWORD` variable with the value that you configured at the beginning of this article.
 
-### Create an SQL file to generate the database schema
+### Create a SQL file to generate the database schema
 
 We will use a *src/main/resources/`schema.sql`* file in order to create a database schema. Create that file, with the following content:
 

azure-sql/database/elastic-pool-manage.md

@@ -79,7 +79,7 @@ To create and manage SQL Database elastic pools with [Azure CLI](/cli/azure), us
 
 ## Transact-SQL (T-SQL)
 
-To create and move databases within existing elastic pools or to return information about an SQL Database elastic pool with Transact-SQL, use the following T-SQL commands. You can issue these commands using the Azure portal, [SQL Server Management Studio](/sql/ssms/use-sql-server-management-studio), [Visual Studio Code](https://code.visualstudio.com/docs), or any other program that can connect to a server and pass Transact-SQL commands. To create and manage firewall rules using T-SQL, see [Manage firewall rules using Transact-SQL](firewall-configure.md#use-transact-sql-to-manage-ip-firewall-rules).
+To create and move databases within existing elastic pools or to return information about a SQL Database elastic pool with Transact-SQL, use the following T-SQL commands. You can issue these commands using the Azure portal, [SQL Server Management Studio](/sql/ssms/use-sql-server-management-studio), [Visual Studio Code](https://code.visualstudio.com/docs), or any other program that can connect to a server and pass Transact-SQL commands. To create and manage firewall rules using T-SQL, see [Manage firewall rules using Transact-SQL](firewall-configure.md#use-transact-sql-to-manage-ip-firewall-rules).
 
 > [!IMPORTANT]  
 > You cannot create, update, or delete an Azure SQL Database elastic pool using Transact-SQL. You can add or remove databases from an elastic pool, and you can use DMVs to return information about existing elastic pools.

azure-sql/database/saas-dbpertenant-get-started-deploy.md

@@ -200,7 +200,7 @@ The initial deployment creates three sample tenants. Now you create another tena
 
 The new tenant database is:
 
-- Created in an SQL elastic pool.
+- Created in a SQL elastic pool.
 - Initialized.
 - Registered in the catalog.
 

azure-sql/database/saas-tenancy-tenant-analytics.md

@@ -36,7 +36,7 @@ Multi-tenant SaaS applications typically have a vast amount of tenant data store
 
 Accessing data for all tenants is simple when all the data is in just one multi-tenant database. But the access is more complex when distributed at scale across potentially thousands of databases. One way to tame the complexity and to minimize the impact of analytics queries on transactional data is to extract data into a purpose designed analytics database or data warehouse.
 
-This tutorial presents a complete analytics scenario for Wingtip Tickets SaaS application. First, *Elastic Jobs* is used to extract data from each tenant database and load it into staging tables in an analytics store. The analytics store could either be an SQL Database or a dedicated SQL pool. For large-scale data extraction, [Azure Data Factory](/azure/data-factory/introduction) is recommended.
+This tutorial presents a complete analytics scenario for Wingtip Tickets SaaS application. First, *Elastic Jobs* is used to extract data from each tenant database and load it into staging tables in an analytics store. The analytics store could either be a SQL Database or a dedicated SQL pool. For large-scale data extraction, [Azure Data Factory](/azure/data-factory/introduction) is recommended.
 
 Next, the aggregated data is transformed into a set of [star-schema](https://www.wikipedia.org/wiki/Star_schema) tables. The tables consist of a central fact table plus related dimension tables.  For Wingtip Tickets:
 

azure-sql/database/security-overview.md

@@ -123,7 +123,7 @@ In Azure, all newly created databases are encrypted by default and the database
 
 ### Always Encrypted (Encryption-in-use)
 
-![Diagram showing the basics of the Always Encrypted feature. An SQL database with a lock is only accessed by an app containing a key.](./media/security-overview/azure-database-ae.png)
+![Diagram showing the basics of the Always Encrypted feature. A SQL database with a lock is only accessed by an app containing a key.](./media/security-overview/azure-database-ae.png)
 
 [Always Encrypted](/sql/relational-databases/security/encryption/always-encrypted-database-engine) is a feature designed to protect sensitive data stored in specific database columns from access (for example, credit card numbers, national/regional identification numbers, or data on a _need to know_ basis). This includes database administrators or other privileged users who are authorized to access the database to perform management tasks, but have no business need to access the particular data in the encrypted columns. The data is always encrypted, which means the encrypted data is decrypted only for processing by client applications with access to the encryption key. The encryption key is never exposed to SQL Database or SQL Managed Instance and can be stored either in the [Windows Certificate Store](always-encrypted-certificate-store-configure.md) or in [Azure Key Vault](always-encrypted-azure-key-vault-configure.md).
 

azure-sql/includes/passwordless-connect-azure-sql-mssql.md

@@ -1,7 +1,7 @@
 The following steps are required to connect the App Service instance to Azure SQL Database:
 
 1. Create a managed identity for the App Service.
-1. Create an SQL database user and associate it with the App Service managed identity.
+1. Create a SQL database user and associate it with the App Service managed identity.
 1. Assign SQL roles to the database user that allow for read, write, and potentially other permissions.
 
 There are multiple tools available to implement these steps:
@@ -72,7 +72,7 @@ The Azure portal allows you to work with managed identities and run queries agai
 
     :::image type="content" source="../database/media/passwordless-connections/query-editor-small.png" lightbox="../database/media/passwordless-connections/query-editor.png" alt-text="A screenshot showing how to use the Azure Query editor.":::
 
-    This SQL script creates an SQL database user that maps back to the managed identity of your App Service instance. It also assigns the necessary SQL roles to the user to allow your app to read, write, and modify the data and schema of your database. After this step is completed, your services are connected.
+    This SQL script creates a SQL database user that maps back to the managed identity of your App Service instance. It also assigns the necessary SQL roles to the user to allow your app to read, write, and modify the data and schema of your database. After this step is completed, your services are connected.
 
 > [!IMPORTANT]
 > Although this solution provides a simple approach for getting started, it's not a best practice for production-grade environments. In those scenarios, the app shouldn't perform all operations using a single, elevated identity. You should try to implement the principle of least privilege by configuring multiple identities with specific permissions for specific tasks.

azure-sql/managed-instance/transact-sql-tsql-differences-sql-server.md

@@ -416,7 +416,7 @@ Further, [CREATE EXTERNAL TABLE AS SELECT (CETAS)](/sql/t-sql/statements/create-
 For more information about configuring transactional replication, see the following tutorials:
 
 - [Replication between a SQL MI publisher and SQL MI subscriber](replication-between-two-instances-configure-tutorial.md)
-- [Replication between an SQL MI publisher, SQL MI distributor, and SQL Server subscriber](replication-two-instances-and-sql-server-configure-tutorial.md)
+- [Replication between a SQL MI publisher, SQL MI distributor, and SQL Server subscriber](replication-two-instances-and-sql-server-configure-tutorial.md)
 
 ### RESTORE statement