Updated text

Author: ronmiab

azure-local/manage/disconnected-operations-deploy.md

@@ -105,8 +105,8 @@ To prepare each machine for the disconnected operations appliance, follow these
 
 1. [Rename each node](/powershell/module/microsoft.powershell.management/rename-computer?view=powershell-7.4&preserve-view=true) according to your environments naming conventions. For example, azlocal-n1, azlocal-n2, and azlocal-n3.  
 
- 1. Check and make sure you have sufficient disk space for disconnected operations deployment.
- 
+1. Check and make sure you have sufficient disk space for disconnected operations deployment.
+
     Make sure you have at least 600 GB of free space on the drive you plan to use for deployment. If your drive has less space, use a data disk on each node and initialize it so each node has the same available data disks for deployment.
 
     Here’s how to initialize a disk on the nodes and format it for a D partition: 
@@ -145,11 +145,10 @@ To prepare each machine for the disconnected operations appliance, follow these
     > [!NOTE]
     > If you use a different root for the management certificate, repeat the process and import the key on each node.
 
-
 1. [Install and configure the CLI](disconnected-operations-cli.md) with your local endpoint on each node.
-   
+
 1. Set the environment variable to support disconnected operations
-   
+
     ```powershell
     [Environment]::SetEnvironmentVariable("DISCONNECTED_OPS_SUPPORT", $true, [System.EnvironmentVariableTarget]::Machine)
     ```
@@ -330,7 +329,6 @@ Populate the required parameters based on your deployment planning. Modify the e
     copy-item AzureLocal.DisconnectedOperations.Manifest.json $applianceConfigBasePath\AzureLocal.DisconnectedOperations.Appliance.manifest.json
     ```  
 
-
 ## Install and configure the appliance  
 
 To install and configure the appliance on the first machine (seed node), use the following command. Point the `AzureLocalInstallationFile` to a path that contains the **IRVM01.zip**.
@@ -455,10 +453,10 @@ Wait until all resource providers are in the state **Registered**. Here's a samp
 
 ```azurecli  
     az provider list -o table
-``` 
+```
 
-> [!NOTE] 
-> You can also register or view resource provider statuses in the local portal. To do this, go to your **Subscription**, click the dropdown arrow for **Settings**, and select **Resource providers**. 
+> [!NOTE]
+> You can also register or view resource provider statuses in the local portal. To do this, go to your **Subscription**, click the dropdown arrow for **Settings**, and select **Resource providers**.
 
 ### Create resource group SPN for cluster  
 
@@ -494,7 +492,6 @@ Use the operator account to create an SPN for Arc initialization of each Azure L
     >
     > Don't place the cluster resource in the operator subscription, unless you plan to restrict this to only operators with full access to other operations. You can create more subscriptions or place it in the starter subscription.
 
-
 ### Initialize each node
 
 To initialize each node, follow these steps. Modify where necessary to match your environment details: