[BULK] Remove hidden non-breaking spaces from repo

Author: rwestMSFT

azure-sql/database/automated-backups-overview.md

@@ -120,23 +120,23 @@ Automatic backups on secondary replicas:
 
 This table summarizes the capabilities and features of [point-in-time restore (PITR)](recovery-using-backups.md#point-in-time-restore), [geo-restore](recovery-using-backups.md#geo-restore), and [long-term retention](long-term-retention-overview.md).
 
-| Backup property | PITR | Geo-restore | LTR |
+| Backup property | PITR | Geo-restore | LTR |
 |---|---|---|---|
 | **Types of SQL backup** | Full, differential, log. | Most recent geo-replicated copies of PITR backups. | Only the full backups. |
-| **Recovery point objective (RPO)** | 10 minutes, based on compute size and amount of database activity. | Up to 1 hour, based on geo-replication. <sup>1</sup> | One week (or user's policy).|
-| **Recovery time objective (RTO)** | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). |
-| **Retention** | 7 days by default, configurable between 1 and 35 days (except Basic databases, which are configurable between 1 and 7 days). | Enabled by default, same as source.<sup>2</sup>| Not enabled by default. Retention is up to 10 years. |
-| **Azure Storage**  | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant. Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
+| **Recovery point objective (RPO)** | 10 minutes, based on compute size and amount of database activity. | Up to 1 hour, based on geo-replication. <sup>1</sup> | One week (or user's policy).|
+| **Recovery time objective (RTO)** | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). | Restore usually takes less than 12 hours but could take longer, depending on size and activity. See [Recovery](recovery-using-backups.md#recovery-time). |
+| **Retention** | 7 days by default, configurable between 1 and 35 days (except Basic databases, which are configurable between 1 and 7 days). | Enabled by default, same as source.<sup>2</sup>| Not enabled by default. Retention is up to 10 years. |
+| **Azure Storage**  | Geo-redundant by default. You can optionally configure zone-redundant or locally redundant storage. | Available when PITR backup storage redundancy is set to geo-redundant. Not available when PITR backup storage is zone-redundant or locally redundant. | Geo-redundant by default. You can configure zone-redundant or locally redundant storage. |
 | **Configure backups as [immutable](/azure/storage/blobs/immutable-storage-overview)** | Not supported | Not supported | Not supported | 
-| **Restoring a new database in the same region** | Supported | Supported | Supported |
+| **Restoring a new database in the same region** | Supported | Supported | Supported |
 | **Restoring a new database in another region** | Not supported | Supported in any Azure region | Supported in any Azure region |
 | **Restoring a new database in another subscription** |  Not supported  |  Not supported<sup>3</sup> | Not supported<sup>3</sup> |
 | **Restoring via Azure portal**|Yes|Yes|Yes|
 | **Restoring via PowerShell** |Yes|Yes|Yes|
 | **Restoring via Azure CLI** |Yes|Yes|Yes|
 
 
-<sup>1</sup> For business-critical applications that require large databases and must ensure business continuity, use [failover groups](failover-group-sql-db.md).   
+<sup>1</sup> For business-critical applications that require large databases and must ensure business continuity, use [failover groups](failover-group-sql-db.md).   
 <sup>2</sup> All PITR backups are stored on geo-redundant storage by default, so geo-restore is enabled by default.   
 <sup>3</sup> The workaround is to restore to a new server and use Resource Move to move the server to another subscription, or use a [cross-subscription database copy](database-copy.md#copy-to-a-different-subscription).   
 

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

@@ -33,7 +33,7 @@ In this scenario, the applications have the following characteristics:
 * Web tier and data tier must be collocated to reduce latency and traffic cost
 * Fundamentally, downtime is a higher business risk for these applications than data loss
 
-In this case, the application deployment topology is optimized for handling regional disasters when all application components need to fail over together. The diagram below shows this topology. For geographic redundancy, the application's resources are deployed to Region A and B. However, the resources in Region B are not utilized until Region A fails. A failover group is configured between the two regions to manage database connectivity, replication and failover. The web service in both regions is configured to access the database via the read-write listener **<failover-group-name>.database.windows.net** (1). Azure Traffic Manager is set up to use [priority routing method](/azure/traffic-manager/traffic-manager-configure-priority-routing-method) (2).  
+In this case, the application deployment topology is optimized for handling regional disasters when all application components need to fail over together. The diagram below shows this topology. For geographic redundancy, the application's resources are deployed to Region A and B. However, the resources in Region B are not utilized until Region A fails. A failover group is configured between the two regions to manage database connectivity, replication and failover. The web service in both regions is configured to access the database via the read-write listener **<failover-group-name>.database.windows.net** (1). Azure Traffic Manager is set up to use [priority routing method](/azure/traffic-manager/traffic-manager-configure-priority-routing-method) (2).  
 
 > [!NOTE]
 > [Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview) is used throughout this article for illustration purposes only. You can use any load-balancing solution that supports priority routing method.

azure-sql/database/doc-changes-updates-release-notes-whats-new-archive.md

@@ -31,7 +31,7 @@ Return to [What's new in Azure SQL Database?](doc-changes-updates-release-notes-
 |**Always Encrypted with VBS enclaves GA** | November |  Take advantage of rich confidential queries and in-place encryption operations for Azure SQL Database with Always Encrypted with virtualization-based security (VBS) enclaves. This feature is now generally available. Review [Always Encrypted with VBS enclaves](always-encrypted-enclaves-getting-started-vbs.md) to get started. |
 |**DC-series hardware up to 40 vCores GA** | November |  DC-series hardware from 10 to 40 vCores is now generally available for General Purpose, Business Critical, and Hyperscale provisioned compute. Review [Resource limits](resource-limits-vcore-single-databases.md) for more information. |
 | **Elastic jobs preview refresh** | November |  [Updated with a preview refresh and new capabilities](https://techcommunity.microsoft.com/t5/azure-sql-blog/azure-sql-database-elastic-jobs-preview-refresh/ba-p/3965759), [elastic jobs](elastic-jobs-overview.md) are the SQL Server Agent replacement for Azure SQL Database. Elastic jobs now support Microsoft Entra ID (formerly Azure Active Directory) authentication, private endpoints, management via REST APIs, Azure Alerts, and new capabilities and user interface in the Azure portal. Job Agents now provide four capacity tiers to scale concurrency for job execution. |
-|**License-free standby replica preview** | November | Save on licensing costs by configuring your secondary database replica for disaster recovery standby. This feature is currently in preview. Review [License-free standby replica](standby-replica-how-to-configure.md) to learn more.  | 
+|**License-free standby replica preview** | November | Save on licensing costs by configuring your secondary database replica for disaster recovery standby. This feature is currently in preview. Review [License-free standby replica](standby-replica-how-to-configure.md) to learn more.  | 
 |**Premium-series hardware for Hyperscale elastic pools preview** | November | Premium-series and premium-series memory optimized hardware is now in preview for [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md). |
 | **Intelligent applications**| October | Learn how to use AI integration with Azure SQL Database, such as OpenAI, to build intelligent applications. To learn more, review [intelligent applications](ai-artificial-intelligence-intelligent-applications.md). |
 | **BASE64_ENCODE and BASE64_DECODE support** | September | The [BASE64_ENCODE](/sql/t-sql/functions/base64-encode-transact-sql) and [BASE64_DECODE](/sql/t-sql/functions/base64-decode-transact-sql) are now available in Azure SQL Database. |

azure-sql/database/elastic-jobs-powershell-create.md

@@ -48,7 +48,7 @@ Find-Package PowerShellGet | Install-Package -Force
 # Restart your powershell session with administrative access
 
 # Install and import the Az.Sql module, then confirm
-Install-Module -Name Az.Sql
+Install-Module -Name Az.Sql
 Import-Module Az.Sql
 Install-Module -Name SqlServer
 Import-Module SqlServer

azure-sql/database/elastic-transactions-overview.md

@@ -190,7 +190,7 @@ using (TransactionScope s = new TransactionScope())
         Helper.ExecuteNonQueryOnOpenConnection(conn, "BEGIN DISTRIBUTED TRAN");
         // ...
     }
- 
+ 
     using (SqlConnection conn2 = new SqlConnection(DB1_ConnectionString)
     {
         conn2.Open();

azure-sql/database/resource-limits-vcore-single-databases.md

@@ -193,7 +193,7 @@ The following table covers these SLOs: `HS_S_Gen5_2`, `HS_S_Gen5_4`, `HS_S_Gen5_
 | Max log size (TB) | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
 | Tempdb max data size (GB) | 64 | 128 | 192 | 256 | 320 | 384 | 448 |
 | Storage type | Multi-tiered <sup>1</sup>| Multi-tiered <sup>1</sup>| Multi-tiered <sup>1</sup>| Multi-tiered <sup>1</sup>| Multi-tiered <sup>1</sup>| Multi-tiered <sup>1</sup>| Multi-tiered <sup>1</sup>|
-| Max local SSD IOPS <sup>2</sup> | 8000 | 16000 | 24000 | 32000 | 40000 | 48000 | 56000 |
+| Max local SSD IOPS <sup>2</sup> | 8000 | 16000 | 24000 | 32000 | 40000 | 48000 | 56000 |
 | Max log rate (MBps) | 100 | 100 | 100 | 100 | 100 | 100 | 100 |
 | IO latency (approximate) | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup>| Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> |
 | Max concurrent workers | 150 | 300 | 450 | 600 | 750 | 900 | 1050 |
@@ -226,7 +226,7 @@ The following table covers these SLOs: `HS_S_Gen5_16`, `HS_S_Gen5_18`, `HS_S_Gen
 | Max log size (TB) | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
 | Tempdb max data size (GB) | 512 | 576 | 640 | 768 | 1024 | 1280 | 2560 |
 | Storage type | Multi-tiered <sup>1</sup> | Multi-tiered <sup>1</sup> | Multi-tiered <sup>1</sup> | Multi-tiered <sup>1</sup> | Multi-tiered <sup>1</sup> | Multi-tiered <sup>1</sup> | Multi-tiered <sup>1</sup> |
-| Max local SSD IOPS <sup>2</sup> | 64000 | 72000 | 80000 | 96000 | 128000 | 160000 | 204800 |
+| Max local SSD IOPS <sup>2</sup> | 64000 | 72000 | 80000 | 96000 | 128000 | 160000 | 204800 |
 | Max log rate (MBps) | 100 | 100 | 100 | 100 | 100 | 100 | 100 |
 | IO latency (approximate) | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> | Variable <sup>3</sup> |
 | Max concurrent workers | 1200 | 1350 | 1500 | 1800 | 2400 | 3000 | 6000 |

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

@@ -108,13 +108,13 @@ A central **Events Hub** page provides a list of links to the tenants in your de
 
     ![Events Hub](./media/saas-dbpertenant-get-started-deploy/events-hub.png)
 
-2. Select **Fabrikam Jazz Club** in the Events Hub.
+2. Select **Fabrikam Jazz Club** in the Events Hub.
 
     ![Events](./media/saas-dbpertenant-get-started-deploy/fabrikam.png)
 
 ### Azure Traffic Manager
 
-The Wingtip application uses [*Azure Traffic Manager*](/azure/traffic-manager/traffic-manager-overview) to control the distribution of incoming requests. The URL to access the events page for a specific tenant uses the following format:
+The Wingtip application uses [*Azure Traffic Manager*](/azure/traffic-manager/traffic-manager-overview) to control the distribution of incoming requests. The URL to access the events page for a specific tenant uses the following format:
 
 - http://events.wingtip-dpt.<user>.trafficmanager.net/fabrikamjazzclub
 
@@ -134,7 +134,7 @@ The Wingtip application uses [*Azure Traffic Manager*](/azure/traffic-manager/t
   - The catalog is implemented by using *shard map management*.
 - The Events Hub uses extended metadata in the catalog to construct the list-of-events page URLs for each tenant.
 
-In a production environment, typically you create a CNAME DNS record to [*point a company internet domain*](/azure/traffic-manager/traffic-manager-point-internet-domain) to the Traffic Manager DNS name.
+In a production environment, typically you create a CNAME DNS record to [*point a company internet domain*](/azure/traffic-manager/traffic-manager-point-internet-domain) to the Traffic Manager DNS name.
 
 > [!NOTE]
 > It may not be immediately obvious what the use of the traffic manager is in this tutorial. The goal of this series of tutorials is to showcase patterns that can handle the scale of a complex production environment. In such a case, for example, you would have multiple web apps distributed across the globe, co-located with databases and you would need traffic manager to route between these instances.
@@ -147,7 +147,7 @@ Now that the app is deployed, let's put it to work.
 The *Demo-LoadGenerator* PowerShell script starts a workload that runs against all tenant databases. The real-world load on many SaaS apps is sporadic and unpredictable. To simulate this type of load, the generator produces a load with randomized spikes or bursts of activity on each tenant. The bursts occur at randomized intervals. It takes several minutes for the load pattern to emerge. Let the generator run for at least three or four minutes before you monitor the load.
 
 1. In the PowerShell ISE, open the ...\\Learning Modules\\Utilities\\*Demo-LoadGenerator.ps1* script.
-2. Press F5 to run the script and start the load generator. Leave the default parameter values for now.
+2. Press F5 to run the script and start the load generator. Leave the default parameter values for now.
 3. Sign in to your Azure account, and select the subscription you want to use, if necessary.
 
 The load generator script starts a background job for each database in the catalog and then stops. If you rerun the load generator script, it stops any background jobs that are running before it starts new ones.
@@ -193,10 +193,10 @@ The initial deployment creates three sample tenants. Now you create another tena
 
 1. Open a new PowerShell ISE.
 2. Open ...\\Learning Modules\Provision and Catalog\\*Demo-ProvisionAndCatalog.ps1*.
-3. To run the script, press F5. Leave the default values for now.
+3. To run the script, press F5. Leave the default values for now.
 
    > [!NOTE]
-   > Many Wingtip SaaS scripts use *$PSScriptRoot* to browse folders to call functions in other scripts. This variable is evaluated only when the full script is executed by pressing F5. Highlighting and running a selection with F8 can result in errors. To run the scripts, press F5.
+   > Many Wingtip SaaS scripts use *$PSScriptRoot* to browse folders to call functions in other scripts. This variable is evaluated only when the full script is executed by pressing F5. Highlighting and running a selection with F8 can result in errors. To run the scripts, press F5.
 
 The new tenant database is:
 
@@ -214,7 +214,7 @@ Refresh the Events Hub to make the new tenant appear in the list.
 
 Now that you've started running a load against the collection of tenants, let's look at some of the resources that were deployed.
 
-1. In the [Azure portal](https://portal.azure.com), browse to your list of SQL servers. Then open the **catalog-dpt-<USER>** server.
+1. In the [Azure portal](https://portal.azure.com), browse to your list of SQL servers. Then open the **catalog-dpt-<USER>** server.
     - The catalog server contains two databases, **tenantcatalog** and **basetenantdb** (a template database that's copied to create new tenants).
 
     :::image type="content" source="./media/saas-dbpertenant-get-started-deploy/databases.png" alt-text="Screenshot that shows a catalog server Overview page with the two databases." lightbox="./media/saas-dbpertenant-get-started-deploy/databases.png":::
@@ -246,9 +246,9 @@ The two charts illustrate that elastic pools and SQL Database are well suited to
 ## Additional resources
 
 - For more information, see additional [tutorials that build on the Wingtip Tickets SaaS database-per-tenant application](saas-dbpertenant-wingtip-app-overview.md#sql-database-wingtip-saas-tutorials).
-- To learn about elastic pools, see [What is an Azure SQL elastic pool?](elastic-pool-overview.md)
-- To learn about elastic jobs, see [Manage scaled-out cloud databases](./elastic-jobs-overview.md).
-- To learn about multitenant SaaS applications, see [Design patterns for multitenant SaaS applications](saas-tenancy-app-design-patterns.md).
+- To learn about elastic pools, see [What is an Azure SQL elastic pool?](elastic-pool-overview.md)
+- To learn about elastic jobs, see [Manage scaled-out cloud databases](./elastic-jobs-overview.md).
+- To learn about multitenant SaaS applications, see [Design patterns for multitenant SaaS applications](saas-tenancy-app-design-patterns.md).
 
 ## Next steps
 

azure-sql/database/saas-tenancy-wingtip-app-guidance-tips.md

@@ -49,7 +49,7 @@ Setting these values here simply keeps you from having to update these deploymen
 
 ### Execute the scripts by pressing F5
 
-Several scripts use *$PSScriptRoot* to navigate folders, and *$PSScriptRoot* is only evaluated when scripts are executed by pressing **F5**.  Highlighting and running a selection (**F8**) can result in errors, so press **F5** when running scripts.
+Several scripts use *$PSScriptRoot* to navigate folders, and *$PSScriptRoot* is only evaluated when scripts are executed by pressing **F5**.  Highlighting and running a selection (**F8**) can result in errors, so press **F5** when running scripts.
 
 ### Step through the scripts to examine the implementation