From dbb50ab30a50a5beb9ab03c63225b6b64d101237 Mon Sep 17 00:00:00 2001
From: "Leslie H. Cheung" <51898510+lezzokafka@users.noreply.github.com>
Date: Mon, 17 May 2021 11:02:30 +0800
Subject: [PATCH] Update docs/getting-started/upgrade_guide.md

Co-authored-by: Calvin Lau <38898718+calvinaco@users.noreply.github.com>
---
 docs/getting-started/upgrade_guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting-started/upgrade_guide.md b/docs/getting-started/upgrade_guide.md
index 4af18aa6..94267c03 100644
--- a/docs/getting-started/upgrade_guide.md
+++ b/docs/getting-started/upgrade_guide.md
@@ -11,6 +11,7 @@ At the point of proposed upgrade, user will see the following error message on t
 `ERR BINARY UPDATED BEFORE TRIGGER! UPGRADE "v2.0.0" - in binary but not executed on chain`
 
 Don't panic - The Chain will be paused to allow the majority of validators to upgrade. Validators and full node hosts will have to upgrade your Crypto.org Chain nodes to the latest release binary.
+
 ## Step 1 - Get the `v2.0.0` binary
 
 To simplify the following step, we will be using **Linux** for illustration. Binary for
@@ -131,4 +132,3 @@ Sit back and wait for the syncing process. You can query the node syncing status
   $ ./chain-maind status 2>&1 | jq '.SyncInfo.catching_up'
   ```
   If the above command returns `false`, It means that your node **is synced**; otherwise, it returns `true` and implies your node is still catching up.
-