Merge pull request #19977 from MikeRayMSFT/20210812-fix-warnings

PRMerger14 · web-flow · commit dc1b89380497 · 2021-08-13T00:03:35.000+05:30
Fix formatting and warnings
diff --git a/docs/relational-databases/track-changes/about-change-data-capture-sql-server.md b/docs/relational-databases/track-changes/about-change-data-capture-sql-server.md
@@ -123,7 +123,7 @@ Although it is common for the database validity interval and the validity interv
 In Azure SQL Database, a change data capture scheduler takes the place of the SQL Server Agent that invokes stored procedures to start periodic capture and cleanup of the change data capture tables. The scheduler runs capture and cleanup automatically within SQL Database, without any external dependency for reliability or performance. Users still have the option to run capture and cleanup manually on demand. 
 
 > [!NOTE]
-> Support for change data capture in Azure SQL Database is currently in [Preview](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). 
+> Support for change data capture in Azure SQL Database is currently in [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). 
  
 ## Collation differences
 
diff --git a/docs/relational-databases/track-changes/administer-and-monitor-change-data-capture-sql-server.md b/docs/relational-databases/track-changes/administer-and-monitor-change-data-capture-sql-server.md
@@ -22,7 +22,7 @@ ms.custom: seo-dt-2019
 This topic describes how to administer and monitor change data capture.  
   
 > [!NOTE]  
-> Support for change data capture in Azure SQL Database is currently in [Preview](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). In Azure SQL Database, the capture and cleanup SQL Server Agent jobs are replaced by a change data capture scheduler that invokes stored procedures to start periodic capture and cleanup of the change tables. 
+> Support for change data capture in Azure SQL Database is currently in [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). In Azure SQL Database, the capture and cleanup SQL Server Agent jobs are replaced by a change data capture scheduler that invokes stored procedures to start periodic capture and cleanup of the change tables. 
 
 ## <a name="Capture"></a> Capture job
 
diff --git a/docs/relational-databases/track-changes/change-data-capture-and-other-sql-server-features.md b/docs/relational-databases/track-changes/change-data-capture-and-other-sql-server-features.md
@@ -74,14 +74,14 @@ This topic describes how the following features interact with change data captur
 Running point-in-time-restore (PITR) on a Azure SQL Database that has change data capture enabled will not preserve the change data capture artifacts (e.g. system tables). After PITR, CDC artifacts will not be available.
 
 > [!NOTE]
-> Support for change data capture in Azure SQL Database is currently in [Preview](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). 
+> Support for change data capture in Azure SQL Database is currently in [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). 
 
 ##  <a name="AzureActiveDirectory"></a> Azure Active Directory in Azure SQL Database (Preview)
 
 If you create a database in Azure SQL Database as an AAD user and enable change data capture on it, a SQL user (e.g. even sys admin role) will not be able to disable/make changes to change data capture artifacts. However, another AAD user will be able to enable/disable change data capture on the same database. 
 
 > [!NOTE]
-> Support for change data capture in Azure SQL Database is currently in [Preview](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). 
+> Support for change data capture in Azure SQL Database is currently in [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). 
 
 
 ## See Also  
diff --git a/docs/relational-databases/track-changes/enable-and-disable-change-data-capture-sql-server.md b/docs/relational-databases/track-changes/enable-and-disable-change-data-capture-sql-server.md
@@ -22,7 +22,7 @@ ms.author: jroth
   This topic describes how to enable and disable change data capture for a database and a table.  
 
 > [!NOTE]
-> Support for change data capture in Azure SQL Database is currently in [Preview](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). 
+> Support for change data capture in Azure SQL Database is currently in [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). 
   
 ## Enable for a database  
 
diff --git a/docs/relational-databases/track-changes/work-with-change-data-sql-server.md b/docs/relational-databases/track-changes/work-with-change-data-sql-server.md
@@ -24,7 +24,7 @@ ms.author: jroth
  Several functions are provided to help determine appropriate LSN values for use in querying a TVF. The function [sys.fn_cdc_get_min_lsn](../../relational-databases/system-functions/sys-fn-cdc-get-min-lsn-transact-sql.md) returns the smallest LSN that is associated with a capture instance validity interval. The validity interval is the time interval for which change data is currently available for its capture instances. The function [sys.fn_cdc_get_max_lsn](../../relational-databases/system-functions/sys-fn-cdc-get-max-lsn-transact-sql.md) returns the largest LSN in the validity interval. The functions [sys.fn_cdc_map_time_to_lsn](../../relational-databases/system-functions/sys-fn-cdc-map-time-to-lsn-transact-sql.md) and [sys.fn_cdc_map_lsn_to_time](../../relational-databases/system-functions/sys-fn-cdc-map-lsn-to-time-transact-sql.md) are available to help place LSN values on a conventional timeline. Because change data capture uses closed query intervals, it is sometimes necessary to generate the next LSN value in a sequence to ensure that changes are not duplicated in consecutive query windows. The functions [sys.fn_cdc_increment_lsn](../../relational-databases/system-functions/sys-fn-cdc-increment-lsn-transact-sql.md) and [sys.fn_cdc_decrement_lsn](../../relational-databases/system-functions/sys-fn-cdc-decrement-lsn-transact-sql.md) are useful when an incremental adjustment to an LSN value is required.  
 
 > [!NOTE]
-> Support for change data capture in Azure SQL Database is currently in [Preview](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). 
+> Support for change data capture in Azure SQL Database is currently in [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). 
 
 ##  <a name="LSN"></a> Validating LSN Boundaries  
  We recommend validating the LSN boundaries that are to be used in a TVF query before their use. Null endpoints or endpoints that lie outside the validity interval for a capture instance will force an error to be returned by a change data capture TVF.  
diff --git a/docs/tools/synapse-pathway/synapse-pathway-download.md b/docs/tools/synapse-pathway/synapse-pathway-download.md
@@ -43,8 +43,8 @@ Download the latest version of the tool from the [Microsoft Download Center](htt
 ## Pricing
 
 1. Synapse Pathway is **free to download**. There's no associated cost to run your code translation.
-1. Data Ingress: There's no cost associated with bringing your data into Azure. For more information, see the [Bandwidth pricing details](https://azure.microsoft.com/en-us/pricing/details/bandwidth/).
-1. See the [Azure Synapse pricing page](https://azure.microsoft.com/en-us/pricing/calculator/?service=synapse-analytics) to see the cost of provisioning Azure Synapse.
+1. Data Ingress: There's no cost associated with bringing your data into Azure. For more information, see the [Bandwidth pricing details](https://azure.microsoft.com/pricing/details/bandwidth/).
+1. See the [Azure Synapse pricing page](https://azure.microsoft.com/pricing/calculator/?service=synapse-analytics) to see the cost of provisioning Azure Synapse.
 
 ## Next steps
 
