Merge pull request #229523 from JAC0BSMITH/Nexus_Deploy_Restructure_0303

content and format fix for BMM

Author: prmerger-automator[bot]

articles/operator-nexus/howto-baremetal-functions.md

@@ -5,7 +5,7 @@ author: harish6724
 ms.author: harishrao
 ms.service: azure 
 ms.topic: how-to
-ms.date: 02/01/2023
+ms.date: 03/06/2023
 ms.custom: template-how-to
 ---
 
@@ -22,7 +22,7 @@ This article describes how to perform lifecycle management operations on Bare Me
 
 1. Install the latest version of the
   [appropriate CLI extensions](./howto-install-cli-extensions.md)
-1. Ensure that the target bare metal machine (server) must be `powered-on` and have its `readyState` set to True
+1. Ensure that the target bare metal machine (server) must have its `poweredState` set to `On` and have its `readyState` set to `True`
 1. Get the Resource group name that you created for `network cloud cluster resource`
 
 ## Power-off bare metal machines
@@ -49,8 +49,8 @@ You can make a BMM unschedulable by executing the [`cordon`](#make-a-bmm-unsched
 On the execution of the `cordon` command,
 Operator Nexus workloads are not scheduled on the BMM when cordon is set; any attempt to create a workload on a `cordoned`
 BMM results in the workload being set to `pending` state. Existing workloads continue to run.
-The cordon command supports an `evacuate` parameter with the default `false` value.
-On executing the `cordon` command, with the value `true` for the `evacuate`
+The cordon command supports an `evacuate` parameter with the default `False` value.
+On executing the `cordon` command, with the value `True` for the `evacuate`
 parameter, the workloads that are running on the BMM are `stopped` and the BMM is set to `pending` state.
 
 ```azurecli
@@ -60,7 +60,7 @@ parameter, the workloads that are running on the BMM are `stopped` and the BMM i
     --resource-group "resourceGroupName"
 ```
 
-The `evacuate "True"` removes workloads from that node while `evacuate "FALSE"` only prevents the scheduling of new workloads.
+The `evacuate "True"` removes workloads from that node while `evacuate "False"` only prevents the scheduling of new workloads.
 
 ## Make a BMM schedulable (uncordon)
 
@@ -77,7 +77,7 @@ state on the BMM are `restarted` when the BMM is `uncordoned`.
 
 The existing BMM image can be **reinstalled** using the `reimage` command but will not install a new image.
 Make sure the BMM's workloads are drained using the [`cordon`](#make-a-bmm-unschedulable-cordon)
-command, with `evacuate "TRUE"`, prior to executing the `reimage` command.
+command, with `evacuate "True"`, prior to executing the `reimage` command.
 
 ```azurecli
 az networkcloud baremetalmachine reimage –-name "bareMetalMachineName"  \