fix bookmark links

Author: haywoodsloan

support/sql/azure-sql/sql-installation-fails-sector-size-error-azure-vm.md

@@ -53,7 +53,7 @@ To resolve this problem, reinstall SQL Server after forcing the Azure VM to use
 To successfully install SQL Server on your Azure VM, follow these steps:
 
 1. If you've already installed SQL Server, uninstall SQL Server. Otherwise, skip to the next step. 
-1. Add the [ForcedPhysicalSectorSizeInBytes](../database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolutions) registry key. 
+1. Add the [ForcedPhysicalSectorSizeInBytes](../database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolution-steps-for-disk-sector-size-errors-in-sql-server) registry key. 
 1. Verify the sector size is 4 KB by running the following command in an elevated command prompt:
 
    `fsutil fsinfo sectorinfo <volume pathname>`

support/sql/database-engine/connect/network-related-or-instance-specific-error-occurred-while-establishing-connection.md

@@ -11,7 +11,7 @@ ms.reviewer: jopilov
 
 _Applies to:_   SQL Server
 
-When connecting to a SQL Server instance, you may encounter one or more of the following [error messages](#error-messages). This article provides some steps to help you troubleshoot these errors, which are provided in order of the issues from simple to complex.
+When connecting to a SQL Server instance, you may encounter one or more of the following [error messages](#common-sql-server-connection-error-messages). This article provides some steps to help you troubleshoot these errors, which are provided in order of the issues from simple to complex.
 
 ## Common SQL Server connection error messages
 

support/sql/database-engine/performance/performance-degradation-misaligned-io-sector-error.md

@@ -55,7 +55,7 @@ The following screenshot shows the output of the `fsutil fsinfo sectorinfo` comm
 
 ## Resolution 
 
-If you're experiencing performance degradation due to misaligned I/O operations and can't [modify your sector size](../database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolutions), you can use [Trace Flag 1800](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf1800) as a global startup parameter to force SQL Server to use a consistent 4-KB sector size for transaction log I/O operations.
+If you're experiencing performance degradation due to misaligned I/O operations and can't [modify your sector size](../database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolution-steps-for-disk-sector-size-errors-in-sql-server), you can use [Trace Flag 1800](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf1800) as a global startup parameter to force SQL Server to use a consistent 4-KB sector size for transaction log I/O operations.
 
 To enable Trace Flag 1800 as a startup parameter, follow these steps:
 

support/sql/database-engine/security/transfer-logins-passwords-between-instances.md

@@ -284,8 +284,8 @@ To generate scripts via SSMS on the source server and manually reset passwords f
      ```
 
 1. The output script that the `sp_help_revlogin` stored procedure generates is the login script. This login script creates the logins that have the original Security Identifier (SID) and the original password.
-1. Review and follow the information in the [Remarks](#remarks) section before you proceed with implementing steps on the destination server.
-1. Once you implement any applicable steps from the [Remarks](#remarks) section, connect to the destination server B using any client tool (like SSMS).
+1. Review and follow the information in the [Additional considerations when transferring SQL Server logins](#additional-considerations-when-transferring-sql-server-logins) section before you proceed with implementing steps on the destination server.
+1. Once you implement any applicable steps from the [Additional considerations when transferring SQL Server logins](#additional-considerations-when-transferring-sql-server-logins) section, connect to the destination server B using any client tool (like SSMS).
 1. Run the script generated as the output of `sp_helprevlogin` from server A.
 
 ## Additional considerations when transferring SQL Server logins