fixing things

Author: MashaMSFT

articles/azure-sql/database/replication-to-sql-database.md

@@ -22,7 +22,7 @@ You can configure an Azure SQL Database as the push subscriber in a one-way tran
 ## Supported Configurations
 
 - Azure SQL Database can only be the push subscriber of a SQL Server publisher and distributor.  
-- The SQL Server acting as publisher and/or distributor can be an instance of [SQL Server running on-premises](https://www.microsoft.com/sql-server/sql-server-downloads), an [Azure SQL Managed Instance](../azure-sql/managed-instance/instance-create-quickstart.md), or an instance of [SQL Server running on an Azure virtual machine in the cloud](../virtual-machines/windows/sql-vm-create-portal-quickstart.md). 
+- The SQL Server acting as publisher and/or distributor can be an instance of [SQL Server running on-premises](https://www.microsoft.com/sql-server/sql-server-downloads), an [Azure SQL Managed Instance](../managed-instance/instance-create-quickstart.md), or an instance of [SQL Server running on an Azure virtual machine in the cloud](../virtual-machines/windows/sql-vm-create-portal-quickstart.md). 
 - The distribution database and the replication agents cannot be placed on an Azure SQL database.  
 - [Snapshot](/sql/relational-databases/replication/snapshot-replication) and [one-way transactional](/sql/relational-databases/replication/transactional/transactional-replication) replication are supported. Peer-to-peer transactional replication and merge replication are not supported.
 

articles/azure-sql/virtual-machines/windows/doc-changes-updates-release-notes.md

@@ -31,7 +31,7 @@ Azure allows you to deploy a virtual machine (VM) with an image of SQL Server bu
 |Changes | Details |
  --- | --- |
 | **Free DR replica in Azure** | You can host a [free passive instance](business-continuity-high-availability-disaster-recovery-hadr-overview.md#free-dr-replica-in-azure) for disaster recovery in Azure for your on-premises SQL Server instance if you have [Software Assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default?rtc=1&activetab=software-assurance-default-pivot:primaryr3). | 
-| **Bulk resource provider registration** | You can now [bulk register](sql-vm-resource-provider-register-bulk.md) SQL virtual machines with the resource provider. | 
+| **Bulk resource provider registration** | You can now [bulk register](sql-vm-resource-provider-bulk-register.md) SQL virtual machines with the resource provider. | 
 |**Performance Optimized Storage Configuration** | You can now [fully customize your storage configuration](storage-configuration.md#new-vms) when creating a new SQL Server VM. |
 |**Premium file share for FCI** | You can now create a failover cluster instance using a [Premium File Share](failover-cluster-instance-premium-file-share-manually-configure.md) instead of the original method of [Storage Spaces Direct](failover-cluster-instance-storage-spaces-direct-manually-configure.md). 
 | **Azure dedicated host** | You can run your SQL Server VM on an [Azure Dedicated Host](dedicated-host.md). | 

articles/azure-sql/virtual-machines/windows/sql-vm-resource-provider-bulk-register.md

@@ -23,13 +23,13 @@ The `Register-SqlVMs` cmdlet can be used to register all virtual machines in a g
 
 The registration process carries no risk, has no downtime, and will not restart SQL Server or the virtual machine. 
 
-For more information about the resource provider, see [SQL VM resource provider](sql-resource-provider-register.md). 
+For more information about the resource provider, see [SQL VM resource provider](sql-vm-resource-provider-register.md). 
 
 ## Prerequisites
 
 To register your SQL Server VM with the resource provider, you'll need the following: 
 
-- An [Azure subscription](https://azure.microsoft.com/free/) that has been [registered with the resource provider](sql-resource-provider-register.md#register-subscription-with-rp) and contains unregistered SQL Server virtual machines. 
+- An [Azure subscription](https://azure.microsoft.com/free/) that has been [registered with the resource provider](sql-vm-resource-provider-register.md#register-subscription-with-rp) and contains unregistered SQL Server virtual machines. 
 - The client credentials used to register the virtual machines exist in any of the following RBAC roles: **Virtual Machine contributor**, **Contributor**, or **Owner**. 
 - The latest version of [Az PowerShell](/powershell/azure/new-azureps-module-az). 
 - The latest version of [Az.SqlVirtualMachine](https://www.powershellgallery.com/packages/Az.SqlVirtualMachine/0.1.0).
@@ -217,7 +217,7 @@ Errors are logged in the log file named `VMsNotRegisteredDueToError<Timestamp>.l
 
 When you register SQL Server VMs with the resource provider using the provided script, consider the following:
 
-- Registration with the resource provider requires a guest agent running on the SQL Server VM. Windows Server 2008 images do not have a guest agent, so these virtual machines will fail and must be registered manually using the [NoAgent management mode](sql-resource-provider-register.md#management-modes).
+- Registration with the resource provider requires a guest agent running on the SQL Server VM. Windows Server 2008 images do not have a guest agent, so these virtual machines will fail and must be registered manually using the [NoAgent management mode](sql-vm-resource-provider-register.md#management-modes).
 - There is retry logic built-in to overcome transparent errors. If the virtual machine is successfully registered, then it is a rapid operation. However, if the registration fails, then each virtual machine will be retried.  As such, you should allow significant time to complete the registration process -  though actual time requirement is dependent on the type and number of errors. 
 
 ## Full script

articles/azure-sql/virtual-machines/windows/sql-vm-resource-provider-register.md

@@ -94,7 +94,7 @@ To register your SQL Server VM with the SQL VM resource provider, you must first
 1. Enter **sql** in the filter to bring up the SQL-related resource providers. 
 1. Select **Register**, **Re-register**, or **Unregister** for the  **Microsoft.SqlVirtualMachine** provider, depending on your desired action. 
 
-![Modify the provider](./media/sql-resource-provider-register/select-resource-provider-sql.png)
+![Modify the provider](./media/sql-vm-resource-provider-register/select-resource-provider-sql.png)
 
 
 ### Command line
@@ -245,11 +245,11 @@ To upgrade the agent mode to full:
 1. Select your SQL Server virtual machine, and select **Overview**. 
 1. For SQL Server VMs with the NoAgent or lightweight IaaS mode, select the **Only license type and edition updates are available with the SQL IaaS extension** message.
 
-   ![Selections for changing the mode from the portal](./media/sql-resource-provider-register/change-sql-iaas-mode-portal.png)
+   ![Selections for changing the mode from the portal](./media/sql-vm-resource-provider-register/change-sql-iaas-mode-portal.png)
 
 1. Select the **I agree to restart the SQL Server service on the virtual machine** check box, and then select **Confirm** to upgrade your IaaS mode to full. 
 
-    ![Check box for agreeing to restart the SQL Server service on the virtual machine](./media/sql-resource-provider-register/enable-full-mode-iaas.png)
+    ![Check box for agreeing to restart the SQL Server service on the virtual machine](./media/sql-vm-resource-provider-register/enable-full-mode-iaas.png)
 
 ### Command line
 
@@ -286,7 +286,7 @@ You can verify if your SQL Server VM has already been registered with the SQL VM
 1. Select your SQL Server VM from the list. If your SQL Server VM is not listed here, it likely hasn't been registered with the SQL VM resource provider. 
 1. View the value under **Status**. If **Status** is **Succeeded**, then the SQL Server VM has been registered with the SQL VM resource provider successfully. 
 
-![Verify status with SQL RP registration](./media/sql-resource-provider-register/verify-registration-status.png)
+![Verify status with SQL RP registration](./media/sql-vm-resource-provider-register/verify-registration-status.png)
 
 ### Command line
 
@@ -323,15 +323,15 @@ To unregister your SQL Server VM with the resource provider using the Azure port
 1. Sign into the [Azure portal](https://portal.azure.com).
 1. Navigate to the SQL Server VM resource. 
 
-   ![SQL virtual machines resource](./media/sql-resource-provider-register/sql-vm-manage.png)
+   ![SQL virtual machines resource](./media/sql-vm-resource-provider-register/sql-vm-manage.png)
 
 1. Select **Delete**. 
 
-   ![Delete SQL VM resource provider](./media/sql-resource-provider-register/delete-sql-vm-resource-provider.png)
+   ![Delete SQL VM resource provider](./media/sql-vm-resource-provider-register/delete-sql-vm-resource-provider.png)
 
 1. Type the name of the SQL virtual machine and **clear the checkbox next to the virtual machine**.
 
-   ![Delete SQL VM resource provider](./media/sql-resource-provider-register/confirm-delete-of-resource-uncheck-box.png)
+   ![Delete SQL VM resource provider](./media/sql-vm-resource-provider-register/confirm-delete-of-resource-uncheck-box.png)
 
    >[!WARNING]
    > Failure to clear the checkbox next to the virtual machine name will *delete* the virtual machine entirely. Clear the checkbox to unregister the SQL Server VM from the resource provider but *not delete the actual virtual machine*.