Changing header.

Author: roygara

articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md

@@ -27,7 +27,7 @@ This script creates a managed disk from a snapshot. Use it to restore a virtual
 
 [!code-powershell[main](../../../powershell_scripts/virtual-machine/create-managed-disk-from-snapshot/create-managed-disk-from-snapshot.ps1 "Create managed disk from snapshot")]
 
-## Performance impact - copy process
+## Performance impact - background copy process
 
 When you create a managed disk from a snapshot, it starts a background copy process. You can attach a disk to a VM while this process is running but you'll experience performance impact (4k disks experience read impact, 512e experience both read and write impact). For Ultra Disks and Premium SSD v2, you can check the status of the background copy process with the [Azure CLI](create-managed-disk-from-snapshot.md#performance-impact---copy-process). This isn't currently supported with the Azure PowerShell module.
 

includes/virtual-machines-disks-incremental-snapshots-restrictions.md

@@ -28,7 +28,7 @@ Incremental snapshots of Premium SSD v2 and Ultra Disks have the following extra
 - When an incremental snapshot of either a Premium SSD v2 or an Ultra Disk is created, a background copy process for that disk is started. While a background copy is ongoing, you can have up to three total snapshots pending. The process must complete before any more snapshots of that disk can be created.
 - Incremental snapshots of a Premium SSD v2 or an Ultra disk can't be used immediately after they're created. The background copy must complete before you can create a disk from the snapshot. See [Check snapshot status](#check-snapshot-status) for details.
 - Taking increment snapshots of a Premium SSD v2 or an Ultra disk while the CompletionPercent property of the disk hasn't reached 100 isn't supported.
-- When you attach a Premium SSD v2 or Ultra disk created from snapshot to a running Virtual Machine while CompletionPercent property hasn't reached 100, the disk suffers performance impact. Specifically, if the disk has a 4k sector size, it may experience slower read. If the disk has a 512e sector size, it may experience slower read and write. To track the progress of this background copy process, see the the check disk status section of either the Azure [PowerShell sample](../articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md#performance-impact---copy-process) or the [Azure CLI](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#performance-impact---copy-process).
+- When you attach a Premium SSD v2 or Ultra disk created from snapshot to a running Virtual Machine while CompletionPercent property hasn't reached 100, the disk suffers performance impact. Specifically, if the disk has a 4k sector size, it may experience slower read. If the disk has a 512e sector size, it may experience slower read and write. To track the progress of this background copy process, see the the check disk status section of either the Azure [PowerShell sample](../articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md#performance-impact--background-copy-process) or the [Azure CLI](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#performance-impact---copy-process).
 
 > [!NOTE]
 > Normally, when you take an incremental snapshot, and there aren't any changes, the size of that snapshot is 0 MiB. Currently, empty snapshots of disks with a 4096 logical sector size instead have a size of 6 MiB, when they'd normally be 0 MiB.