Skip to content

Commit 0d66181

Browse files
author
Dan Crank
committed
reduce document to an Acrolinx reading level
1 parent 4764077 commit 0d66181

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ run simple actions on bare metal machines without using the Azure console or com
2424
2525
## Prerequisites
2626

27-
1. Create a [BareMetalMachineKeySet](./howto-baremetal-bmm-ssh.md) to allow ssh access to the bare metal machines. The user must have superuser privilege level.
27+
1. A [BareMetalMachineKeySet](./howto-baremetal-bmm-ssh.md) must be available to allow ssh access to the bare metal machines. The user must have superuser privilege level.
2828
1. The platform Kubernetes must be up and running on site.
2929

3030
## Overview
@@ -69,7 +69,7 @@ The status is blank until the operation completes and reaches either a "succeede
6969

7070
## Start a bare metal machine
7171

72-
A single bare metal machine can be started from a power-off state by connecting to a control-plane or management-plane node via ssh and running the command:
72+
A single bare metal machine can be started by connecting to a control-plane or management-plane node via ssh and running the command:
7373

7474
```
7575
sudo nc-toolbox nc-toolbox-breakglass nexusctl baremetal start --name <machine name>
@@ -85,19 +85,19 @@ The status is blank until the operation completes and reaches either a "succeede
8585

8686
## Unmanage a bare metal machine (set to unmanaged state)
8787

88-
A single bare metal machine can be moved from a managed state to an unmanaged state by connecting to a control-plane or management-plane node via ssh and running the command:
88+
A single bare metal machine can be switched to an unmanaged state by connecting to a control-plane or management-plane node via ssh and running the command:
8989

9090
```
9191
sudo nc-toolbox nc-toolbox-breakglass nexusctl baremetal unmanage --name <machine name>
9292
```
9393

94-
While in an unmanaged state, no actions are permitted for that machine, except for returning it to a managed state (see next section). This can be used to keep a bare metal machine powered off in the instance it's caught in a rebooting crash loop.
94+
While in an unmanaged state, no actions are permitted for that machine, except for returning it to a managed state (see next section). This function can be used to keep a bare metal machine powered off if it's in a rebooting crash loop.
9595

9696
`unmanage` isn't a long-running command, so there's no associated command to check operation status.
9797

9898
## Manage a bare metal machine (set to managed state)
9999

100-
A single bare metal machine can be moved from an unmanaged state to a managed state by connecting to a control-plane or management-plane node via ssh and running the command:
100+
A single bare metal machine can be switched to a managed state by connecting to a control-plane or management-plane node via ssh and running the command:
101101

102102
```
103103
sudo nc-toolbox nc-toolbox-breakglass nexusctl baremetal manage --name <machine name>

0 commit comments

Comments
 (0)