[SCOPED] Minor character fixes

rwestMSFT · rwestMSFT · commit d173a3eda8a0 · 2026-01-07T11:24:33.000-07:00
diff --git a/azure-sql/includes/tls-deprecation.md b/azure-sql/includes/tls-deprecation.md
@@ -32,19 +32,19 @@ After August 31, 2025, TLS 1.0 and 1.1 will no longer be supported, and connecti
 
 - To verify the minimum TLS version configured for your Azure Database for MySQL Server, check the value of the `tls_version` server parameter using the MySQL command-line interface to understand what protocols are configured.
 
-#### Why was my service flagged if I’ve already configured TLS 1.2?
+#### Why was my service flagged if I've already configured TLS 1.2?
 
 Services might be incorrectly flagged due to:
 
 - Intermittent fallback to older TLS versions by legacy clients.
-- Misconfigured client libraries or connection strings that don’t enforce TLS 1.2.
+- Misconfigured client libraries or connection strings that don't enforce TLS 1.2.
 - Telemetry lag or false positives in detection logic.
 
 #### What should I do if I received a retirement notice in error?
 
 If your server or database is already configured with minimum TLS 1.2, or configured with no minimum TLS (the default setting in SQL Database and SQL Managed Instance `minimalTLSVersion` that maps to `0`) and connecting with 1.2, no action is required.
 
-#### What happens if my application or client library doesn’t support TLS 1.2?
+#### What happens if my application or client library doesn't support TLS 1.2?
 
 Connections will fail once TLS 1.0/1.1 are disabled. You must upgrade your client libraries, drivers, or frameworks to versions that support TLS 1.2.
 
diff --git a/azure-sql/managed-instance/identify-query-performance-issues.md b/azure-sql/managed-instance/identify-query-performance-issues.md
@@ -63,7 +63,7 @@ Several workarounds can mitigate PSP problems. Each workaround has associated tr
 
 - A new feature introduced with SQL Server 2022 (16.x) is [Parameter Sensitive Plan optimization](/sql/relational-databases/performance/parameter-sensitivity-plan-optimization), which attempts to mitigate most suboptimal query plans caused by parameter sensitivity. This is enabled with database compatibility level 160.
 - Use the [RECOMPILE](/sql/t-sql/queries/hints-transact-sql-query) query hint at each query execution. This workaround trades compilation time and increased CPU for better plan quality. The `RECOMPILE` option is often not possible for workloads that require a high throughput. 
-- Use the [OPTION (OPTIMIZE FOR…)](/sql/t-sql/queries/hints-transact-sql-query) query hint to override the actual parameter value with a typical parameter value that produces a plan that's good enough for most parameter value possibilities. This option requires a good understanding of optimal parameter values and associated plan characteristics.
+- Use the [OPTION (OPTIMIZE FOR...)](/sql/t-sql/queries/hints-transact-sql-query) query hint to override the actual parameter value with a typical parameter value that produces a plan that's good enough for most parameter value possibilities. This option requires a good understanding of optimal parameter values and associated plan characteristics.
 - Use the [OPTION (OPTIMIZE FOR UNKNOWN)](/sql/t-sql/queries/hints-transact-sql-query) query hint to override the actual parameter value and instead use the density vector average. You can also do this by capturing the incoming parameter values in local variables and then using the local variables within the predicates instead of using the parameters themselves. For this fix, the average density must be *good enough*.
 - Disable parameter sniffing entirely by using the [DISABLE_PARAMETER_SNIFFING](/sql/t-sql/queries/hints-transact-sql-query) query hint.
 - Use the [KEEPFIXEDPLAN](/sql/t-sql/queries/hints-transact-sql-query) query hint to prevent recompilations in cache. This workaround assumes that the good-enough common plan is the one in cache already. You can also disable automatic statistics updates to reduce the chances that the good plan will be evicted and a new bad plan will be compiled.
diff --git a/azure-sql/managed-instance/managed-instance-link-best-practices.md b/azure-sql/managed-instance/managed-instance-link-best-practices.md
@@ -121,7 +121,7 @@ EXEC sp_validate_certificate_ca_chain <certificate_id>
 GO 
 ```
 
-A response of `Commands completed successfully. Completion time: …` indicates the MI endpoint certificate has been successfully validated. 
+A response of `Commands completed successfully. Completion time: ...` indicates the MI endpoint certificate has been successfully validated. 
 
 > [!IMPORTANT]
 > The stored procedure `sp_validate_certificate_ca_chain` relies on host OS services to perform certificate validation, which might involve an online certificate revocation check. If the host OS is not configured to access the internet, the execution fails even if the certificate chain is valid. 
diff --git a/docs/connect/ado-net/sql/bulk-copy-example-setup.md b/docs/connect/ado-net/sql/bulk-copy-example-setup.md
@@ -22,7 +22,7 @@ The **BulkCopyDemoMatchingColumns** and **BulkCopyDemoDifferentColumns** tables
 A few of the code samples demonstrate how to use one <xref:Microsoft.Data.SqlClient.SqlBulkCopy> class to write to multiple tables. For these samples, the **BulkCopyDemoOrderHeader** and **BulkCopyDemoOrderDetail** tables are used as the destination tables. These tables are based on the **Sales.SalesOrderHeader** and **Sales.SalesOrderDetail** tables in **AdventureWorks**.  
   
 > [!NOTE]
->  The **SqlBulkCopy** code samples are provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data.  
+>  The **SqlBulkCopy** code samples are provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 ## Table setup  
 To create the tables necessary for the code samples to run correctly, you must run the following Transact-SQL statements in a SQL Server database.  
diff --git a/docs/connect/ado-net/sql/multiple-bulk-copy-operations.md b/docs/connect/ado-net/sql/multiple-bulk-copy-operations.md
@@ -25,7 +25,7 @@ If you perform several bulk copy operations using the same <xref:Microsoft.Data.
 ## Example
 
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopy_._ColumnMappingOrdersDetails#1](~/../sqlclient/doc/samples/SqlBulkCopy_ColumnMappingOrdersDetails.cs#1)]
   
diff --git a/docs/connect/ado-net/sql/single-bulk-copy-operations.md b/docs/connect/ado-net/sql/single-bulk-copy-operations.md
@@ -46,7 +46,7 @@ The general steps for performing a bulk copy operation are as follows:
 The following console application demonstrates how to load data using the <xref:Microsoft.Data.SqlClient.SqlBulkCopy> class. In this example, a <xref:Microsoft.Data.SqlClient.SqlDataReader> is used to copy data from the **Production.Product** table in the SQL Server **AdventureWorks** database to a similar table in the same database.  
   
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopy_WriteToServer#1](~/../sqlclient/doc/samples/SqlBulkCopy_WriteToServer.cs#1)]
   
diff --git a/docs/connect/php/use-table-valued-parameters.md b/docs/connect/php/use-table-valued-parameters.md
@@ -130,7 +130,7 @@ sqlsrv_next_result($stmt);
 
 ### Use the PDO_SQLSRV driver
 
-This is an equivalent example when using the PDO_SQLSRV driver. You can use prepare/execute with [bindParam](../../connect/php/pdostatement-bindparam.md) and specify the TVP input as a `PDO::PARAM_LOB`. If not, you'll get this error: `Operand type clash: nvarchar is incompatible with …`.
+This is an equivalent example when using the PDO_SQLSRV driver. You can use prepare/execute with [bindParam](../../connect/php/pdostatement-bindparam.md) and specify the TVP input as a `PDO::PARAM_LOB`. If not, you'll get this error: `Operand type clash: nvarchar is incompatible with ...`.
 
 ```php
 try {
diff --git a/docs/machine-learning/python/reference/azureml-model-management-sdk/mlserver.md b/docs/machine-learning/python/reference/azureml-model-management-sdk/mlserver.md
@@ -41,7 +41,7 @@ ML Server supports two forms of authentication contexts:
 
 * LDAP: tuple *(username, password)* 
 
-* Azure Active Directory (AAD): dict *{…}* 
+* Azure Active Directory (AAD): dict *{...}* 
 
 * access-token: str *=4534535* 
 
diff --git a/docs/master-data-services/master-data-services-host-database-on-managed-instance.md b/docs/master-data-services/master-data-services-host-database-on-managed-instance.md
@@ -215,7 +215,7 @@ To fix this issue, you need upgrade the database version:
 
    ![Screenshot of the Connect to a Master Data Service Database dialog box.](../master-data-services/media/mds-sqlserver2019-config-mi-connectdbname.png "mds-SQLServer2019-Config-MI_ConnectDBName")
 
-1. Select **Upgrade Database…** .
+1. Select **Upgrade Database...** .
 
    ![Screenshot of the Upgrade Database option.](../master-data-services/media/mds-sqlserver2019-config-mi-selectupgradedb.png "mds-SQLServer2019-Config-MI_SelectUpgradeDB")
 
diff --git a/docs/relational-databases/polybase/polybase-errors-and-possible-solutions.md b/docs/relational-databases/polybase/polybase-errors-and-possible-solutions.md
@@ -102,9 +102,9 @@ If there are multiple files per table, put each set of files into different dire
 
 ```syntaxsql
 Create External Table foo
-(col1 int)WITH (LOCATION='/bar/foobar.txt',DATA_SOURCE…); OR
+(col1 int)WITH (LOCATION='/bar/foobar.txt',DATA_SOURCE...); OR
 Create External Table foo
-(col1 int) WITH (LOCATION = '/bar/', DATA_SOURCE…);
+(col1 int) WITH (LOCATION = '/bar/', DATA_SOURCE...);
 ```
 
 > [!NOTE] 
diff --git a/docs/relational-databases/replication/add-publisher.md b/docs/relational-databases/replication/add-publisher.md
@@ -23,15 +23,15 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016"
  **Add**  
  Click to select a type of Publisher to add, which launches the **Connect to Server** dialog box. The options are:  
   
--   **Add SQL Server Publisher…**  
+-   **Add SQL Server Publisher...**  
   
      Connect to the Publisher using the **Connect to Server** dialog box.  
   
--   **Add Oracle Publisher…**  
+-   **Add Oracle Publisher...**  
   
      Connect to the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributor associated with the Oracle Publisher using the **Connect to Server** dialog box.  
   
--   **Specify a Distributor and Add Its Publishers…**  
+-   **Specify a Distributor and Add Its Publishers...**  
   
      Connect to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributor associated with one or more Publishers using the **Connect to Server** dialog box.  
   
diff --git a/docs/relational-databases/replication/agents/view-and-modify-replication-agent-command-prompt-parameters.md b/docs/relational-databases/replication/agents/view-and-modify-replication-agent-command-prompt-parameters.md
@@ -23,7 +23,7 @@ helpviewer_keywords:
   
  If you access agent jobs from the **Jobs** folder, use the following table to determine the agent job name and the parameters available for each agent.  
   
-|Agent|Job name|For a list of parameters, see…|  
+|Agent|Job name|For a list of parameters, see...|  
 |-----------|--------------|------------------------------------|  
 |Snapshot Agent|**\<Publisher>-\<PublicationDatabase>-\<Publication>-\<integer>**|[Replication Snapshot Agent](../../../relational-databases/replication/agents/replication-snapshot-agent.md)|  
 |Snapshot Agent for a merge publication partition|**Dyn_\<Publisher>-\<PublicationDatabase>-\<Publication>-\<GUID>**|[Replication Snapshot Agent](../../../relational-databases/replication/agents/replication-snapshot-agent.md)|  
diff --git a/docs/relational-databases/replication/create-a-subscription-for-a-non-sql-server-subscriber.md b/docs/relational-databases/replication/create-a-subscription-for-a-non-sql-server-subscriber.md
@@ -90,7 +90,7 @@ helpviewer_keywords:
   
     -   For IBM Db2, the database is specified in the **Initial Catalog** property of the DB2 connection string, which can be entered in the **Additional connection options** field described later in this process.  
   
-8.  On the **Distribution Agent Security** page, click the properties button (**…**) next to the Subscriber to access the **Distribution Agent Security** dialog box.  
+8.  On the **Distribution Agent Security** page, click the properties button (**...**) next to the Subscriber to access the **Distribution Agent Security** dialog box.  
   
 9. In the **Distribution Agent Security** dialog box:  
   
diff --git a/docs/relational-databases/replication/distributor-properties.md b/docs/relational-databases/replication/distributor-properties.md
@@ -71,7 +71,7 @@ The **Publishers** page of the **Distributor Properties** dialog box allows you
  The length of time history metadata is stored for all types of replication.  
   
  **Queue Reader Agent security**  
- The Queue Reader Agent is used by transactional replication with queued updating subscriptions. A Queue Reader Agent is created automatically if you select **Transactional publication with updating subscriptions** on the **Publication Type** page of the New Publication Wizard. Click **Security Settings…** to change the account under which the agent runs and makes connections to the Distributor.  
+ The Queue Reader Agent is used by transactional replication with queued updating subscriptions. A Queue Reader Agent is created automatically if you select **Transactional publication with updating subscriptions** on the **Publication Type** page of the New Publication Wizard. Click **Security Settings...** to change the account under which the agent runs and makes connections to the Distributor.  
   
  A Queue Reader Agent can also be created by selecting **Create Queue Reader Agent** on this page (this option is disabled if the agent has already been created).  
   
diff --git a/docs/relational-databases/replication/microsoft-replication-conflict-viewer-merge-replication.md b/docs/relational-databases/replication/microsoft-replication-conflict-viewer-merge-replication.md
@@ -64,7 +64,7 @@ f1_keywords:
  **Show first five columns and other columns with conflicting data**  
  Select to display the first five columns and any columns that have conflicts. This is helpful when the table has a large number of columns, but you want to see only the columns most relevant to resolving the conflict. The first five columns are always included in this view, as fields that identify a row, such as the primary key or name fields, are often among the first columns of the table.  
   
- **Display Column Information** (**…**)  
+ **Display Column Information** (**...**)  
  Click to view column information: **Table Name**, **Column Name**, **Data Type**, and **Column Value**. **Column Value** is editable unless the value is displayed as read-only.  
   
  **Submit Winner**  
diff --git a/docs/relational-databases/replication/microsoft-replication-conflict-viewer-transactional-replication.md b/docs/relational-databases/replication/microsoft-replication-conflict-viewer-transactional-replication.md
@@ -55,7 +55,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016"
  **Show first five columns and other columns with conflicting data**  
  Select to display the first five columns and any columns that have conflicts. This is helpful when the table has a large number of columns, but you want to see only the columns most relevant to resolving the conflict. The first five columns are always included in this view, as fields that identify a row, such as the primary key or name fields, are often among the first columns of the table.  
   
- **Display Column Information** (**…**)  
+ **Display Column Information** (**...**)  
  Click to view column information: **Table Name**, **Column Name**, **Data Type**, and **Column Value**.  
   
  **Log the details of the conflict**  
diff --git a/docs/relational-databases/replication/set-the-history-retention-period-sql-server-management-studio.md b/docs/relational-databases/replication/set-the-history-retention-period-sql-server-management-studio.md
@@ -20,7 +20,7 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016"
   
 ### To specify the history retention period  
   
-1.  On the **General** page of the **Distributor Properties - \<Distributor>** dialog box, click the properties button (**…**) for the distribution database.  
+1.  On the **General** page of the **Distributor Properties - \<Distributor>** dialog box, click the properties button (**...**) for the distribution database.  
   
 2.  Enter a value in the **Store replication performance history at least** box.  
   
diff --git a/docs/relational-databases/replication/tutorial-replicating-data-with-mobile-clients.md b/docs/relational-databases/replication/tutorial-replicating-data-with-mobile-clients.md
@@ -199,7 +199,7 @@ In this section, you add a subscription to the merge publication that you create
 
    ![Selections for adding a database to the subscriber](media/tutorial-replicating-data-with-mobile-clients/addsubdb.png)
   
-8. On the **Merge Agent Security** page, select the ellipsis (**…**) button. Enter <*Subscriber_Machine_Name*>**\repl_merge** in the **Process account** box, and supply the password for this account. Select **OK**, select **Next**, and then select **Next** again.  
+8. On the **Merge Agent Security** page, select the ellipsis (**...**) button. Enter <*Subscriber_Machine_Name*>**\repl_merge** in the **Process account** box, and supply the password for this account. Select **OK**, select **Next**, and then select **Next** again.  
 
    ![Selections for Merge Agent security](media/tutorial-replicating-data-with-mobile-clients/mergeagentsecurity.png)
 
diff --git a/docs/relational-databases/replication/view-data-conflicts-for-transactional-publications-sql-server-management-studio.md b/docs/relational-databases/replication/view-data-conflicts-for-transactional-publications-sql-server-management-studio.md
@@ -50,7 +50,7 @@ helpviewer_keywords:
   
     -   Select one or more rows in the upper grid, and then click **Remove**, which removes the row from the conflicts metadata table.  
   
-    -   Click the properties button (**…**) to view more information on a column involved in a conflict.  
+    -   Click the properties button (**...**) to view more information on a column involved in a conflict.  
   
     -   Select **Log the details of this conflict** to log conflict data to a file. To specify a location for the file, point to the **View** menu, and then click **Options**. Enter a value, or click the browse button (**...**), and then navigate to the appropriate file. Click **OK** to close the **Options** dialog box.  
   
diff --git a/docs/relational-databases/security/networking/tds-8.md b/docs/relational-databases/security/networking/tds-8.md
@@ -50,7 +50,7 @@ TCP handshake :arrow_right: TLS handshake :arrow_right: TDS prelogin (encrypted)
 
 You can enable both TLS 1.2 and TLS 1.3 versions at the OS level, which allows client connections to SQL Server to use multiple TDS protocol versions (TDS 7.x and 8.0). Depending on the OS version, TLS 1.2 and TLS 1.3 might be enabled by default. 
 
-Only TDS 7.x supports non-encrypted (optional) communication, TDS 8.0 doesn’t support this. TDS 7.x supports encryption using TLS up to version 1.2. TDS 8.0 requires encryption – everything is always encrypted with TDS 8.0 (Encrypt=Strict). TDS 8.0 has no minimum TLS version requirement and supports TLS 1.3.
+Only TDS 7.x supports non-encrypted (optional) communication, TDS 8.0 doesn't support this. TDS 7.x supports encryption using TLS up to version 1.2. TDS 8.0 requires encryption – everything is always encrypted with TDS 8.0 (Encrypt=Strict). TDS 8.0 has no minimum TLS version requirement and supports TLS 1.3.
 TLS 1.3 support is dependent on the operating system version. The following table summarizes various scenarios with the encryption options and the corresponding TLS and TDS versions.
 
 
diff --git a/docs/relational-databases/system-catalog-views/sys-query-store-plan-feedback.md b/docs/relational-databases/system-catalog-views/sys-query-store-plan-feedback.md
@@ -35,7 +35,7 @@ Contains information about Query Store tuning via query feedback features, inclu
 | `plan_id` | **bigint** | Foreign key. Joins to [sys.query_store_plan (Transact-SQL)](../../relational-databases/system-catalog-views/sys-query-store-plan-transact-sql.md). |
 | `feature_id` | **tinyint** | ID of the feature in use. |
 | `feature_desc` | **nvarchar(60)** | 1 = CE Feedback<br />2 = Memory Grant Feedback<br />3 = DOP Feedback<br />4 = LAQ Feedback |
-| `feedback_data` | **nvarchar(max)** | For CE feedback, displays query hints in use.<br /><br />For memory grant feedback, displays JSON string containing operator-level grant values.<br />Format: `{"node_id": value}, {"node_id": value},….`<br />Example: `{"NodeId":"0","AdditionalMemoryKB":"1152"},{"NodeId":"18","AdditionalMemoryKB":"1856"}` |
+| `feedback_data` | **nvarchar(max)** | For CE feedback, displays query hints in use.<br /><br />For memory grant feedback, displays JSON string containing operator-level grant values.<br />Format: `{"node_id": value}, {"node_id": value},...`<br />Example: `{"NodeId":"0","AdditionalMemoryKB":"1152"},{"NodeId":"18","AdditionalMemoryKB":"1856"}` |
 | `state` | **int** | ID of the current feedback state. |
 | `state_desc` | **nvarchar(60)** | 0. NO_FEEDBACK<br />1. NO_RECOMMENDATION<br />2. PENDING_VALIDATION<br />3. IN_VALIDATION<br />4. VERIFICATION_REGRESSED<br />5. VERIFICATION_PASSED<br />6. ROLLEDBACK_BY_APRC<br />7. FEEDBACK_VALID<br />8. FEEDBACK_INVALID |
 | `create_time` | **datetimeoffset(7)** | When this row was created. |
diff --git a/docs/sql-server/ai/artificial-intelligence-intelligent-applications-faq.md b/docs/sql-server/ai/artificial-intelligence-intelligent-applications-faq.md
diff --git a/docs/sql-server/azure-arc/manage-pay-as-you-go-transition.md b/docs/sql-server/azure-arc/manage-pay-as-you-go-transition.md
diff --git a/docs/sql-server/azure-arc/move-resources.md b/docs/sql-server/azure-arc/move-resources.md
diff --git a/docs/t-sql/functions/odbc-scalar-functions-transact-sql.md b/docs/t-sql/functions/odbc-scalar-functions-transact-sql.md
diff --git a/docs/t-sql/statements/insert-transact-sql.md b/docs/t-sql/statements/insert-transact-sql.md
diff --git a/docs/tools/sqlpackage/sqlpackage-download.md b/docs/tools/sqlpackage/sqlpackage-download.md
diff --git a/docs/tools/synapse-pathway/synapse-pathway-behind-the-scenes.md b/docs/tools/synapse-pathway/synapse-pathway-behind-the-scenes.md
