Adding line spaces for consistency

Author: ShawnJackson

articles/site-recovery/vmware-azure-troubleshoot-configuration-server.md

@@ -48,8 +48,11 @@ The source machine registers with the configuration server when you install the
     - If the string is found:
 
       1. Resolve the network issues between the source machine and the configuration server. Verify that the configuration server is reachable from the source machine by using network tools like ping, traceroute, or a web browser. Ensure that the source machine can reach the configuration server through port 443.
+ 
       1. Check whether any firewall rules on the source machine block the connection between the source machine and the configuration server. Work with your network admins to unblock any connection issues.
+
       1. Ensure that the folders listed in [Site Recovery folder exclusions from antivirus programs](vmware-azure-set-up-source.md#azure-site-recovery-folder-exclusions-from-antivirus-program) are excluded from the antivirus software.
+
       1. When network issues are resolved, retry the registration by following the guidelines in [Register the source machine with the configuration server](vmware-azure-troubleshoot-configuration-server.md#register-source-machine-with-configuration-server).
 
     - If the string isn't found:
@@ -66,8 +69,11 @@ The source machine registers with the configuration server when you install the
 1. On Linux, if the value of the platform in `<INSTALLATION_DIR\>/etc/drscout.conf` is corrupted, registration fails. To identify this issue, open the `/var/log/ua_install.log` file. Search for the string **Aborting configuration as VM_PLATFORM value is either null or it is not VmWare/Azure**. The platform should be set to either **VmWare** or **Azure**. If the `drscout.conf` file is corrupted, we recommend that you [uninstall the mobility agent](vmware-physical-manage-mobility-service.md#uninstall-mobility-service) and then reinstall the mobility agent. If uninstallation fails, follow these steps:
 
     1. Open the `Installation_Directory/uninstall.sh` file and comment out the call to the `StopServices` function.
+
     1. Open the `Installation_Directory/Vx/bin/uninstall.sh` file and comment out the call to the `stop_services` function.
+
     1. Open the `Installation_Directory/Fx/uninstall.sh` file and comment out the entire section that's trying to stop the Fx service.
+
     1. [Uninstall](vmware-physical-manage-mobility-service.md#uninstall-mobility-service) the mobility agent. After successful uninstallation, reboot the system, and then try to reinstall the mobility agent.
 
 1. Ensure that multifactor authentication (MFA) isn't enabled for the user account. Currently, Site Recovery doesn't support MFA for user accounts. Register the configuration server without the MFA-enabled user account.