fix missing link extensions

Author: haywoodsloan

support/sql/database-engine/general/error-556-insert-exec-failed.md

@@ -37,7 +37,7 @@ The auto-cleanup process flushes the plan out of Query Data Store. The query enc
 
 This issue is fixed in the following service pack for SQL Server:  
 
-[Service Pack 3 for SQL Server 2016](~/sql/releases/sqlserver-2016/servicepack3)
+[Service Pack 3 for SQL Server 2016](~/sql/releases/sqlserver-2016/servicepack3.md)
 
 **About service packs for SQL Server:**  
 

support/sql/database-engine/performance/buffer-pool-scan-runs-slowly-large-memory-machines.md

@@ -33,13 +33,13 @@ Here are some operations that may trigger a buffer pool scan to occur:
 
 ### Error log shows that a scan took a long time
 
-Starting with [SQL Server 2016 SP3](~/sql/releases/sqlserver-2016/servicepack3), [SQL Server 2017 CU23](~/sql/releases/sqlserver-2017/cumulativeupdate23#bkmk_13741858) and [SQL Server 2019 CU9](~/sql/releases/sqlserver-2019/cumulativeupdate9#bkmk_13744390), an error message was added to the SQL Server [Error log](/sql/tools/configuration-manager/viewing-the-sql-server-error-log) to indicate that a buffer pool scan took a long time (10 seconds or longer):
+Starting with [SQL Server 2016 SP3](~/sql/releases/sqlserver-2016/servicepack3.md), [SQL Server 2017 CU23](~/sql/releases/sqlserver-2017/cumulativeupdate23.md#bkmk_13741858) and [SQL Server 2019 CU9](~/sql/releases/sqlserver-2019/cumulativeupdate9.md#bkmk_13744390), an error message was added to the SQL Server [Error log](/sql/tools/configuration-manager/viewing-the-sql-server-error-log) to indicate that a buffer pool scan took a long time (10 seconds or longer):
 
 > Buffer Pool scan took 14 seconds: database ID 7, command 'BACKUP DATABASE', operation 'FlushCache', scanned buffers 115, total iterated buffers 204640239, wait time 0 ms. See 'https://go.microsoft.com/fwlink/?linkid=2132602' for more information.
 
 ### Extended Event to diagnose a long scan
 
-Also, starting with the same builds [SQL Server 2016 SP3](~/sql/releases/sqlserver-2016/servicepack3), [SQL Server 2017 CU23](~/sql/releases/sqlserver-2017/cumulativeupdate23#bkmk_13741858) and [SQL Server 2019 CU9](~/sql/releases/sqlserver-2019/cumulativeupdate9#bkmk_13744390)  the **buffer_pool_scan_complete** Extended event was introduced to help you identify long buffer pool scans.
+Also, starting with the same builds [SQL Server 2016 SP3](~/sql/releases/sqlserver-2016/servicepack3.md), [SQL Server 2017 CU23](~/sql/releases/sqlserver-2017/cumulativeupdate23.md#bkmk_13741858) and [SQL Server 2019 CU9](~/sql/releases/sqlserver-2019/cumulativeupdate9.md#bkmk_13744390)  the **buffer_pool_scan_complete** Extended event was introduced to help you identify long buffer pool scans.
 
 If a scan takes more than 1 second, the XEvent will be recorded as follows when the event is enabled.
 

support/sql/database-engine/replication/understand-merge-replication-article-process.md

@@ -78,7 +78,7 @@ The Merge Agent processes generations in batches, also referred to as generation
 
 In a situation where multiple generation batches are exchanged, the Merge Agent may split related parent and child changes across two separate generation batches. If that is the case, the Merge Agent may deliver a child change in a generation batch ahead of the generation batch that contains the associated parent change. In hierarchical merge topologies that use re-publishers, there is one rare situation in which the splitting of parent and child changes across generation batches can lead to non-convergence. For more information about non-convergence, see the following article:
 
-[Non-convergence when SQL Server processes child and parent generations in separate generation batches](~/sql/database-engine/replication/non-convergence-when-processes-child-generations).  
+[Non-convergence when SQL Server processes child and parent generations in separate generation batches](~/sql/database-engine/replication/non-convergence-when-processes-child-generations.md).  
 
 You can increase the `-UploadGenerationsPerBatch` and the `-DownloadGenerationsPerBatch` parameters discussed previously to avoid splitting parent and child changes across generation batches.
 

support/sql/releases/faq-acronyms.md

@@ -56,11 +56,11 @@ For more information, go to the following websites:
 
 - [Announcing the Modern Servicing Model for SQL Server](https://techcommunity.microsoft.com/t5/sql-server/announcing-the-modern-servicing-model-for-sql-server/ba-p/385594)
 
-- [Naming schema and Fix area descriptions for SQL Server software update packages](~/sql/releases/naming-schema-and-fix-area)
+- [Naming schema and Fix area descriptions for SQL Server software update packages](~/sql/releases/naming-schema-and-fix-area.md)
 
-- [Description of the standard terminology that is used to describe Microsoft software updates](~/windows-client/installing-updates-features-roles/standard-terminology-software-updates)
+- [Description of the standard terminology that is used to describe Microsoft software updates](~/windows-client/installing-updates-features-roles/standard-terminology-software-updates.md)
 
-- [An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems](~/sql/releases/servicing-models-sql-server)
+- [An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems](~/sql/releases/servicing-models-sql-server.md)
 
 - [SQL Server documentation](/sql/sql-server/?view=sql-server-ver15&preserve-view=true)
 

support/sql/releases/naming-schema-and-fix-area.md

@@ -37,7 +37,7 @@ SQL Server software update packages typically fall into two major release types:
 
   - CU (Cumulative Update): CU releases are non-critical requests that provide fixes for isolated issues not affecting key business functionality. The CU releases on a two-month cadence while the product and service pack are in mainstream support.
 
-To learn more about the ISM and the different release types, which SQL Server servicing follows, see [An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems](~/sql/releases/servicing-models-sql-server).
+To learn more about the ISM and the different release types, which SQL Server servicing follows, see [An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems](~/sql/releases/servicing-models-sql-server.md).
 
 ## Naming schema for SQL Server software update packages