PR feedback

Author: haywoodsloan

support/sql/database-engine/backup-restore/backup-restore-operations.md

@@ -214,7 +214,7 @@ You fail to restore a CRM backup from the Enterprise edition on a Standard editi
 
 **Resolution**
 
-To solve the issue, see [2567984 "Database cannot be started in this edition of SQL Server" error when restoring a Microsoft Dynamics CRM database](/previous-versions/troubleshoot/dynamics/crm/database-cannot-be-started-in-this-edition-of-sql-error-when-restoring).
+To solve the issue, see ["Database cannot be started in this edition of SQL Server" error when restoring a Microsoft Dynamics CRM database](/previous-versions/troubleshoot/dynamics/crm/database-cannot-be-started-in-this-edition-of-sql-error-when-restoring).
   
 ## FAQ about SQL Server backup and restore operations
 

support/sql/database-engine/replication/ascii-function-returns-different-results-publisher-subscriber.md

@@ -68,6 +68,6 @@ In this scenario, when you use the `ASCII` function to convert the column in the
 
 - To work around this issue for merge replication, follow these steps:
 
-    1. Apply [SQL Server 2019 Cumulative Update 15 (CU15)](https://support.microsoft.com/help/5008996) or a later version on the Distributor server.
+    1. Apply [SQL Server 2019 Cumulative Update 15 (CU15)](~/sql/releases/sqlserver-2019/cumulativeupdate15.md) or a later version on the Distributor server.
 
     1. Follow all the steps that are applied to the transactional replication issue.