[SCOPED] Fix smart quotes

rwestMSFT · rwestMSFT · commit 6e166ba07f0d · 2023-08-21T12:46:41.000-06:00
diff --git a/azure-sql/database/always-encrypted-enclaves-plan.md b/azure-sql/database/always-encrypted-enclaves-plan.md
@@ -43,7 +43,7 @@ SGX enclaves are recommended for workloads that require the strongest data confi
 > [!NOTE]
 > VBS enclaves are available in all Azure SQL Database regions **except**: Jio India Central.
 
-VBS enclaves are the recommended solution for customers who seek protection for data in use from high-privileged users in the customer’s organization, including Database Administrators (DBAs). Without having the cryptographic keys protecting the data, a DBA won't be able to access the data in plaintext.
+VBS enclaves are the recommended solution for customers who seek protection for data in use from high-privileged users in the customer's organization, including Database Administrators (DBAs). Without having the cryptographic keys protecting the data, a DBA won't be able to access the data in plaintext.
 
 VBS enclaves can also help prevent some OS-level threats, such as exfiltrating sensitive data from memory dumps within a VM hosting your database. The plaintext data processed in an enclave doesn't show up in memory dumps, providing the code inside the enclave and its properties haven't been maliciously altered. However, VBS enclaves in Azure SQL Database can't address more sophisticated attacks, such as replacing the enclave binary with malicious code, due to the current lack of enclave attestation. Also, regardless of attestation, VBS enclaves don't provide any protection from attacks using privileged system accounts originating from the host. It's important to note that Microsoft has implemented multiple layers of security controls to detect and prevent such attacks in the Azure cloud, including just-in-time access, multi-factor authentication, and security monitoring. Nevertheless, customers who require strong security isolation may prefer Intel SGX enclaves with the DC-series hardware configuration over VBS enclaves.
 
diff --git a/azure-sql/database/transparent-data-encryption-byok-cross-tenant.md b/azure-sql/database/transparent-data-encryption-byok-cross-tenant.md
@@ -25,7 +25,7 @@ You can configure TDE with CMK for Azure SQL Database for keys stored in key vau
 
 ## Common use scenario
 
-Cross-tenant CMK capabilities allow service providers or independent software vendors (ISV) building services on top of Azure SQL to extend Azure SQL’s TDE with CMK capabilities to their respective customers. With cross-tenant CMK support enabled, ISV customers can own the key vault and encryption keys in their own subscription and Azure AD tenant. The customer has full control over key management operations, while accessing Azure SQL resources in the ISV tenant.
+Cross-tenant CMK capabilities allow service providers or independent software vendors (ISV) building services on top of Azure SQL to extend Azure SQL's TDE with CMK capabilities to their respective customers. With cross-tenant CMK support enabled, ISV customers can own the key vault and encryption keys in their own subscription and Azure AD tenant. The customer has full control over key management operations, while accessing Azure SQL resources in the ISV tenant.
 
 ## Cross-tenant interactions
 
diff --git a/azure-sql/database/transparent-data-encryption-byok-database-level-basic-actions.md b/azure-sql/database/transparent-data-encryption-byok-database-level-basic-actions.md
@@ -464,7 +464,7 @@ GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{
 Retrieve the basic database level customer-managed key settings from a database and the current keys in use
 
 ```rest
-GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}?api-version=2022-08-01-preview&$expand=keys($filter=pointInTime(‘current’))
+GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}?api-version=2022-08-01-preview&$expand=keys($filter=pointInTime('current'))
 ```
 
 Retrieve the basic database level customer-managed key settings from a database and the keys in use at a particular point in time
diff --git a/azure-sql/database/transparent-data-encryption-byok-database-level-geo-replication-restore.md b/azure-sql/database/transparent-data-encryption-byok-database-level-geo-replication-restore.md
@@ -149,7 +149,7 @@ Use a [Custom deployment in the Azure portal](https://portal.azure.com/#create/M
 - Prepopulate the list of current keys in use by the primary database using the following REST API request:
 
     ```rest
-    GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}?api-version=2022-08-01-preview&$expand=keys($filter=pointInTime(‘current’))
+    GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}?api-version=2022-08-01-preview&$expand=keys($filter=pointInTime('current'))
     ```
 
 - Select the user-assigned managed identity (and federated client ID if configuring cross tenant access).
diff --git a/azure-sql/database/transparent-data-encryption-byok-database-level-overview.md b/azure-sql/database/transparent-data-encryption-byok-database-level-overview.md
@@ -40,7 +40,7 @@ As more service providers, also known as independent software vendors (ISVs), us
 
 However, there's one significant limitation to this approach. When multiple databases are hosted on the same Azure SQL logical server, they share the server-level TDE protector. ISVs are unable to offer true customer-managed keys (CMK) capabilities to their customers. Without the ability to manage their own encryption keys, customers may be hesitant to entrust sensitive data to the ISV's service, particularly if compliance regulations require them to maintain full control over their encryption keys.
 
-With database level TDE CMK, ISVs can offer CMK capability to their customers and achieve security isolation, as each database’s TDE protector can potentially be owned by the respective ISV customer in a key vault that they own. The security isolation achieved for ISV’s customers is both in terms of the *key* and the *identity* used to access the key.
+With database level TDE CMK, ISVs can offer CMK capability to their customers and achieve security isolation, as each database's TDE protector can potentially be owned by the respective ISV customer in a key vault that they own. The security isolation achieved for ISV's customers is both in terms of the *key* and the *identity* used to access the key.
 
 The diagram below summarizes the new functionality indicated above. It presents two separate Azure AD tenants. The `Best Services` tenant that contains the Azure SQL logical server with two databases, `DB 1` and `DB 2`, and the `Azure Key Vault 1` with a `Key 1` accessing the database `DB 1` using `UMI 1`. Both `UMI 1` and `Key 1` represent the server level setting. By default, all databases created initially on this server inherit this setting for TDE with CMK. The `Contoso` tenant represents a client tenant that contains `Azure Key Vault 2` with a `Key 2` assessing the database `DB 2` across the tenant as part of the database level CMK cross-tenant support using `Key 2` and `UMI 2` setup for this database.  
 
@@ -124,7 +124,7 @@ In case of an inaccessible TDE protector as described in [Transparent data encry
 
 ### Additional considerations
 
-- If TDE with CMK is already enabled at the server level, setting CMK for a particular database overrides the server level CMK setting (database’s DEK gets re-encrypted with the database-level TDE protector).
+- If TDE with CMK is already enabled at the server level, setting CMK for a particular database overrides the server level CMK setting (database's DEK gets re-encrypted with the database-level TDE protector).
 - Any logical server level key changes or rotations don't affect database level CMK settings and the database continues to use its own CMK setting.
 - Database level CMK isn't supported through Transact-SQL (T-SQL).
 - The logical server user-assigned managed identity (UMI) can be used at the database level. However, it's recommended to use a designated UMI for the database level CMK.
diff --git a/azure-sql/managed-instance/managed-instance-link-feature-overview.md b/azure-sql/managed-instance/managed-instance-link-feature-overview.md
@@ -168,7 +168,7 @@ Feature limitations include:
 - If you're using Transparent Data Encryption (TDE) to encrypt SQL Server databases, the database encryption key from SQL Server needs to be exported and uploaded to Azure Key Vault, and you need to also configure the BYOK TDE option on SQL Managed Instance before creating the link.
 - You can't establish a link between SQL Server and SQL Managed Instance if the functionality that's used on the SQL Server instance isn't supported on the managed instance. For example: 
     - Databases with file tables and file streams can't be replicated, because SQL Managed Instance doesn't support file tables or file streams.
-    - Databases that use In-Memory OLTP (Hekaton) can be replicated only to the *Business Critical* service tier for SQL Managed Instance, because the *General Purpose* service tier doesn't support In-Memory OLTP. Databases with multiple Hekaton files can’t be replicated to the Business Critical service tier for SQL Managed Instance, as multiple Hekaton files aren't supported.
+    - Databases that use In-Memory OLTP (Hekaton) can be replicated only to the *Business Critical* service tier for SQL Managed Instance, because the *General Purpose* service tier doesn't support In-Memory OLTP. Databases with multiple Hekaton files can't be replicated to the Business Critical service tier for SQL Managed Instance, as multiple Hekaton files aren't supported.
 
 Trying to add an unsupported functionality to a replicated database in: 
    - SQL Server 2019 and 2022 fails with an error. 
diff --git a/docs/azure-data-studio/download-azure-data-studio.md b/docs/azure-data-studio/download-azure-data-studio.md
@@ -13,7 +13,7 @@ ms.custom: intro-overview
 
 Azure Data Studio is a lightweight, cross-platform data management and development tool with connectivity to popular cloud and on-premises databases. Azure Data Studio supports Windows, macOS, and Linux, with immediate capability to connect to Azure SQL and SQL Server.  Browse the extension library for more database support options including MySQL, PostgreSQL, and CosmosDB.
 
-Azure Data Studio’s familiar interface offers a modern editor experience with IntelliSense, code snippets, source control integration, and an integrated terminal.  Engineered with the data platform user in mind, its extensibility allows users to customize their experience by installing the extensions relevant to their workflow, including database migrations, charting, GitHub Copilot, and more!
+Azure Data Studio's familiar interface offers a modern editor experience with IntelliSense, code snippets, source control integration, and an integrated terminal.  Engineered with the data platform user in mind, its extensibility allows users to customize their experience by installing the extensions relevant to their workflow, including database migrations, charting, GitHub Copilot, and more!
 
 Use Azure Data Studio to query, design, and manage your databases and data warehouses wherever they are, on your local computer or in the cloud.
 
diff --git a/docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md b/docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md
@@ -60,7 +60,7 @@ Your server will open in the **SERVERS** sidebar after you've successfully conne
 ### [API for MongoDB (vCore)](#tab/mongodb-vcore)
 
 1. Open the new Azure Cosmos DB for MongoDB (vCore) account in the Azure Portal.
-2. Navigate to “Settings” > “Connection string”. and copy the shown “Connection string”.
+2. Navigate to "Settings" > "Connection string". and copy the shown "Connection string".
 
     :::image type="content" source="media/quickstart-azure-cosmos-db-mongodb/connection-string-in-portal.png" lightbox="media/quickstart-azure-cosmos-db-mongodb/connection-string-in-portal.png" alt-text="Screenshot of the connection string in the portal.":::
 
diff --git a/docs/azure-data-studio/release-notes-azure-data-studio.md b/docs/azure-data-studio/release-notes-azure-data-studio.md
@@ -283,7 +283,7 @@ For a full list of bug fixes addressed for the May 2023 release, visit the [May
 | Connection | Added ability to include optional name and grouping when creating a new connection using a connection string |
 | Connection | Updating username in MSSQL connections to use Preferred username for the display name |
 | Connection | Fixed issue with encoding for OSX keychain on macOS |
-| Connection | Added support for Azure AD Multi-Factor Authentication and ‘Sql Authentication Provider’ on Linux |
+| Connection | Added support for Azure AD Multi-Factor Authentication and 'Sql Authentication Provider' on Linux |
 | Dataverse | Addressed error generated when expanding the database node for a Dataverse database in Object Explorer |
 | IntelliCode extension | Fixed error that occurred when launching Azure Data Studio with Visual Studio Code IntelliCode extension installed |
 | PostgreSQL extension | Implemented support for exporting query results on Apple M1 from a notebook |
diff --git a/docs/azure-data-studio/what-is-azure-data-studio.md b/docs/azure-data-studio/what-is-azure-data-studio.md
@@ -14,7 +14,7 @@ ms.custom: intro-overview
 
 Azure Data Studio is a lightweight, cross-platform data management and development tool with connectivity to popular cloud and on-premises databases. Azure Data Studio supports Windows, macOS, and Linux, with immediate capability to connect to Azure SQL and SQL Server.  Browse the extension library for more database support options including MySQL, PostgreSQL, and CosmosDB.
 
-Azure Data Studio’s familiar interface offers a modern editor experience with IntelliSense, code snippets, source control integration, and an integrated terminal.  Engineered with the data platform user in mind, its extensibility allows users to customize their experience by installing the extensions relevant to their workflow, including database migrations, charting, GitHub Copilot, and more!
+Azure Data Studio's familiar interface offers a modern editor experience with IntelliSense, code snippets, source control integration, and an integrated terminal.  Engineered with the data platform user in mind, its extensibility allows users to customize their experience by installing the extensions relevant to their workflow, including database migrations, charting, GitHub Copilot, and more!
 
 The source code for Azure Data Studio and its data providers is available on GitHub under a source code EULA that provides rights to modify and use the software, but not to redistribute it or host it in a cloud service. For more information, see [Azure Data Studio FAQ](faq.yml).
 
diff --git a/docs/database-engine/availability-groups/windows/distributed-availability-groups.md b/docs/database-engine/availability-groups/windows/distributed-availability-groups.md
@@ -118,7 +118,7 @@ Post-migration, where the second availability group is now the new primary avail
 
 During a migration scenario, while it's possible to configure a distributed AG to migrate your databases to a SQL Server target that is a higher version than the source, there are a few limitations.
 
-When you configure the distributed AG with a SQL Server migration target that is a higher version than the source, autoseeding isn't supported so the seeding mode must be set to `MANUAL`. If you don’t disable AUTO-SEEDING, your migration will fail and you'll see error 946 "Cannot open database 'DistributionAG' version xxx. Upgrade the database to the latest version" in the error log. You must set seeding mode to MANUAL and manually perform a full and transaction log backup of the source database from the primary AG. Then manually restore it, along with the transaction log, to the secondary AG. To learn more, review the [manual seeding](configure-distributed-availability-groups.md?tabs=manual#create-distributed-availability-group-on-first-cluster) steps to configure your distributed AG, and scripts to back up and restore your database from the primary AG to the secondary AG.
+When you configure the distributed AG with a SQL Server migration target that is a higher version than the source, autoseeding isn't supported so the seeding mode must be set to `MANUAL`. If you don't disable AUTO-SEEDING, your migration will fail and you'll see error 946 "Cannot open database 'DistributionAG' version xxx. Upgrade the database to the latest version" in the error log. You must set seeding mode to MANUAL and manually perform a full and transaction log backup of the source database from the primary AG. Then manually restore it, along with the transaction log, to the secondary AG. To learn more, review the [manual seeding](configure-distributed-availability-groups.md?tabs=manual#create-distributed-availability-group-on-first-cluster) steps to configure your distributed AG, and scripts to back up and restore your database from the primary AG to the secondary AG.
 
 Assuming the secondary AG (AG2) is the migration target and is a higher version than the primary AG (AG1), consider the following limitations:
 
diff --git a/docs/relational-databases/security/encryption/always-encrypted-wizard.md b/docs/relational-databases/security/encryption/always-encrypted-wizard.md
@@ -68,7 +68,7 @@ If you want the wizard to encrypt or re-encrypt one or more columns using a new
 To decrypt a column that is currently encrypted, select **Plaintext** for the encryption type.
 
 > [!NOTE]
-> If you want to leverage in-place encryption and you’re using existing keys, make sure you select enclave-enabled keys – annotated with **(enclave-enabled)**. 
+> If you want to leverage in-place encryption and you're using existing keys, make sure you select enclave-enabled keys – annotated with **(enclave-enabled)**. 
 
 > [!NOTE]
 > The wizard does not support cryptographic operations on temporal and in-memory tables. You can create empty temporal or in-memory tables using Transact-SQL and insert data using your application.
@@ -86,7 +86,7 @@ For more information about creating and storing column master keys in Windows Ce
 > The wizard allows you to browse and create keys only in Windows Certificate Store and Azure Key Vault. It also auto-generates the names of both the new keys and the database metadata objects describing the keys. If you need more control for how your keys are provisioned (and more choices for a key store containing your column master key), you can use the **New Column Master Key** and **New Column Encryption Key** dialogs to create the keys first, and then run the wizard and pick the keys you have created. See [Provision Column Master Keys with the New Column Master Key Dialog](configure-always-encrypted-keys-using-ssms.md#provision-column-master-keys-with-the-new-column-master-key-dialog) or [Provision enclave-enabled keys](always-encrypted-enclaves-provision-keys.md) and [Provision Column Encryption Keys with the New Column Encryption Key Dialog](configure-always-encrypted-keys-using-ssms.md#provision-column-encryption-keys-with-the-new-column-encryption-key-dialog). 
 
 ## In-Place Encryption Settings Page
-If you have configured a secure enclave in your database and you’re using enclave-enabled keys, this page allows you to specify the enclave attestation parameters, required for in-place encryption. If you don’t want to use in-place encryption, unselect **Use in-place encryption for eligible columns** to proceed with client-side encryption. We recommend you to leave this checkbox enabled so that the wizard can use in-place encryption.
+If you have configured a secure enclave in your database and you're using enclave-enabled keys, this page allows you to specify the enclave attestation parameters, required for in-place encryption. If you don't want to use in-place encryption, unselect **Use in-place encryption for eligible columns** to proceed with client-side encryption. We recommend you to leave this checkbox enabled so that the wizard can use in-place encryption.
 
 For more information about enclave attestation, see [Configure attestation for Always Encrypted using Azure Attestation](/azure/azure-sql/database/always-encrypted-enclaves-configure-attestation) 
 
diff --git a/docs/relational-databases/security/sql-vulnerability-assessment.md b/docs/relational-databases/security/sql-vulnerability-assessment.md
diff --git a/docs/reporting-services/application-integration/release-notes-ssrs-application-integration.md b/docs/reporting-services/application-integration/release-notes-ssrs-application-integration.md
diff --git a/docs/sql-server/azure-arc/troubleshoot-assessment.md b/docs/sql-server/azure-arc/troubleshoot-assessment.md
diff --git a/docs/ssdt/ssis-vs2022-troubleshooting-guide.md b/docs/ssdt/ssis-vs2022-troubleshooting-guide.md
diff --git a/docs/ssms/release-notes-ssms.md b/docs/ssms/release-notes-ssms.md
