Merge pull request #34727 from rwestMSFT/rw-0717-fix-smart

[SCOPED] Fix smart characters

Author: JamesJBarnett

azure-sql/managed-instance/managed-instance-link-feature-overview.md

@@ -170,8 +170,7 @@ For example, as a pay-as-you-go customer, if you have 16 vCores assigned to the
 
 In another example, if you have 16 Azure Hybrid Benefit licenses and your secondary SQL managed instance uses 8 vCores, after you designate the secondary instance for hybrid failover, 8 vCores are returned to your license pool for you to use with other Azure SQL deployments.
 
-For precise terms and conditions of the Hybrid failover rights benefit, see the SQL Server licensing terms online in the [“SQL Server – Fail-over Rights”](https://www.microsoft.com/licensing/terms/productoffering/SQLServer/EAEAS) section.
-
+For precise terms and conditions of the Hybrid failover rights benefit, see the SQL Server licensing terms online in the [SQL Server – Fail-over Rights](https://www.microsoft.com/licensing/terms/productoffering/SQLServer/EAEAS) section.
 
 ## Limitations
 

azure-sql/managed-instance/timezones-overview.md

@@ -32,7 +32,7 @@ A set of supported time zones is inherited from the underlying operating system
 A list with names of the supported time zones is exposed through the [sys.time_zone_info](/sql/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql) system view.
 
 > [!NOTE]
-> On October 14, 2024, the Paraguayan government announced a permanent change to the country’s time zone policy. Paraguay will remain on Daylight Saving Time (DST) year-round, effectively adopting UTC-3 as its standard time. As a result, clocks will not advance by 60 minutes at 12:00 a.m. on March 23, 2025, as previously scheduled. This change affects the Paraguay Standard time zone. Microsoft has released related [Windows updates in February and March 2025](https://techcommunity.microsoft.com/blog/dstblog/paraguay-2025-time-zone-update-now-available/4386720). Azure SQL Managed Instance currently does not reflect this update. Instances using affected time zone will not reflect the changes until Azure SQL Managed Instance service absorbs the update on the OS level. If you need to alter affected time zones for you managed instances, please be aware of the [limitations](#limitations) and follow the guidance from the documentation. 
+> On October 14, 2024, the Paraguayan government announced a permanent change to the country's time zone policy. Paraguay will remain on Daylight Saving Time (DST) year-round, effectively adopting UTC-3 as its standard time. As a result, clocks will not advance by 60 minutes at 12:00 a.m. on March 23, 2025, as previously scheduled. This change affects the Paraguay Standard time zone. Microsoft has released related [Windows updates in February and March 2025](https://techcommunity.microsoft.com/blog/dstblog/paraguay-2025-time-zone-update-now-available/4386720). Azure SQL Managed Instance currently does not reflect this update. Instances using affected time zone will not reflect the changes until Azure SQL Managed Instance service absorbs the update on the OS level. If you need to alter affected time zones for you managed instances, please be aware of the [limitations](#limitations) and follow the guidance from the documentation. 
 
 ## Set a time zone
 

azure-sql/managed-instance/update-policy.md

@@ -118,7 +118,7 @@ Set `databaseFormat` = `AlwaysUpToDate` when you update an existing SQL managed
 Although the **SQL Server 2022** update policy is enabled by default, you can choose the **Always-up-to-date** policy when you create your instance by using the Azure portal, PowerShell, Azure CLI and REST API. 
 
 > [!IMPORTANT]
-> Make sure to add update policy configuration to your deployment templates, so that you don’t rely on system defaults that may change over time. 
+> Make sure to add update policy configuration to your deployment templates, so that you don't rely on system defaults that may change over time. 
 
 ### [Azure portal](#tab/azure-portal)
 

azure-sql/virtual-machines/windows/automated-backup-sql-2014.md

@@ -268,7 +268,7 @@ As a general practice, it's recommended to check on the health of your backups f
    BACKUP CERTIFICATE [AutoBackup_Certificate] TO FILE = <file_path> WITH PRIVATE KEY (FILE = <file_path>, ENCRYPTION BY PASSWORD = <password>)
    ```
 
-1. Confirm that your backup files are uploaded with at least 1 full backup. Because mistakes happen, you should be sure you always have at least one full backup before deleting your VM, or in case your VM gets corrupted, so you know you can still access your data. You should make sure the backup in storage is safe and recoverable before deleting your VM’s data disks.
+1. Confirm that your backup files are uploaded with at least 1 full backup. Because mistakes happen, you should be sure you always have at least one full backup before deleting your VM, or in case your VM gets corrupted, so you know you can still access your data. You should make sure the backup in storage is safe and recoverable before deleting your VM's data disks.
 
 
 ## Monitoring

azure-sql/virtual-machines/windows/automated-backup.md

@@ -384,7 +384,7 @@ As a general practice, it is recommended to check on the health of your backups
    BACKUP CERTIFICATE [AutoBackup_Certificate] TO FILE = <file_path> WITH PRIVATE KEY (FILE = <file_path>, ENCRYPTION BY PASSWORD = <password>)
    ```
 
-1. Confirm that your backup files are uploaded with at least 1 full backup. Because mistakes happen, you should be sure you always have at least one full backup before deleting your VM, or in case your VM gets corrupted, so you know you can still access your data. You should make sure the backup in storage is safe and recoverable before deleting your VM’s data disks.
+1. Confirm that your backup files are uploaded with at least 1 full backup. Because mistakes happen, you should be sure you always have at least one full backup before deleting your VM, or in case your VM gets corrupted, so you know you can still access your data. You should make sure the backup in storage is safe and recoverable before deleting your VM's data disks.
 
 
 ## Monitoring

azure-sql/virtual-machines/windows/tempdb-ephemeral-storage.md

@@ -145,7 +145,7 @@ Restart the VM to test the script. After the VM restarts, check that the `tempdb
 
 ## Configure buffer pool extension
 
-You can further enhance SQL Server performance by configuring the [buffer pool extension](/sql/database-engine/configure-windows/buffer-pool-extension) to use the local SSD drive on Azure VMs. This feature extends the in-memory buffer pool by using a file on disk to boost I/O throughput for memory-intensive workloads that exceed available RAM. Since the local SSD (ephemeral storage) offers low latency and high performance, it’s an ideal location for this extension.
+You can further enhance SQL Server performance by configuring the [buffer pool extension](/sql/database-engine/configure-windows/buffer-pool-extension) to use the local SSD drive on Azure VMs. This feature extends the in-memory buffer pool by using a file on disk to boost I/O throughput for memory-intensive workloads that exceed available RAM. Since the local SSD (ephemeral storage) offers low latency and high performance, it's an ideal location for this extension.
  
 When configuring the buffer pool extension, specify the size of the file in kilobytes (KB), megabytes (MB), or gigabytes (GB). The recommended size is typically 4 to 8 times the [max_server_memory] setting configured for SQL Server, though for Standard edition, the maximum is capped at 4 times this value (Enterprise edition allows up to 32 times). For example, if **max_server_memory** is set to 16 GB, aim for a buffer pool extension size of 64-128 GB, adjusted to your SQL Server edition and workload needs. 
  

docs/integration-services/fabric-integration/integrate-fabric-data-warehouse.md

@@ -17,7 +17,7 @@ This document focuses on the best practices to use existing SSIS packages to wor
 
 ## Introduction
 
-****Microsoft Fabric**** is a comprehensive analytics platform that covers every aspect of an organization’s data estate. One of its key experiences is Fabric Data Warehouse, which serves as a simplified SaaS solution for a fully transactional warehouse. It stores data in OneLake using an open format called Delta Parquet, ensuring that data can be accessed by other experiences within Fabric and other client applications that connect using SQL drivers.
+****Microsoft Fabric**** is a comprehensive analytics platform that covers every aspect of an organization's data estate. One of its key experiences is Fabric Data Warehouse, which serves as a simplified SaaS solution for a fully transactional warehouse. It stores data in OneLake using an open format called Delta Parquet, ensuring that data can be accessed by other experiences within Fabric and other client applications that connect using SQL drivers.
 
 ****Microsoft Fabric****, as an analytics platform, exclusively supports authentication through ****Microsoft Entra ID**** for users and Service Principals (SPNs). This deliberate choice ensures centralized and identity-based security, aligning with modern security practices. So, SQL authentication and other authentication methods aren't supported in Fabric Data Warehouse within the Fabric ecosystem.
 
@@ -27,7 +27,7 @@ Microsoft SQL Server Integration Services (SSIS) is a component of the Microsoft
 Two key modifications are required in SSIS package to work seamlessly with Fabric Data Warehouse, outlined as follows.
 
 ### Authentication
-If you're using SQL Authentication or Windows Authentication, reconfigure it to utilize Microsoft Entra ID User or Service Principal Name (SPN). Keep in mind that if you’re using a User account, multifactor authentication (MFA) must be disabled, as SSIS doesn't support pop-up prompts.  It also needs respective drivers as mentioned below:
+If you're using SQL Authentication or Windows Authentication, reconfigure it to utilize Microsoft Entra ID User or Service Principal Name (SPN). Keep in mind that if you're using a User account, multifactor authentication (MFA) must be disabled, as SSIS doesn't support pop-up prompts.  It also needs respective drivers as mentioned below:
 
 ****To use [OLEDB connection manager](../connection-manager/ole-db-connection-manager.md)****:
 - Install [OLE DB Driver for SQL Server](../../connect/oledb/features/using-azure-active-directory.md) version that supports Microsoft Entra ID
@@ -42,7 +42,7 @@ If you're using SQL Authentication or Windows Authentication, reconfigure it to
 :::image type="content" source="media/ado-net-connection.png" alt-text="Screenshot of ado connection manager part 1." lightbox="media/ado-net-connection.png":::
 
 ### File ingestion 
-The ****Fabric Data Warehouse**** recommends utilizing the native T-SQL command ‘COPY INTO’ for efficient data insertion into the warehouse. So, any DFT operations that currently rely on ****Fast Insert Mode**** or ****BCP IN**** scripts should be replaced with the ****COPY INTO**** statement by utilizing [Execute SQL Task](../control-flow/execute-sql-task.md). 
+The ****Fabric Data Warehouse**** recommends utilizing the native T-SQL command 'COPY INTO' for efficient data insertion into the warehouse. So, any DFT operations that currently rely on ****Fast Insert Mode**** or ****BCP IN**** scripts should be replaced with the ****COPY INTO**** statement by utilizing [Execute SQL Task](../control-flow/execute-sql-task.md). 
 
 ### SSIS writing data into Data Warehouse in Fabric
 

docs/relational-databases/regular-expressions/overview.md

@@ -75,23 +75,22 @@ The following table lists currently supported Perl character classes.
 
 The following table lists currently supported ASCII character classes.
 
-|ASCII character classes  |Description  |
-|---------|---------|
-| `[[:alnum:]]`           | alphanumeric ( `[0-9A-Za-z]`) |
-| `[[:alpha:]]`           | alphabetic ( `[A-Za-z]`) |
-| `[[:ascii:]]`           | ASCII ( `[\x00-\x7F]`) |
-| `[[:blank:]]`           | blank ( `[\t ]`) |
-| `[[:cntrl:]]`           | control ( `[\x00-\x1F\x7F]`) |
-| `[[:digit:]]`           | digits ( `[0-9]`) |
-| `[[:graph:]]`           |	graphical ( `[!-~]` or ``[A-Za-z0-9!“#$%&’()*+,\-./:;<=>?@[\\\]^_`{|}~]``) |
-| `[[:lower:]]`           | lower case ( `[a-z]`) |
-| `[[:print:]]`           | printable ( `[ -~]` or `[ [:graph:]]`) |
-| `[[:punct:]]`           | punctuation ( `[!-/:-@[-\``{-~]`) |
-| `[[:space:]]`           | whitespace ( `[\t\n\v\f\r ]`) |
-| `[[:upper:]]`           | upper case ( `[A-Z]`) |
-| `[[:word:]]`            | word characters ( `[0-9A-Za-z_]`) |
-| `[[:xdigit:]]`          | hex digit ( `[0-9A-Fa-f]`) |
-
+| ASCII character classes | Description |
+| --- | --- |
+| `[[:alnum:]]` | alphanumeric ( `[0-9A-Za-z]`) |
+| `[[:alpha:]]` | alphabetic ( `[A-Za-z]`) |
+| `[[:ascii:]]` | ASCII ( `[\x00-\x7F]`) |
+| `[[:blank:]]` | blank ( `[\t ]`) |
+| `[[:cntrl:]]` | control ( `[\x00-\x1F\x7F]`) |
+| `[[:digit:]]` | digits ( `[0-9]`) |
+| `[[:graph:]]` | graphical ( `[!-~]` or ``[A-Za-z0-9!"#$%&'()*+,\-./:;<=>?@[\\\]^_`{|}~]``) |
+| `[[:lower:]]` | lower case ( `[a-z]`) |
+| `[[:print:]]` | printable ( `[ -~]` or `[ [:graph:]]`) |
+| `[[:punct:]]` | punctuation ( `[!-/:-@[-\``{-~]`) |
+| `[[:space:]]` | whitespace ( `[\t\n\v\f\r ]`) |
+| `[[:upper:]]` | upper case ( `[A-Z]`) |
+| `[[:word:]]` | word characters ( `[0-9A-Za-z_]`) |
+| `[[:xdigit:]]` | hex digit ( `[0-9A-Fa-f]`) |
 
 ### Literal characters
 

docs/reporting-services/branding-the-web-portal.md

@@ -16,7 +16,7 @@ ms.custom:
 
 [!INCLUDE[ssrs-appliesto](../includes/ssrs-appliesto.md)] [!INCLUDE[ssrs-appliesto-2016-and-later](../includes/ssrs-appliesto-2016-and-later.md)] [!INCLUDE[ssrs-appliesto-pbirs](../includes/ssrs-appliesto-pbirs.md)]
 
-Learn how to customize your SQL Server Reporting Services (SSRS) or Power BI Report Server web portal to match your business’s branding. By using an uploaded brand package, you can change colors, logos, and other styling elements on your web portal. A brand package consists of three items that you package as a zip file. The following sections describe the items in the brand package and provide examples of the contents. 
+Learn how to customize your SQL Server Reporting Services (SSRS) or Power BI Report Server web portal to match your business's branding. By using an uploaded brand package, you can change colors, logos, and other styling elements on your web portal. A brand package consists of three items that you package as a zip file. The following sections describe the items in the brand package and provide examples of the contents. 
 
 > [!VIDEO https://www.youtube-nocookie.com/embed/m08kLuofwFA]
 
@@ -94,7 +94,7 @@ The following example includes a logo file:
 
 The `colors.json` file defines the color scheme for your brand package. When you upload the brand package, the server extracts the name/value pairs from this file and merges them with the primary LESS stylesheet, `brand.less`. It processes the stylesheet, and serves the resulting CSS file to the client. All colors in the stylesheet follow the six-character hexadecimal representation of a color.
 
-Here’s an example of the `colors.json` file:
+Here's an example of the `colors.json` file:
 
 ```json
 {

docs/reporting-services/create-a-data-driven-subscription-ssrs-tutorial.md

@@ -41,7 +41,7 @@ Your computer must have the following installed to use this tutorial:
 
 - A [!INCLUDE[ssRSnoversion_md](../includes/ssrsnoversion-md.md)] role assignment that includes the **Manage all subscriptions** task on the sample report. This task defines a data-driven subscription. If you're an administrator on the computer, the default role assignment for local administrators provides the permissions necessary for creating data-driven subscriptions. For more information, see [Grant permissions on a native mode report server](../reporting-services/security/granting-permissions-on-a-native-mode-report-server.md).  
 
-- Write permissions to a shared folder that’s accessible over a network connection.
+- Write permissions to a shared folder that's accessible over a network connection.
 
 **Estimated time to complete the tutorial:** 30 minutes. An extra 30 minutes if you need to complete the basic report tutorial.