diff --git a/documentation/operators/src/faq.md b/documentation/operators/src/faq.md
index 5e1f5b72ad..e09a78c21c 100644
--- a/documentation/operators/src/faq.md
+++ b/documentation/operators/src/faq.md
@@ -10,5 +10,7 @@ Hi, do you know if it's on the roadmap for network nodes (requesters, socks5 cli
 
 you should be able to switch gateway (and overwrite keys) using —force-register
 
+make a note that the keys will be overwritten in bold when you're noting it in the operators guides
+
 
 ---> 
diff --git a/documentation/operators/src/nodes/gateway-setup.md b/documentation/operators/src/nodes/gateway-setup.md
index 591cd3d1a9..ecd04d1005 100644
--- a/documentation/operators/src/nodes/gateway-setup.md
+++ b/documentation/operators/src/nodes/gateway-setup.md
@@ -1,3 +1,7 @@
+<!---
+TODO
+- [ ] Move ## VPS Setup and Automation to ./maintenance.md and merge it with mixnode and NR automation setup.
+--->
 # Gateways
 
 > The Nym gateway was built in the [building nym](../binaries/building-nym.md) section. If you haven't yet built Nym and want to run the code, go there first.
@@ -153,9 +157,11 @@ You can either do this graphically via the Desktop Wallet, or the CLI.
 
 #### Updating node information via the Desktop Wallet
 * Navigate to the `Bonding` page and click the `Node Settings` link in the top right corner:
+/
 ![Bonding page](../images/wallet-screenshots/bonding.png)
 
 * Update the fields in the `Node Settings` page and click `Submit changes to the blockchain`.
+/
 ![Node Settings Page](../images/wallet-screenshots/node_settings.png)
 
 #### Updating node information via the CLI
@@ -244,7 +250,7 @@ This lets your operating system know it's ok to reload the service configuration
 Numerous gateway related API endpoints are documented on the Validator API's [Swagger Documentation](https://validator.nymtech.net/api/swagger/index.html). There you can also try out various requests from your broswer, and download the response from the API. Swagger will also show you what commands it is running, so that you can run these from an app or from your CLI if you prefer.
 
 ## Ports
-All gateway specific port configuration can be found in `$HOME/.nym/gateways/<your-id>/config/config.toml`. If you do edit any port configs, remember to restart your gateway.
+All gateway specific port configuration can be found in `$HOME/.nym/gateways/<YOUR_ID>/config/config.toml`. If you do edit any port configs, remember to restart your gateway.
 
 ### Gateway port reference
 | Default port | Use                       |
diff --git a/documentation/operators/src/nodes/mix-node-setup.md b/documentation/operators/src/nodes/mix-node-setup.md
index 68f6bf9090..dc27005feb 100644
--- a/documentation/operators/src/nodes/mix-node-setup.md
+++ b/documentation/operators/src/nodes/mix-node-setup.md
@@ -10,6 +10,10 @@ TODO
 - [x] Add second console output to Initialising your mixnode manually as the automatized is not working
 - [ ] Point users to understand the requirements for becoming a part of the active set.
 - [ ] Include how to move a mix node from one VPS to another while keeping the delegation etc (ie init a new mix node and move `/home/nym/.nym/mixnodes/data/*` there ?)
+    - copy that dir over to the new vps
+    - re-run init - remember that init doesn't overwrite existing keys - to generate a  config with the new listening address etc
+    - change the node info via the wallet
+    - Since otherwise their keys will point to the old IP address in the smart contract, and their node will (a) not be able to be connected to, and (b) fail uptime checks 
 - [ ] Explain more about self hosted nodes in the 6.1 not only as a troubleshooting
 --->