fix: number display order (#1168)

Co-authored-by: lotteam007 <[email protected]>
axelarnetwork · Sep 20, 2024 · facb7de · facb7de
1 parent 3073ea1
commit facb7de
Show file tree

Hide file tree

Showing 6 changed files with 12 additions and 12 deletions.
diff --git a/src/content/docs/resources/mainnet/upgrades/v21.mdx b/src/content/docs/resources/mainnet/upgrades/v21.mdx
@@ -31,8 +31,8 @@ cp -r ~/.axelar/.core/data ~/.axelar-dojo-1-upgrade-0.21/.core/data
   Caution: If you backup the entire folder, `~/.axelar/.core`, that'll also include your private keys (inside `config` and `keyring-file` subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.
 </Callout>
 
-1. Restart your node with the new `v0.21.1` build.
-2. If you're a validator also restart `vald` with `v0.21.1` and `tofnd` with `v0.10.1`.
+4. Restart your node with the new `v0.21.1` build.
+5. If you're a validator also restart `vald` with `v0.21.1` and `tofnd` with `v0.10.1`.
 
 Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):
 

diff --git a/src/content/docs/resources/mainnet/upgrades/v24.mdx b/src/content/docs/resources/mainnet/upgrades/v24.mdx
@@ -31,8 +31,8 @@ cp -r ~/.axelar/.core/data ~/.axelar-dojo-1-upgrade-0.24/.core/data
   Caution: If you backup the entire folder, `~/.axelar/.core`, that'll also include your private keys (inside `config` and `keyring-file` subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.
 </Callout>
 
-1. Restart your node with the new `v0.24.0` build.
-2. If you're a validator also restart `vald` with `v0.24.0` and `tofnd` with `v0.10.1`.
+4. Restart your node with the new `v0.24.0` build.
+5. If you're a validator also restart `vald` with `v0.24.0` and `tofnd` with `v0.10.1`.
 
 Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):
 

diff --git a/src/content/docs/resources/mainnet/upgrades/v26.mdx b/src/content/docs/resources/mainnet/upgrades/v26.mdx
@@ -31,8 +31,8 @@ cp -r ~/.axelar/.core/data ~/.axelar-dojo-1-upgrade-0.26/.core/data
   Caution: If you backup the entire folder, `~/.axelar/.core`, that'll also include your private keys (inside `config` and `keyring-file` subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.
 </Callout>
 
-1. Restart your node with the new `v0.26.5` build.
-2. If you're a validator also restart `vald` with `v0.26.5` and `tofnd` with `v0.10.1`.
+4. Restart your node with the new `v0.26.5` build.
+5. If you're a validator also restart `vald` with `v0.26.5` and `tofnd` with `v0.10.1`.
 
 Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):
 

diff --git a/src/content/docs/resources/mainnet/upgrades/v28.mdx b/src/content/docs/resources/mainnet/upgrades/v28.mdx
@@ -33,8 +33,8 @@ cp -r ~/.axelar/.core/data ~/.axelar-dojo-1-upgrade-0.28/.core/data
   Caution: If you backup the entire folder, `~/.axelar/.core`, that'll also include your private keys (inside `config` and `keyring-file` subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.
 </Callout>
 
-1. Restart your node with the new `v0.28.0` build.
-2. If you're a validator also restart `vald` with `v0.28.0` and `tofnd` with `v0.10.1`.
+4. Restart your node with the new `v0.28.0` build.
+5. If you're a validator also restart `vald` with `v0.28.0` and `tofnd` with `v0.10.1`.
 
 Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):
 

diff --git a/src/content/docs/resources/mainnet/upgrades/v29.mdx b/src/content/docs/resources/mainnet/upgrades/v29.mdx
@@ -31,8 +31,8 @@ cp -r ~/.axelar/.core/data ~/.axelar-dojo-1-upgrade-0.29/.core/data
   Caution: If you backup the entire folder, `~/.axelar/.core`, that'll also include your private keys (inside `config` and `keyring-file` subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.
 </Callout>
 
-1. Restart your node with the new `v0.29.1` build.
-2. If you're a validator also restart `vald` with `v0.29.1` and `tofnd` with `v0.10.1`.
+4. Restart your node with the new `v0.29.1` build.
+5. If you're a validator also restart `vald` with `v0.29.1` and `tofnd` with `v0.10.1`.
 
 Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):
 

diff --git a/src/content/docs/resources/mainnet/upgrades/v31.mdx b/src/content/docs/resources/mainnet/upgrades/v31.mdx
@@ -31,8 +31,8 @@ cp -r ~/.axelar/.core/data ~/.axelar-dojo-1-upgrade-0.31/.core/data
   Caution: If you backup the entire folder, `~/.axelar/.core`, that'll also include your private keys (inside `config` and `keyring-file` subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.
 </Callout>
 
-1. Restart your node with the new `v0.31.2` build.
-2. If you're a validator also restart `vald` with `v0.31.2` and `tofnd` with `v0.10.1`.
+4. Restart your node with the new `v0.31.2` build.
+5. If you're a validator also restart `vald` with `v0.31.2` and `tofnd` with `v0.10.1`.
 
 Example using join scripts in [axelarate-community git repo](https://github.com/axelarnetwork/axelarate-community):