Updated RB installation instructions to retain the config files

Author: KarthikKR07

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -150,26 +150,24 @@ A typical onboarding that uses the script takes 30 to 60 minutes. During the pro
 
 After the command finishes running, your setup is complete. You can now use the capabilities of Azure Arc-enabled VMware vSphere.
 
-> [!IMPORTANT]
-> If the Azure Arc resource bridge deployment fails, clean up the installation and retry the deployment.
->
-> **Retry command - Windows**
->
-> Run the command with ```-Force``` to clean up the installation and onboard again.
->
->```powershell-interactive
->./resource-bridge-onboarding-script.ps1-Force -Subscription <Subscription> -ResourceGroup <ResourceGroup> -AzLocation <AzLocation> -ApplianceName <ApplianceName> -CustomLocationName <CustomLocationName> -vCenterservername <vCenterservername>
->```
->
-> **Retry command - Linux**
->
-> Run the command with ```--force``` to clean up the installation and onboard again.
->
->```bash
->bash resource-bridge-onboarding-script.sh --force
->```    
-> 
-> While there can be a number of reasons why the Azure Arc resource bridge deployment fails, one of them is KVA timeout error. For more information about the KVA timeout error and how to troubleshoot it, see [KVA timeout error](../resource-bridge/troubleshoot-resource-bridge.md#kva-timeout-error).
+If the Azure Arc resource bridge deployment fails, clean up the installation and retry the deployment.
+
+#### Retry command - Windows
+
+Run the command with ```-Force``` to clean up the installation and onboard again.
+
+```powershell-interactive
+./resource-bridge-onboarding-script.ps1-Force -Subscription <Subscription> -ResourceGroup <ResourceGroup> -AzLocation <AzLocation> -ApplianceName <ApplianceName> -CustomLocationName <CustomLocationName> -vCenterservername <vCenterservername>
+```
+
+#### Retry command - Linux
+
+Run the command with ```--force``` to clean up the installation and onboard again.
+```bash
+bash resource-bridge-onboarding-script.sh --force
+```    
+ 
+While there can be a number of reasons why the Azure Arc resource bridge deployment fails, one of them is KVA timeout error. For more information about the KVA timeout error and how to troubleshoot it, see [KVA timeout error](../resource-bridge/troubleshoot-resource-bridge.md#kva-timeout-error).
 
 > [!IMPORTANT]
 > After the successful installation of Azure Arc resource bridge, it is recommended to retain a copy of the resource bridge config .yaml files and the kubeconfig file safe and secure in a place that facilitates easy retrieval. These files may be needed later to run a few commands to perform management operations on the resource bridge.