manual edits

Author: robertstarling

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

@@ -33,7 +33,7 @@ The Cordon action without the `evacuate` parameter isn't considered disruptive w
 [!INCLUDE [important-donot-disrupt-kcpnodes](./includes/baremetal-machines/important-donot-disrupt-kcpnodes.md)]
 
 > [!TIP]
-> In Operator Nexus version 2509.1+ and with API version 2025-07-01-preview or newer, you can monitor recent or in-progress BMM actions in the Azure portal JSON view under `properties.actionStates`. See [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties).
+> In version 2509.1 and above, you can monitor recent or in-progress BMM actions in the Azure portal. For more information, see [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties).
 
 [!INCLUDE [prerequisites-azure-cli-bare-metal-machine-actions](./includes/baremetal-machines/prerequisites-azure-cli-bare-metal-machine-actions.md)]
 

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

@@ -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) as described in [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 from the previous `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 above `run-read-command` in the `actionStates` status field.
 
 ## `Warning: PXE port is unhealthy`
 

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

@@ -34,7 +34,7 @@ The time required to complete each of these actions is similar. Restarting is th
 > This check is done to maintain the integrity of the Nexus instance and ensure multiple KCP nodes don't go down at once due to simultaneous disruptive actions. If multiple nodes go down, it breaks the healthy quorum threshold of the Kubernetes Control Plane.
 
 > [!TIP]
-> In Operator Nexus version 2509.1+ and with API version 2025-07-01-preview or newer, you can monitor recent or in-progress BMM actions (Replace, Reimage, Restart) in the Azure portal JSON view under `properties.actionStates` (status, start/end times, stepStates, and correlationId). See [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties).
+> In version 2509.1 and above, you can monitor recent or in-progress BMM actions in the Azure portal. For more information, see [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties).
 
 ## Identify the corrective action