tweak copilot edits

Author: robertstarling

articles/operator-nexus/concepts-compute.md

@@ -110,9 +110,6 @@ The following properties reflect the operational state of a BMM:
 > [!NOTE]
 > Customers can't create or delete BMMs directly. These machines are created only as the realization of the cluster lifecycle. Implementation blocks creation or deletion requests from any user, and it allows only internal/application-driven creation or deletion operations.
 
-> [!TIP]
-> For recent or in-progress lifecycle actions (Replace, Reimage, Restart), the Azure portal JSON view shows `properties.actionStates` with action status, times, stepStates, and correlationId (requires Operator Nexus 2509.1+ and API 2025-07-01-preview+). See [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties).
-
 ## Form-factor-specific information
 
 Azure Operator Nexus offers a group of on-premises cloud solutions that cater to both [near-edge](reference-near-edge-compute.md) and far-edge environments.

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

@@ -16,9 +16,6 @@ These steps should be used for troubleshooting purposes to recover from failures
 
 First, read the advice in the article [Best Practices for Bare Metal Machine Operations](./howto-bare-metal-best-practices.md) before proceeding with operations.
 
-> [!NOTE]
-> 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).
-
 The bolded actions listed are considered disruptive (Power off, Restart, Reimage, Replace).
 The Cordon action without the `evacuate` parameter isn't considered disruptive while Cordon with the `evacuate` parameter is considered disruptive.
 
@@ -35,6 +32,9 @@ 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).
+
 [!INCLUDE [prerequisites-azure-cli-bare-metal-machine-actions](./includes/baremetal-machines/prerequisites-azure-cli-bare-metal-machine-actions.md)]
 
 ## Power off a Bare Metal Machine

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

@@ -104,9 +104,6 @@ To show details and the status of a single Bare Metal Machine:
 az networkcloud baremetalmachine show -g $CLUSTER_MRG -n $BMM_NAME
 ```
 
-> [!TIP]
-> If you’ve initiated any BMM lifecycle action (all action types, for example Replace, Reimage, Restart), you can monitor the action’s progress in the Azure portal JSON view under `properties.actionStates` (version 2509.1+ and API 2025-07-01-preview+ required). See [Monitor status in Bare Metal Machine JSON properties](./howto-bare-metal-best-practices.md#monitor-status-in-bare-metal-machine-json-properties).
-
 For Bare Metal Machine details specific to troubleshooting:
 
 ```azurecli

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

@@ -26,16 +26,16 @@ The time required to complete each of these actions is similar. Restarting is th
   - Name of the BMM that requires a lifecycle management operation
   - Subscription ID
 
-> [!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).
-
 > [!IMPORTANT]
 > Disruptive command requests against a Kubernetes Control Plane (KCP) node are rejected if there's another disruptive action command already running against another KCP node or if the full KCP isn't available.
 >
 > Restart, reimage and replace are all considered disruptive actions.
 >
 > 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).
+
 ## Identify the corrective action
 
 When troubleshooting a BMM for failures and determining the most appropriate corrective action, it's essential to understand the available options. This article provides a systematic approach to troubleshoot Azure Operator Nexus server problems using these three methods: