PS selection updates

Rajeswari-Mamilla · Rajeswari-Mamilla · commit e191d54a8ccd · 2019-04-23T13:04:44.000+05:30
diff --git a/articles/site-recovery/vmware-azure-manage-process-server.md b/articles/site-recovery/vmware-azure-manage-process-server.md
@@ -70,12 +70,12 @@ Azure Site Recovery automatically identifies if Process Server is approaching it
 
 |Health Status  |Explanation  | Resource availability  | Recommendation|
 |---------|---------|---------|---------|
-| Healthy (Green)    |   Process server is connected and is healthy      |CPU and memory utilization is below 80%; Free space availability is above 30%| This process server can be used to protect additional servers. Ensure that the new workload is within the [defined process server limits](#sizing-requirements).
-|Warning (Orange)    |   Process server is connected but certain resources are about to reach maximum limits  |   CPU and memory utilization is between 80% - 95%; Free space availability is between 25% - 30%       | Usage of process server is close to threshold values. Adding new servers to same process server will lead to crossing the threshold values and can impact existing protected items. It is advised to [setup a scale-out process server](#before-you-start) for new replications.
-|Warning (Orange)   |   Process server is connected but data wasn't uploaded to Azure in last 30 min  |   Resource utilization is within threshold limits       | Troubleshoot [data upload failures](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) before adding new workloads **OR** [setup a scale-out process server](#before-you-start) for new replications.
-|Critical (Red)    |     Process server might be disconnected  |  Resource utilization is within threshold limits      | Troubleshoot [Process server connectivity issues](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) OR [setup a scale-out process server](#before-you-start) for new replications.
-|Critical (Red)    |     Resource utilization has crossed threshold limits |  CPU and memory utilization is above 95%; Free space availability is less than 25%.   | Adding new workloads to same process server is disabled as resource threshold limits are already met. So, [setup a scale-out process server](#before-you-start) for new replications.
-Critical (Red)    |     Data wasn't uploaded from Azure to Azure in last 45 min. |  CPU and memory utilization is above 95%; Free space availability is less than 25%.      | Troubleshoot [data upload failures](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) before adding new workloads to same process server OR [setup a scale-out process server](#before-you-start)
+| Healthy (Green)    |   Process server is connected and is healthy      |CPU and memory utilization is below 80%; Free space availability is above 30%| This process server can be used to protect additional servers. Ensure that the new workload is within the [defined process server limits](vmware-azure-set-up-process-server-scale.md#sizing-requirements).
+|Warning (Orange)    |   Process server is connected but certain resources are about to reach maximum limits  |   CPU and memory utilization is between 80% - 95%; Free space availability is between 25% - 30%       | Usage of process server is close to threshold values. Adding new servers to same process server will lead to crossing the threshold values and can impact existing protected items. It is advised to [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#before-you-start) for new replications.
+|Warning (Orange)   |   Process server is connected but data wasn't uploaded to Azure in last 30 min  |   Resource utilization is within threshold limits       | Troubleshoot [data upload failures](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) before adding new workloads **OR** [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#before-you-start) for new replications.
+|Critical (Red)    |     Process server might be disconnected  |  Resource utilization is within threshold limits      | Troubleshoot [Process server connectivity issues](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) OR [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#before-you-start) for new replications.
+|Critical (Red)    |     Resource utilization has crossed threshold limits |  CPU and memory utilization is above 95%; Free space availability is less than 25%.   | Adding new workloads to same process server is disabled as resource threshold limits are already met. So, [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#before-you-start) for new replications.
+Critical (Red)    |     Data wasn't uploaded from Azure to Azure in last 45 min. |  CPU and memory utilization is above 95%; Free space availability is less than 25%.      | Troubleshoot [data upload failures](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) before adding new workloads to same process server OR [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#before-you-start)
 
 ## Reregister a process server
 
