[doc] PR for Remove reference to portal.dev from public docs

docs/content/preview/yugabyte-platform/manage-deployments/high-availability.md

@@ -79,7 +79,7 @@ Once the active instance has been configured, you can configure one or more stan
 
 1. Paste the shared authentication key from the active instance into the **Shared Authentication Key** field.
 
-1. Switch to the active instance and then switch to **Instance Configuration**. Click **Add Instance**, enter the new standby instance's IP address or hostname, including the HTTP or HTTPS protocol prefix and port if you are not using the default of 80 or 443, and then click **Continue** on the **Add Standby Instance** dialog.
+1. Switch to the active instance, and then switch to **Instance Configuration**. Click **Add Instance**, enter the new standby instance's IP address or hostname, including the HTTP or HTTPS protocol prefix and port if you are not using the default of 80 or 443, and then click **Continue** on the **Add Standby Instance** dialog.
 
 1. Switch back to the new standby instance, wait for a replication interval to pass, and then refresh the page. The other instances in the high-availability cluster should now appear in the list of instances.
 
@@ -93,11 +93,9 @@ You can make a standby instance active as follows:
 
 1. Use the **Make Active** dialog to select the backup from which you want to restore (in most cases, you should choose the most recent backup in the vast majority of cases) and enable **Confirm promotion**.
 
-1. Click **Continue**.
-
-    \
-    The restore take a few seconds, after which expect to be logged out.
-
+1. Click **Continue**.<br>
+The restore take a few seconds, after which expect to be logged out.
+
 1. Login using credentials that you had configured on the previously active instance.
 
 You should be able to see that all of the data has been restored into the instance, including universes, users, metrics, alerts, task history, cloud providers, and so on.