feedback updates

Author: davidsmatlak

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -211,7 +211,7 @@ Azure Disk Encryption (ADE) for Windows OS | Supported for VMs with managed disk
 Azure Disk Encryption (ADE) for Linux OS | Supported for VMs with managed disks. | VMs using unmanaged disks are not supported. <br/><br/> HSM-protected keys are not supported. |
 Hot add    | Supported | Enabling replication for a data disk that you add to a replicated Azure VM is supported for VMs that use managed disks.
 Hot remove disk    | Not supported | If you  remove data disk on the VM, you need to disable replication and enable replication again for the VM.
-Exclude disk | Support. You must use [Powershell](azure-to-azure-exclude-disks.md) to configure. |    Temporary disks are excluded by default.
+Exclude disk | Support. You must use [PowerShell](azure-to-azure-exclude-disks.md) to configure. |    Temporary disks are excluded by default.
 Storage Spaces Direct  | Supported for crash consistent recovery points. Application consistent recovery points are not supported. |
 Scale-out File Server  | Supported for crash consistent recovery points. Application consistent recovery points are not supported. |
 DRBD | Disks that are part of a DRBD setup are not supported. |

articles/site-recovery/azure-to-azure-troubleshoot-errors.md

@@ -159,11 +159,11 @@ Because SUSE Linux uses symbolic links (or *symlinks*) to maintain a certificate
 
 ## Outbound connectivity for Site Recovery URLs or IP ranges (error code 151037 or 151072)
 
-For Site Recovery replication to work, outbound connectivity to specific URLs is required from the VM. If your VM is behind a firewall or uses network security group (NSG) rules to control outbound connectivity, you might face one of these issues. Please note that while we continue to support outbound access via URLs, whitelisting of IP ranges is no longer supported.
+For Site Recovery replication to work, outbound connectivity to specific URLs is required from the VM. If your VM is behind a firewall or uses network security group (NSG) rules to control outbound connectivity, you might face one of these issues. Please note that while we continue to support outbound access via URLs, using an allow list of IP ranges is no longer supported.
 
 ### <a name="issue-1-failed-to-register-azure-virtual-machine-with-site-recovery-151195-br"></a>Issue 1: Failed to register Azure virtual machine with Site Recovery (151195) </br>
 - **Possible cause** </br>
-  - Connection cannot be established to site recovery endpoints due to DNS resolution failure.
+  - Connection cannot be established to Site Recovery endpoints due to DNS resolution failure.
   - This is more frequently seen during re-protection when you have failed over the virtual machine but the DNS server is not reachable from the DR region.
 
 - **Resolution**
@@ -186,7 +186,7 @@ For Site Recovery replication to work, outbound connectivity to specific URLs is
   - Connection cannot be established to Azure Site Recovery service endpoints.
 
 - **Resolution**
-  - If you are using Azure Network Security Group (NSG) rules/firewall proxy to control outbound network connectivity on the VM, please ensure you use service tags. We no longer support whitelisting of IP addresses via NSGs for ASR.
+  - If you are using Azure Network Security Group (NSG) rules/firewall proxy to control outbound network connectivity on the VM, please ensure you use service tags. We no longer support using an allow list of IP addresses via NSGs for Azure Site Recovery (ASR).
 
 
 ### Issue 4: A2A replication failed when the network traffic goes through on-premise proxy server (151072)
@@ -207,7 +207,8 @@ For Site Recovery replication to work, outbound connectivity to specific URLs is
 
 
 ### Fix the problem
-To whitelist [the required URLs](azure-to-azure-about-networking.md#outbound-connectivity-for-urls), follow the steps in the [networking guidance document](site-recovery-azure-to-azure-networking-guidance.md).
+
+To add [the required URLs](azure-to-azure-about-networking.md#outbound-connectivity-for-urls) to an allow list, follow the steps in the [networking guidance document](site-recovery-azure-to-azure-networking-guidance.md).
 
 
 ### More information