Review and linting fixes

Author: pjw711

articles/operator-nexus/concepts-storage-virtual-machine.md

@@ -24,7 +24,7 @@ Azure Operator Nexus supports deploying VM OS disks on either local or persisten
 
 VMs with persistent OS disks are migrated to a suitable BMM when their host BMM is stopped. See [here](#disk-migration-on-bmm-shutdown) for further information. There's no support for migration of VMs with local OS disks under any circumstances.
 
-## Data Disks
+## Data disks
 
 Azure Operator Nexus supports the following persistent data disk features.
 
@@ -42,7 +42,7 @@ Azure Operator Nexus supports the following persistent data disk features.
 | Migration of data disks from an unexpected BMM hardware failure | Not supported                                     |
 | Live VM migration                                  | Not supported                                        |
 
-## Disk Migration on BMM shutdown
+## Disk migration on BMM shutdown
 
 Azure Operator Nexus supports migration of a VM with persistent disks from a stopped BMM to a suitable alternative BMM. However, there are some restrictions and limitations to this functionality.
 

articles/operator-nexus/howto-deploy-data-disk-bicep.md

@@ -35,27 +35,21 @@ Once you have reviewed and saved the template file named ```data-disk-bicep-temp
 
 ## Review the deployed resources
 
-After the deployment finishes, you can view the resources using the CLI or the Azure portal.
+After the deployment finishes, you can view the resources using the CLI.
 
 To view the details of the ```myDataDisk``` volume in the ```myResourceGroup``` resource group, execute the following
 
-### [Azure CLI](#tab/azure-cli)
-
 ```azurecli-interactive
 az networkcloud volume show --name myDataDisk --resource-group myResourceGroup
 ```
 
----
-
 ## Delete the deployed resources
 
 You can delete the data disk using the Azure CLI.
 
 > [!IMPORTANT]
 > Deleting a data disk removes the backing volume from the storage appliance. Any data stored on that volume is lost unless you have a backup. You can't delete a data disk which is attached to a VM. If your disk has previously been attached to a VM, don't delete it unless you're certain you don't need the data!
 
-### [Azure CLI](#tab/azure-cli)
-
 ```azurecli-interactive
 az networkcloud volume delete --name myDataDisk --resource-group myResourceGroup
 ```

articles/operator-nexus/howto-deploy-persistent-vm-bicep.md

@@ -39,27 +39,21 @@ Once you have reviewed and saved the template file named ```virtual-machine-bice
 
 ## Review the deployed resources
 
-After the deployment finishes, you can view the resources using the CLI or the Azure portal.
+After the deployment finishes, you can view the resources using the CLI.
 
 To view the details of the ```myNexusVirtualMachine``` VM in the ```myResourceGroup``` resource group, execute the following
 
-### [Azure CLI](#tab/azure-cli)
-
 ```azurecli-interactive
 az networkcloud virtualmachine show --name myNexusVirtualMachine --resource-group myResourceGroup
 ```
 
----
-
 ## Delete the deployed resources
 
 You can delete the virtual machine using the Azure CLI.
 
 > [!IMPORTANT]
 > The OS disk is deleted when you delete the VM. Data disks aren't deleted when you delete a VM. You can delete the data disks using the Azure CLI to delete the Volume (Operator Nexus) resource. Deleting a data disk removes the backing volume from the storage appliance. Any data stored on that volume will be lost unless you have a backup. You can't delete a data disk which is attached to a VM. If your disk was attached to a VM, don't delete it unless you're certain you don't need the data!
 
-### [Azure CLI](#tab/azure-cli)
-
 ```azurecli-interactive
 az networkcloud virtualmachine delete --name myNexusVirtualMachine --resource-group myResourceGroup
 ```

articles/operator-nexus/howto-platform-prerequisites.md

@@ -67,8 +67,7 @@ ordering errors because of complex parts lists.
 
 #### Placing a SKU-based order
 
-Operator Nexus has created a series of SKUs with vendors such as Dell, Pure
-Storage and Arista that the operator can reference when they place
+Operator Nexus has created a series of SKUs with vendors such as Dell, Pure Storage, and Arista that the operator can reference when they place
 an order. Thus, an operator simply needs to place an order based on the SKU
 information provided by Operator Nexus to the vendor to receive the correct
 parts list for the build.
@@ -140,14 +139,15 @@ Now that the physical installation and validation has completed, the next steps
 > This guide has been validated with Opengear firmware version 24.11.2, which was upgraded from version 22.06.0, and is supported with Nexus Network Fabric runtime version 5.0.0.
 
 Terminal Server has been deployed and configured as follows:
-  - Terminal Server is configured for Out-of-Band management
-    - Authentication credentials have been set up
-    - DHCP client is enabled on the out-of-band management port
-    - HTTP access is enabled
-  - Terminal Server interface is connected to the operators on-premises Provider Edge routers (PEs) and configured with the IP addresses and credentials
-  - Terminal Server is accessible from the management VPN
-  - To upgrade the terminal server to OS version 24.11.2 [refer](./howto-upgrade-os-of-terminal-server.md)
-  - To setup single session and session timeout for serial console [refer](./howto-restrict-serial-port-access-and-set-timeout-on-terminal-server.md)
+
+- Terminal Server is configured for Out-of-Band management
+  - Authentication credentials have been set up
+  - DHCP client is enabled on the out-of-band management port
+  - HTTP access is enabled
+- Terminal Server interface is connected to the operators on-premises Provider Edge routers (PEs) and configured with the IP addresses and credentials
+- Terminal Server is accessible from the management VPN
+- To upgrade the terminal server to OS version 24.11.2 [refer](./howto-upgrade-os-of-terminal-server.md)
+- To setup single session and session timeout for serial console [refer](./howto-restrict-serial-port-access-and-set-timeout-on-terminal-server.md)
 
 ### Step 1: Setting up hostname
 
@@ -532,7 +532,7 @@ Interface:    net1, via: LLDP, RID: 1, Time: 0 day, 20:28:36
      - `puretune -set PS_RDMA_STALE_OP_THRESH_MS 5000 "PURE-209441";`
      - `puretune -set PS_BDRV_REQ_MAXBUFS 128 "PURE-209441";`
 
-## [Optional] Set up second storage array
+## (Optional) Set up second storage array
 
 >[!NOTE]
 > This section is optional. You only need to execute it if you are deploying an Azure Operator Nexus instance with two storage appliances. For more information, including restrictions on supported hardware, see [Azure Operator Nexus multiple storage appliances](./concepts-storage-multiple-appliances.md).