From 8757b4dde803440cc2220e55da044c583df9b9cd Mon Sep 17 00:00:00 2001
From: Marcel Moura <5615598+marcelstanley@users.noreply.github.com>
Date: Tue, 9 Jul 2024 11:39:09 -0300
Subject: [PATCH] chore(docs): amend v1.5.0 upgrade guide

---
 docs/upgrade_to_1_5.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/upgrade_to_1_5.md b/docs/upgrade_to_1_5.md
index 0a7af3c1f..8bc5ec711 100644
--- a/docs/upgrade_to_1_5.md
+++ b/docs/upgrade_to_1_5.md
@@ -26,7 +26,7 @@ Where `BLOCK_TIME` corresponds to the duration it takes to generate a block in t
 >
 > So, `CARTESI_EPOCH_LENGTH = 86400/12 = 7200`
 
-Check the [`CHANGELOG`](./CHANGELOG.md) and the [configuration](./docs/config.md) for more details.
+Check the [`CHANGELOG`](../CHANGELOG.md) and the [Rolups Node configuration](./config.md) for more details.
 
 ## How to upgrade
 
@@ -126,5 +126,6 @@ cast send \
 ```
 
 After the _History_ replacement is complete, one must update `CARTESI_CONTRACTS_HISTORY_ADDRESS` with the new _History_ address in the application configuration and proceed with the upgrade of the Cartesi Rollups Node as usual.
+More details about the release may be found in the [CHANGELOG](../CHANGELOG.md).
 
 Once the Cartesi Rollups Node is started, it will relay all existing inputs to be processed by the application, calculate the new epochs and send the respective claims to the new _History_ as a result, all based on the updated configuration.