From e9db4160e7b6bef06e7968d2de5c4321dd862a25 Mon Sep 17 00:00:00 2001
From: Marius Poke <marius.poke@posteo.de>
Date: Wed, 18 Sep 2024 11:40:09 +0200
Subject: [PATCH] fix inconsistency on docs (#3341)

---
 docs/docs/hub-tutorials/join-mainnet.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docs/hub-tutorials/join-mainnet.md b/docs/docs/hub-tutorials/join-mainnet.md
index b461af4087b..9a966462636 100644
--- a/docs/docs/hub-tutorials/join-mainnet.md
+++ b/docs/docs/hub-tutorials/join-mainnet.md
@@ -449,10 +449,10 @@ gaiad export --height [height] --for-zero-height > [filename].json
 ## Verify Mainnet
 
 Help to prevent a catastrophe by running invariants on each block on your full
-node. In essence, by running invariants the node operator ensures that the state of mainnet is the correct expected state. One vital invariant check is that no atoms are being created or destroyed outside of expected protocol, however there are many other invariant checks each unique to their respective module. Because invariant checks are computationally expensive, they are not enabled by default. To run a node with these checks start your node with the --x-crisis-skip-assert-invariants flag:
+node. In essence, by running invariants the node operator ensures that the state of mainnet is the correct expected state. One vital invariant check is that no atoms are being created or destroyed outside of expected protocol, however there are many other invariant checks each unique to their respective module. Because invariant checks are computationally expensive, they are not enabled by default. To run a node with these checks start your node without the `--x-crisis-skip-assert-invariants` flag:
 
 ```bash
-gaiad start --x-crisis-skip-assert-invariants
+gaiad start
 ```
 
 If an invariant is broken on the node, it will panic and prompt the operator to send a transaction which will halt mainnet. For example the provided message may look like: