Fix operator typos (#2871)

omni-network · Jan 22, 2025 · 8db842b · 8db842b
1 parent 05338f7
commit 8db842b
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/content/operate/config.md b/docs/content/operate/config.md
@@ -1,7 +1,7 @@
 # Configure a Full Node
 
 This document provides a detailed step-by-step process describing how to manually setup and configure an Omni node.
-It reproduces what the `omni operators init-nodes` command does automatically.
+It reproduces what the `omni operator init-nodes` command does automatically.
 See [Run a Full Node](run-full-node.md) docs for the automated process.
 
 The resulting `~/.omni/<network>` folder has the following structure:

diff --git a/docs/content/operate/validator.md b/docs/content/operate/validator.md
@@ -87,14 +87,14 @@ timeout_commit = "1s"
 > The “halo consensus key” (also known in Cosmos chains as the “[Tendermint/CometBFT consensus key](https://tutorials.cosmos.network/tutorials/9-path-to-prod/3-keys.html#what-validator-keys)”) is used to sign CometBFT blocks on an ongoing basis.
 >
 
-The `omni operators init-nodes` command generates a consensus private key in `~/.omni/omega/halo/config/priv_validator_key.json` .
+The `omni operator init-nodes` command generates a consensus private key in `~/.omni/omega/halo/config/priv_validator_key.json` .
 
 When registering a validator, the associated public key must be provided which will enable this node as a validator.
 
 The public key can be obtained via either of the following commands
 
 ```bash
-# docker compose command in `~/.omni/omega` if `omni init-nodes` was used
+# docker compose command in `~/.omni/omega` if `omni operator init-nodes` was used
 ❯ docker compose run halo run consensus-pubkey
 
 # or
@@ -110,7 +110,7 @@ INF running app args=["consensus-pubkey"] module=cosmovisor path=/halo/cosmoviso
 Consensus public key: 02e47138b658317e8a9ce3fd59c4c41ede153cf2051de3bf9926bd6cfe839512f5
 ```
 
-> Note the `omni operator create-consesus-key` CLI command can also be used to generate a new consensus key and state files.
+> Note the `omni operator create-consensus-key` CLI command can also be used to generate a new consensus key and state files.
 >
 
 **Remember to backup this consensus private key** if you haven’t already.