Skip to content

Commit

Permalink
docs: fix spelling mistake
Browse files Browse the repository at this point in the history
Fix typo

Signed-off-by: Noel Georgi <[email protected]>
  • Loading branch information
martin-sweeny authored and frezbo committed Apr 20, 2022
1 parent c29d464 commit 6092854
Show file tree
Hide file tree
Showing 10 changed files with 10 additions and 10 deletions.
2 changes: 1 addition & 1 deletion website/content/v0.1/Resource Configuration/servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ its exit.

Sidero can use IPMI information to control `Server` power state, reboot servers and set boot order.

IMPI connection information can be set in the `Server` spec after initial registration:
IPMI connection information can be set in the `Server` spec after initial registration:

```yaml
apiVersion: metal.sidero.dev/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.2/Resource Configuration/servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ its exit.

Sidero can use IPMI information to control `Server` power state, reboot servers and set boot order.

IMPI connection information can be set in the `Server` spec after initial registration:
IPMI connection information can be set in the `Server` spec after initial registration:

```yaml
apiVersion: metal.sidero.dev/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.3/Guides/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ Sidero can use IPMI information to control Server power state, reboot servers an
IPMI information will be, by default, setup automatically if possible as part of the acceptance process.
See [IPMI](/docs/v0.3/resource-configuration/servers/#ipmi) for more information.

IMPI connection information can also be set manually in the Server spec after initial registration:
IPMI connection information can also be set manually in the Server spec after initial registration:

```bash
kubectl patch server 00000000-0000-0000-0000-d05099d33360 --type='json' -p='[{"op": "add", "path": "/spec/bmc", "value": {"endpoint": "192.168.88.9", "user": "ADMIN", "pass":"ADMIN"}}]'
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.3/Resource Configuration/servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ In this design, a "sidero" user will be added to the IPMI user list and a random
This information is then squirreled away in a Kubernetes secret in the `sidero-system` namespace, with a name format of `<server-uuid>-bmc`.
Users wishing to turn off this feature can pass the `--auto-bmc-setup=false` flag to `sidero-controller-manager`

IMPI connection information can also be set manually in the `Server` spec after initial registration:
IPMI connection information can also be set manually in the `Server` spec after initial registration:

```yaml
apiVersion: metal.sidero.dev/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.4/Guides/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ Sidero can use IPMI information to control Server power state, reboot servers an
IPMI information will be, by default, setup automatically if possible as part of the acceptance process.
See [IPMI](../../resource-configuration/servers/#ipmi) for more information.
IMPI connection information can also be set manually in the Server spec after initial registration:
IPMI connection information can also be set manually in the Server spec after initial registration:
```bash
kubectl patch server 00000000-0000-0000-0000-d05099d33360 --type='json' -p='[{"op": "add", "path": "/spec/bmc", "value": {"endpoint": "192.168.88.9", "user": "ADMIN", "pass":"ADMIN"}}]'
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.4/Resource Configuration/servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ In this design, a "sidero" user will be added to the IPMI user list and a random
This information is then squirreled away in a Kubernetes secret in the `sidero-system` namespace, with a name format of `<server-uuid>-bmc`.
Users wishing to turn off this feature can pass the `--auto-bmc-setup=false` flag to `sidero-controller-manager`

IMPI connection information can also be set manually in the `Server` spec after initial registration:
IPMI connection information can also be set manually in the `Server` spec after initial registration:

```yaml
apiVersion: metal.sidero.dev/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.5/Guides/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ Sidero can use IPMI information to control Server power state, reboot servers an
IPMI information will be, by default, setup automatically if possible as part of the acceptance process.
See [IPMI](../../resource-configuration/servers/#ipmi) for more information.
IMPI connection information can also be set manually in the Server spec after initial registration:
IPMI connection information can also be set manually in the Server spec after initial registration:
```bash
kubectl patch server 00000000-0000-0000-0000-d05099d33360 --type='json' -p='[{"op": "add", "path": "/spec/bmc", "value": {"endpoint": "192.168.88.9", "user": "ADMIN", "pass":"ADMIN"}}]'
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.5/Resource Configuration/servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ In this design, a "sidero" user will be added to the IPMI user list and a random
This information is then squirreled away in a Kubernetes secret in the `sidero-system` namespace, with a name format of `<server-uuid>-bmc`.
Users wishing to turn off this feature can pass the `--auto-bmc-setup=false` flag to `sidero-controller-manager`

IMPI connection information can also be set manually in the `Server` spec after initial registration:
IPMI connection information can also be set manually in the `Server` spec after initial registration:

```yaml
apiVersion: metal.sidero.dev/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.6/Guides/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ Sidero can use IPMI information to control Server power state, reboot servers an
IPMI information will be, by default, setup automatically if possible as part of the acceptance process.
See [IPMI](../../resource-configuration/servers/#ipmi) for more information.
IMPI connection information can also be set manually in the Server spec after initial registration:
IPMI connection information can also be set manually in the Server spec after initial registration:
```bash
kubectl patch server 00000000-0000-0000-0000-d05099d33360 --type='json' -p='[{"op": "add", "path": "/spec/bmc", "value": {"endpoint": "192.168.88.9", "user": "ADMIN", "pass":"ADMIN"}}]'
Expand Down
2 changes: 1 addition & 1 deletion website/content/v0.6/Resource Configuration/servers.md
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ In this design, a "sidero" user will be added to the IPMI user list and a random
This information is then squirreled away in a Kubernetes secret in the `sidero-system` namespace, with a name format of `<server-uuid>-bmc`.
Users wishing to turn off this feature can pass the `--auto-bmc-setup=false` flag to `sidero-controller-manager`

IMPI connection information can also be set manually in the `Server` spec after initial registration:
IPMI connection information can also be set manually in the `Server` spec after initial registration:

```yaml
apiVersion: metal.sidero.dev/v1alpha2
Expand Down

0 comments on commit 6092854

Please sign in to comment.