docs: add approve process

Author: JuArce

docs/0_internal/3_b_1_deploy_new_impl.md

@@ -144,4 +144,4 @@ You can deploy the new implementation of the following contracts:
 
 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).
 
-Send the new address and `calldata` to the multisig participants to propose the upgrade transaction.
+Send the contracts addresses and `calldata` to the multisig participants to propose the upgrade transaction.

docs/0_internal/3_b_2_propose_upgrade.md

@@ -105,11 +105,7 @@ To propose the upgrade transaction you can follow the steps below:
    > 
    >    Make sure to set the path to the correct deployment output file.
 
-8. If the ABI is not automatically filled, get the ABI and paste it on the corresponding box:
-
-    ```bash
-    jq ".abi" contracts/out/ProxyAdmin.sol/ProxyAdmin.json | pbcopy
-    ```
+8. Once you paste the `ProxyAdmin` address, the ABI should be automatically filled.
 
     ![Enter Address or ENS Name](./images/3_b_2_multisig_3.png)
 
@@ -123,5 +119,28 @@ To propose the upgrade transaction you can follow the steps below:
 
     ![Data](./images/3_b_2_multisig_6.png)
 
+   You should see the new transaction to be executed on the right side.
+
+11. Click on `Create batch` to create the transaction.
+
+    ![Create batch](./images/3_b_2_multisig_7.png)
+
+12. Review and confirm the transaction.
+   
+   To make sure everything is fine, simulate the transaction by clicking on `Simulate batch`
+
+   Once the simulation is successful, click on `Send Batch` to send the transaction.
+
+    ![Simulate batch](./images/3_b_2_multisig_8.png)
+
+13. Confirm the transaction checking the function being called is correct and the contract address is the one you deployed.
+
+   If everything is correct, click on `Sign` to send the transaction.
+
+    ![Confirm transaction](./images/3_b_2_multisig_9.png)
+
+14. Now in your transactions, you should be able to see the newly created transaction.
 
+    ![New transaction](./images/3_b_2_multisig_10.png)
 
+15. If the transaction is correctly created, you have to wait until the required Multisig member signs the transaction to send it.

docs/0_internal/3_b_3_approve_upgrade.md

@@ -0,0 +1,45 @@
+# Approve the Upgrade
+
+Once the transaction is proposed, the multisig owners must approve the transaction.
+
+## Prerequisites
+
+- One of the multisig owners must have proposed the upgrade transaction using the `calldata` obtained from the deployment of the new implementation.
+
+## Approve the Upgrade
+
+To approve the upgrade transaction, you can follow the steps below:
+
+1. Go to [Safe](https://app.safe.global/home) and connect your wallet.
+
+2. Go to the `Transactions` tab and find the transaction that was proposed.
+
+3. Click on the transaction and validate the data is correct. 
+
+   If you are upgrading the AlignedLayerServiceManager or the RegistryCoordinator, the called function must be `upgrade(address, address)`.
+
+   Else, if you are upgrading the BatcherPaymentService, the called function must be `upgradeTo(address)`.
+
+   Also check contract addresses are the ones you received from the deployment.
+
+   ![Check details](images/3_b_3_approve_1.png)
+
+4. If data is correct, click on `Confirm` and sign the transaction.
+
+   ![Confirm transaction](images/3_b_3_approve_2.png)
+
+5. Revalidate the transaction data and simulate the transaction to check everything is correct.
+
+   ![Simulate transaction](images/3_b_3_approve_3.png)
+
+6. Once you are sure everything is correct, click on `Execute` to approve the transaction.
+
+   > [!NOTE]
+   > 
+   > The transaction gas usage is approximately 100,000 gas units. Make sure you have enough ETH to cover the gas fees.
+
+7. Wait for the transaction to be executed. You can check the transaction status on the `Transactions` tab.
+
+8. Once the multisig threshold is reached, the transaction will be executed and the contract will be upgraded.
+
+   ![Transaction executed](images/3_b_3_approve_4.png)