diff --git a/README.md b/README.md
index 3c527fa..235f083 100644
--- a/README.md
+++ b/README.md
@@ -21,8 +21,12 @@ This repository contains all the resources for deploying a forger or rpc EVM sid
 
 ## Upgrade
 
-1. If your project structure is 1.2.* follow the instructions here: [Migration from 1.2.* to 1.3.0](./docs/MIGRATION.md)
+1. If your project structure is 1.2.* , first follow the instructions here: [Migration from 1.2.* to 1.3.0](./docs/MIGRATION.md)
 2. Run the [upgrade.sh](./scripts/upgrade.sh) script to upgrade the project to the new version. Should the script prompt you to update some of the values in .env file, it is reccomended to accept all the changes unless you know what you are doing.
+3. Check that you're running the updated version with the following command :
+```
+docker exec evmapp gosu user curl -X POST "http://127.0.0.1:9545/node/info" -H  "accept: application/json" | grep nodeVersion
+```
 
 ---
 
diff --git a/docs/MIGRATION.md b/docs/MIGRATION.md
index 0de710e..dab60ed 100644
--- a/docs/MIGRATION.md
+++ b/docs/MIGRATION.md
@@ -16,4 +16,5 @@ If you are using version 1.2.* of this project, you will need to follow these st
 5. When requested by the script provide the already generated SCNODE_WALLET_SEED available in the old .env file.
 6. Review the new .env file and update the values if necessary. For instance RPC or REST passwords, or node names.
 7. Run the `docker compose up -d` command to start the new containers. See the [README](../README.md) for more information. 
+8. Go back to [README](../README.md) and execute the second step, regarding the [upgrade.sh](./scripts/upgrade.sh) script.
 The nodes should start and use the old volumes and data, so there should be no need to resync the nodes.