From f51af10a926c69a241f48642efc8ac4af1dbcee4 Mon Sep 17 00:00:00 2001
From: Uriel Mihura <43704209+uri-99@users.noreply.github.com>
Date: Fri, 22 Nov 2024 15:20:43 -0300
Subject: [PATCH] Update docs/0_internal/3_b_1_deploy_new_impl.md

---
 docs/0_internal/3_b_1_deploy_new_impl.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/0_internal/3_b_1_deploy_new_impl.md b/docs/0_internal/3_b_1_deploy_new_impl.md
index 34288c59d..d3428ee3d 100644
--- a/docs/0_internal/3_b_1_deploy_new_impl.md
+++ b/docs/0_internal/3_b_1_deploy_new_impl.md
@@ -139,6 +139,6 @@ You can deploy the new implementation of the following contracts:
    
 ## Next Steps
 
-Once you have deployed the new implementation of the contract you want to upgrade, you need to propose the upgrade transaction following this [guide](./3_b_2_propose_upgrade.md).
+Once you have deployed the new implementation of the contract you want to upgrade, you need to propose the upgrade transaction to the mulstisig, following this [guide](./3_b_2_propose_upgrade.md).
 
-Send the contracts addresses and `calldata` to the multisig participants to propose the upgrade transaction.
+You must also send the contracts addresses and `calldata` you gathered from this guide, to all the multisig participants.