Skip to content

Commit 1a8a0d5

Browse files
Merge pull request #299659 from ManoharLakkoju-MSFT/patch-498194
(AzureCXP) fixes MicrosoftDocs/azure-docs#419720
2 parents cd3d594 + 1a54ee3 commit 1a8a0d5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.reviewer: bartpinto
1212

1313
# Best practices for Bare Metal Machine operations
1414

15-
This article provides best practices for BareMetal Machine (BMM) lifecycle management operations.
15+
This article provides best practices for Bare Metal Machine (BMM) lifecycle management operations.
1616
The aim is to highlight common pitfalls and essential prerequisites.
1717

1818
## Read important disclaimers
@@ -76,7 +76,7 @@ Validate that there are no running firmware upgrade jobs through the BMC before
7676
Interrupting an ongoing firmware upgrade can leave the Bare Metal Machine in an inconsistent state.
7777

7878
- You can view in the iDRAC GUI the `jobqueue` or use `run-read-command` `racadm jobqueque view` to determine if there are firmware upgrade jobs running.
79-
- For more information about the `run-read-command` feature, see [BareMetal Run-Read Execution](./howto-baremetal-run-read.md).
79+
- For more information about the `run-read-command` feature, see [Bare Metal Run-Read Execution](./howto-baremetal-run-read.md).
8080

8181
```azurecli
8282
az networkcloud baremetalmachine run-read-command \

0 commit comments

Comments
 (0)