From 96fe8e75f68191c648c26d5ae6a48a201d81a3a9 Mon Sep 17 00:00:00 2001 From: Leslie Cheung Date: Tue, 9 Apr 2024 12:56:48 +0000 Subject: [PATCH] GITBOOK-227: change request with no subject merged in GitBook --- .../cronos-mainnet/the-v1.2-upgrade-guide-v1.1.-to-v1.2.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/for-node-hosts/running-nodes/cronos-mainnet/the-v1.2-upgrade-guide-v1.1.-to-v1.2.0.md b/for-node-hosts/running-nodes/cronos-mainnet/the-v1.2-upgrade-guide-v1.1.-to-v1.2.0.md index c9eb57e..528648f 100644 --- a/for-node-hosts/running-nodes/cronos-mainnet/the-v1.2-upgrade-guide-v1.1.-to-v1.2.0.md +++ b/for-node-hosts/running-nodes/cronos-mainnet/the-v1.2-upgrade-guide-v1.1.-to-v1.2.0.md @@ -26,7 +26,7 @@ It is critically important for validator operators to back up the `.cronos/data/ ## Step 1 - Get the `v1.2.0` binary -To simplify the following step, we will be using **Linux-x86** for illustration. Binary for Mac Windows with different DB and architecture are also available [here](https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0). +To simplify the following step, we will be using **Linux-x86** for illustration. Binary for Mac Windows with different DB and architecture are also available [here](https://github.com/crypto-org-chain/cronos/releases/tag/v1.2.0). * Terminate the `cronosd`; afterwards, download the `1.2.0` released binaries from github: