syntax edit and spellcheck

documentation/operators/src/nodes/bonding.md

@@ -14,7 +14,7 @@ You are asked to `sign` a transaction and bpnd your node to Nyx blockchain so th
 2. [Configure VPS](vps-setup.md) correctly
 3. [Prepare Nym wallet](wallet-preparation.md)
 4. [Setup & Run](setup.md) the node
-5. (Optional but reccomended) [Configure](configuration.md) the node (WSS, reversed proxy, automation)
+5. [Configure](configuration.md) the node (Optionally setup automation, WSS, reversed proxy)
 
 ```admonish warning
 Do not bond your node to the API if the previous steps weren't finished. Bad connectivity, closed ports, or other poor setup will result in your node getting blacklisted.
@@ -63,5 +63,6 @@ It will look something like this:
 If everything worked, you'll see your node running on the either the [Sandbox testnet network explorer](https://sandbox-explorer.nymtech.net) or the [mainnet network explorer](https://explorer.nymtech.net), depending on which network you're running.
 
 
-### Bond via the CLI (power users)
+## Bond via the CLI (power users)
+
 If you want to bond your Mix Node via the CLI, then check out the [relevant section in the Nym CLI](https://nymtech.net/docs/tools/nym-cli.html#bond-a-mix-node) docs.

documentation/operators/src/nodes/nym-node.md

@@ -16,15 +16,17 @@ To setup any type of Nym Node, start with either building [Nym's platform](../bi
 
 Once VPS and Nym wallet are configured, binaries ready, the operators of `nym-node` need to:
 
-#### 1. [Setup & Run](setup.md) the node
-#### 2. [Configure](configuration.md) the node (and optionaly WSS, reversed proxy, automation)
-#### 3. [Bond](bonding.md) the node to the Nym API, using Nym wallet
+1. **[Setup & Run](setup.md) the node**
+
+2. **[Configure](configuration.md) the node** (and optionally WSS, reversed proxy, automation)
+
+3. **[Bond](bonding.md) the node to the Nym API, using Nym wallet**
 
 ## Quick `nym-node --mode exit-gateway` Setup
 
 During our ongoing testing events [Fast and Furious](https://nymtech.net/events/fast-and-furious) we found out, that after introducing IP Packet Router and [Nym exit policy](https://nymtech.net/.wellknown/network-requester/exit-policy.txt) by default,  only a fragment of Gateways routes correctly through IPv4 and IPv6. We built a useful monitor to check out your Gateway (`nym-node --mode exit-gateway`) at [harbourmaster.nymtech.net](https://harbourmaster.nymtech.net/).
 
-Below is a fast - ten commands - deployment to get and setup your node, configure networking and connectivity and verify that it all works as it should by getting two free jokes through the mixnet.
+Below is a fast - ten commands - deployment to get and setup your node, configure networking and connectivity and verify that it all works as it should by getting two free jokes through the Mixnet.
 
 ```admonish caution
 If you are not well familiar with `nym-node` setup, automation, and `nymtun0` configuration, follow the [steps above](#steps-for-nym-node-operators) page by page. You can use this flow as a reference later on.

documentation/operators/src/nodes/setup.md

@@ -166,7 +166,7 @@ Run the node with custom `--id` without initialising:
 ### Migrate
 
 ```admonish caution
-Migration is a must for all deprecated nodes (`nym-mixnode`, `nym-gateway`). For backward compatibility we created an [archive section](../archive/setup-guides.md) with all the guides for individual binaries. However, the binaries from version 1.1.35 (`nym-gateway`) and 1.1.37 (`nym-mixnode`) onwards will no have init command.
+Migration is a must for all deprecated nodes (`nym-mixnode`, `nym-gateway`). For backward compatibility we created an [archive section](../archive/setup-guides.md) with all the guides for individual binaries. However, the binaries from version 1.1.35 (`nym-gateway`) and 1.1.37 (`nym-mixnode`) onwards will no longer have `init` command.
 ```
 
 To migrate a `nym-mixnode` or a `nym-gateway` to `nym-node` is fairly simple, use the `migrate` command with `--config-file` flag pointing to the original `config.toml` file, with a conditional argument defining which type of node this configuration belongs to. Examples are below.

documentation/operators/src/nodes/vps-setup.md

@@ -85,7 +85,7 @@ sudo ufw allow 1789,1790,8000,9000,9001,22/tcp
 # in case of planning to setup a WSS (for Gateway functionality)
 sudo ufw allow 9001/tcp
 
-# inn case of reverse proxy for the swagger page (for Gateway optionality)
+# in case of reverse proxy for the swagger page (for Gateway optionality)
 sudo ufw allow 8080,80,443
 
 # for validator