Merge pull request #247134 from SadiqhAhmed-MSFT/patch-47

Update vmware-physical-azure-troubleshoot-process-server.md

Author: prmerger-automator[bot]

articles/site-recovery/vmware-physical-azure-troubleshoot-process-server.md

@@ -53,7 +53,7 @@ The process server generates a number of health alerts. These alerts, and recomm
 ![Critical][red] | Memory usage > 95% for the last 15 minutes. | 1. Don't add new machines, and considering setting up an [additional process server](vmware-azure-set-up-process-server-scale.md).<br/> 2. Follow any instructions associated with the warning.<br/> 3. 4. If the issue continues, follow the instructions below to [troubleshoot connectivity and replication issues](#check-connectivity-and-replication).<br/> 4. If the issue persists, run the [Deployment Planner](./site-recovery-deployment-planner.md) for VMware/physical server replication issues.
 ![Warning][yellow] | Cache folder free space < 30% for the last 15 minutes. | 1. Don't add new machines, and consider setting up an [additional process server](vmware-azure-set-up-process-server-scale.md).<br/>2. Check that the number of VMs using the process server aligns to [guidelines](site-recovery-plan-capacity-vmware.md#capacity-considerations).<br/> 3. Follow the instructions below to [troubleshoot connectivity and replication issues](#check-connectivity-and-replication).
 ![Critical][red] |  Free space < 25% for last 15 minutes | 1. Follow the instructions associated with the warning for this issue.<br/> 2. 3. Follow the instructions below to [troubleshoot connectivity and replication issues](#check-connectivity-and-replication).<br/> 3. If the issue persists, run the [Deployment Planner](./site-recovery-deployment-planner.md) for VMware/physical server replication.
-![Critical][red] | No heartbeat from the process server for 15 minutes or more. The tmansvs service isn't communicating with the configuration server. | 1) Check that the process server is up and running.<br/> 2. Check that the tmassvc is running on the process server.<br/> 3. Follow the instructions below to [troubleshoot connectivity and replication issues](#check-connectivity-and-replication).
+![Critical][red] | No heartbeat from the process server for 15 minutes or more. The tmansvs service isn't communicating with the configuration server. | 1) Check that the process server is up and running.<br/> 2. Check that the tmansvc is running on the process server.<br/> 3. Follow the instructions below to [troubleshoot connectivity and replication issues](#check-connectivity-and-replication).
 
 
 ![Table key](./media/vmware-physical-azure-troubleshoot-process-server/table-key.png)
@@ -246,4 +246,4 @@ If you need more help, post your question in the [Microsoft Q&A question page fo
 
 [green]: ./media/vmware-physical-azure-troubleshoot-process-server/green.png
 [yellow]: ./media/vmware-physical-azure-troubleshoot-process-server/yellow.png
-[red]: ./media/vmware-physical-azure-troubleshoot-process-server/red.png
+[red]: ./media/vmware-physical-azure-troubleshoot-process-server/red.png