Acrolinx fixes

Author: robertstarling

articles/operator-nexus/howto-bare-metal-best-practices.md

@@ -67,7 +67,7 @@ See related articles:
 - [How to monitor interface In and Out packet rate for network fabric devices]
 - [How to configure diagnostic settings and monitor configuration differences in Nexus Network Fabric].
 
-Evaluate for any Bare Metal Machine warnings or degraded conditions which could indicate the need to resolve hardware, network, or server configuration problems.
+Evaluate for any Bare Metal Machine warnings or degraded conditions that could indicate the need to resolve hardware, network, or server configuration problems.
 For more information, see [Troubleshoot Degraded Status Errors on Bare Metal Machines] and [Troubleshoot Bare Metal Machine Warning Status].
 
 #### Determine if firmware update jobs are running
@@ -88,7 +88,7 @@ az networkcloud baremetalmachine run-read-command \
   --output-directory .
 ```
 
-Here's an example output from the `racadm jobqueue view` command which shows `Firmware Update`.
+Here's an example output from the `racadm jobqueue view` command that shows `Firmware Update`.
 
 ```
 [Job ID=JID_833540920066]
@@ -127,15 +127,15 @@ Percent Complete=[100]
 
 #### Monitor status in Bare Metal Machine JSON properties
 
-In version 2509.1 and above, you can view the status of any recent or in progress actions in the `JSON View` of the corresponding Bare Metal Machine (Operator Nexus) resource. This shows the following information in the Bare Metal Machine JSON properties, when using API Version `2025-07-01-preview` or higher.
+In version 2509.1 and above, you can view the status of any recent or in progress actions in the `JSON View` of the corresponding Bare Metal Machine (Operator Nexus) resource. This view shows the following information in the Bare Metal Machine JSON properties, when using API Version `2025-07-01-preview` or higher.
 
 - Start and end time of the action.
-- Status of the action (e.g., `Succeeded`, `Failed`, `InProgress`).
-- Any additional context or error message associated with the status.
+- Status of the action (`Succeeded`, `Failed`, or `InProgress`).
+- Any extra context or error message associated with the status.
 - The Correlation ID for the original action request, as shown in the Azure Activity Log for the resource.
-- The detailed steps included in the action, such as `Hardware Validation`, `Deprovisioning`, `Provisioning` and `Cloud Init` for a BMM Replace action.
+- The detailed steps included in the action, such as `Hardware Validation`, `Deprovisioning`, `Provisioning`, and `Cloud Init` for a BMM Replace action.
 
-The most recent (or currently in progress) occurrence of each action type is shown (Replace, Reimage, Restart etc).
+The most recent occurrence of each action type is shown, including any currently in-progress action.
 
 Example output for a Replace action:
 
@@ -202,7 +202,7 @@ Before initiating any `reimage` operation, ensure the following preconditions ar
 
 - Make sure the Bare Metal Machine's workloads are drained using the [`cordon`](./howto-baremetal-functions.md#make-a-bare-metal-machine-unschedulable-cordon) command with the parameter `evacuate` set to `True`.
 - Perform high level checks covered in the article [Troubleshoot Bare Metal Machine Provisioning].
-- Evaluate any Bare Metal Machine warnings or degraded conditions which could indicate the need to resolve hardware, network, or server configuration problems before a `reimage` operation.
+- Evaluate any Bare Metal Machine warnings or degraded conditions that could indicate the need to resolve hardware, network, or server configuration problems before a `reimage` operation.
   For more information, read [Troubleshoot Degraded Status Errors on Bare Metal Machines] and [Troubleshoot Bare Metal Machine Warning Status].
 - If the Bare Metal Machine reports a failed state with the reason of hardware validation (seen in the Bare Metal Machine `Detailed Status` and `Detailed Status Message` fields), then the Bare Metal Machine needs a `replace` instead.
   See the [Best Practices for a Bare Metal Machine Replace](#best-practices-for-a-bare-metal-machine-replace).
@@ -230,7 +230,7 @@ Before initiating any `replace` operation, ensure the following preconditions ar
 
 - Make sure the Bare Metal Machine's workloads are drained using the [`cordon`](./howto-baremetal-functions.md#make-a-bare-metal-machine-unschedulable-cordon) command with the parameter `evacuate` set to `True`.
 - Perform high level checks covered in the article [Troubleshoot Bare Metal Machine Provisioning].
-- Evaluate any Bare Metal Machine warnings or degraded conditions which could indicate the need to resolve hardware, network, or server configuration problems before a `replace` operation.
+- Evaluate any Bare Metal Machine warnings or degraded conditions that could indicate the need to resolve hardware, network, or server configuration problems before a `replace` operation.
   For more information, see [Troubleshoot Degraded Status Errors on Bare Metal Machines] and [Troubleshoot Bare Metal Machine Warning Status].
 - Validate Bare Metal Machine is powered on.
 - Validate that there are no running firmware upgrade jobs.

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

@@ -85,7 +85,7 @@ Existing workloads continue to run on the Bare Metal Machine unless the workload
 
 ### Drain Bare Metal Machine workloads
 
-The cordon command supports the `evacuate` parameter which its default value `False` means that the `cordon` command prevents scheduling new workloads.
+The cordon command supports the `evacuate` parameter, for which its default value `False` means that the `cordon` command prevents scheduling new workloads.
 To drain workloads with the `cordon` command, the `evacuate` parameter must be set to `True`.
 The workloads running on the Bare Metal Machine are `stopped` and the Bare Metal Machine is set to `pending` state.
 
@@ -176,7 +176,7 @@ az networkcloud baremetalmachine replace \
 
 If the `replace` action fails due to a hardware validation failure, the specific error or test failure is shown in the `replace` response, as shown in the following examples.
 This information can also be found in the Activity Log for the Bare Metal Machine (Operator Nexus).
-The error code and error message are included the JSON properties of the corresponding `BareMetalMachines_Replace` operation.
+The error code and error message are also included in the JSON properties of the corresponding `BareMetalMachines_Replace` operation.
 
 **Example 1: Hardware validation fails due to invalid Key Vault URI for Baseboard Management Controller (BMC) credentials**
 

articles/operator-nexus/troubleshoot-bare-metal-machine-warning.md

@@ -12,7 +12,7 @@ ms.reviewer: ekarandjeff
 
 # Troubleshoot _'Warning'_ detailed status messages on an Azure Operator Nexus Cluster Bare Metal Machine
 
-This document provides basic troubleshooting information for Bare Metal Machine (BMM) resources which are reporting a _Warning_ message in the BMM detailed status message.
+This document provides basic troubleshooting information for Bare Metal Machine (BMM) resources that are reporting a _Warning_ message in the BMM detailed status message.
 
 ## Symptoms
 
@@ -92,7 +92,7 @@ Review the `lastTransitionTime` and `message` fields for more information about
 }
 ```
 
-You can also check for any potentially related recent lifecycle actions (such as Restart or Power off actions) in the Azure portal. See [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties). If available, this information is also visible in the output of the above `run-read-command` in the `actionStates` status field.
+You can also check for any potentially related recent lifecycle actions (such as Restart or Power off actions) in the Azure portal. See [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties). If available, this information is also visible in the output of the previous `run-read-command` in the `actionStates` status field.
 
 ## `Warning: PXE port is unhealthy`
 
@@ -116,8 +116,8 @@ To troubleshoot this issue:
 - review the `conditions` status of the kubernetes `bmm` object, as described in the [Troubleshooting](#troubleshooting) section
 - this information should identify the specific root cause (port down or port flapping) and approximate time of the issue
 - check the Ethernet cabling and Top Of Rack (TOR) switch for the affected PXE port
-- check for any other BMMs which are also reporting unhealthy PXE status or other network-related problems
-- check for any recent deployment or infrastructure changes which coincide with the time of failure.
+- check for any other BMMs that are also reporting unhealthy PXE status or other network-related problems
+- check for any recent deployment or infrastructure changes that coincide with the time of failure.
 
 **Example `conditions` output for PXE warning**
 
@@ -145,11 +145,11 @@ This message can indicate an issue with the underlying compute host or baseboard
 To troubleshoot this issue:
 
 - review the `conditions` status of the kubernetes `bmm` object, as described in the [Troubleshooting](#troubleshooting) section
-- review the `actionStates` status field of the kubernetes `bmm` object for any recently initiated lifecycle actions (e.g. Restart or Power off) as described in the [Troubleshooting](#troubleshooting) section
+- review the `actionStates` status field of the kubernetes `bmm` object for any recently initiated lifecycle actions (such as a Restart or Power off) as described in the [Troubleshooting](#troubleshooting) section
 - this information should identify the approximate time of the issue and any other available details
 - check the power feed, power cables, and physical hardware for the specified BMM
 - check whether any other BMMs are also reporting an unexpected power state Warning, which might indicate a broader issue with the underlying infrastructure
-- check for any recent deployment or infrastructure changes which coincide with the time of failure
+- check for any recent deployment or infrastructure changes that coincide with the time of failure
 - review the power state and logs on the BMC for the affected host.
 
 For more information about logging into the BMC, see [Troubleshoot Hardware Validation Failure](./troubleshoot-hardware-validation-failure.md).

articles/operator-nexus/troubleshoot-reboot-reimage-replace.md

@@ -180,7 +180,7 @@ Servers contain many physical components that can fail over time. It's important
 A hardware validation process is invoked to ensure the integrity of the physical host in advance of deploying the OS image. Like the reimage action, the Tenant data isn't modified during replacement.
 
 > [!IMPORTANT]
-> When run with default options, the RAID controller is reset during BMM replace, wiping all data from the server's virtual disks. Baseboard Management Controller (BMC) virtual disk alerts triggered during BMM replace can be ignored unless there are other physical disk and/or RAID controllers alerts. Starting with the 2025-07-01 preview version of the NetworkCloud API, and generally available with the 2025-09-01 GA version, use `replace` with `storage-policy="Preserve"` to retain virtual disk data.
+> When run with default options, the RAID controller is reset during BMM replace, wiping all data from the server's virtual disks. Baseboard Management Controller (BMC) virtual disk alerts triggered during BMM replace can be ignored unless there are other physical disk and/or RAID controllers alerts. Starting with the `2025-07-01-preview` version of the NetworkCloud API, and generally available with the `2025-09-01` GA version, use `replace` with `storage-policy="Preserve"` to retain virtual disk data.
 
 ### Replace workflow