docs: update propose pause process

Author: JuArce

docs/0_internal/4_b_1_propose_pause.md

@@ -10,76 +10,46 @@ If you want to pause the contracts, you can propose the pause transaction using
 
 To propose the pause transaction you can follow the steps below:
 
-1. Create the pause transaction on [Safe](https://app.safe.global/home)
+1. Go to [Safe](https://app.safe.global/home)
 
 2. Click on `New transaction` -> `Transaction Builder`
 
    ![New transaction](./images/4_b_1_pause_1.png)
 
    ![Transaction Builder](./images/4_b_1_pause_2.png)
 
-3. . Enable `Custom data`
-
-4. . Get the `AlignedLayerServiceManager` address:
-
-    ```bash
-   # SEPOLIA
-   jq -r ".addresses.alignedLayerServiceManager" contracts/script/output/sepolia/alignedlayer_deployment_output.json | pbcopy
-    ```
-
-    ```bash
-   # HOLESKY
-   jq -r ".addresses.alignedLayerServiceManager" contracts/script/output/holesky/alignedlayer_deployment_output.json | pbcopy
-    ```
+3. . Get the `AlignedLayerServiceManager` address from ```contracts/script/output/mainnet/alignedlayer_deployment_output.json``` or ```contracts/script/output/holesky/alignedlayer_deployment_output.json``` or ```contracts/script/output/sepolia/alignedlayer_deployment_output.json```
 
-    ```bash
-    # MAINNET
-    jq -r ".addresses.alignedLayerServiceManager" contracts/script/output/mainnet/alignedlayer_deployment_output.json | pbcopy
-    ```
-
->    [!NOTE]
->    Make sure to set the path to the correct deployment output file.
-
-5. Paste the `AlignedLayerServiceManager` address on `Enter Address or ENS Name`
+4. Paste the `AlignedLayerServiceManager` address on `Enter Address or ENS Name`
 
    ![Enter Address](./images/4_b_1_pause_3.png)
 
-6. Set the `ETH Value` to 0.
-
-7. . Generate the function calldata
+5. As this is a Proxy contract, choose `Use Implementation ABI`
 
-    ```bash
-    cast calldata "pauseAll()"
-    ```
+   ![Use Implementation ABI](./images/4_b_1_pause_4.png)
 
-    This will show the `pauseAll()` calldata: `0x595c6a67`.
+6. In `contract method selector` choose `pauseAll()`
 
-8. Paste the `calldata` on `Enter Data`
+   ![Choose pause](./images/4_b_1_pause_5.png)
 
-   ![Enter Data](./images/4_b_1_pause_4.png)
-
-9. Click on `+ Add new transaction`
+7. Click on `+ Add new transaction`
 
    You should see the new transaction to be executed
 
-10. Click on `Create batch` to create the transaction.
-
-11. Simulate the transaction by clicking on `Simulate`
+8. Click on `Create batch` to create the transaction.
 
-12. Check the data matches with the generated data on step 7.
+9. Simulate the transaction by clicking on `Simulate`
 
-   ![Validate data](./images/4_b_1_pause_5.png)
+10. If everything is correct, click on `Send batch` to send the transaction.
 
-13. If everything is correct, click on `Send batch` to send the transaction.
-
-14. Simulate the transaction, and if everything is correct, click on `Sign`.
+11. Simulate the transaction, and if everything is correct, click on `Sign`.
 
    ![Send batch](./images/4_b_1_pause_6.png)
 
 > [!NOTE]
 > In the `call` field, you will see `fallback`.
 
-15. Wait for the transaction to be executed. You can check the transaction status on the `Transactions` tab.
+12. Wait for the transaction to be executed. You can check the transaction status on the `Transactions` tab.
 
 
 ## Propose transaction for Pause BatcherPaymentService
@@ -94,54 +64,36 @@ To propose the pause transaction you can follow the steps below:
 
    ![Transaction Builder](./images/4_b_1_pause_2.png)
 
-3. . Get the `BatcherPaymentService` address:
-
-    ```bash
-   # SEPOLIA
-   jq -r ".addresses.batcherPaymentService" contracts/script/output/sepolia/alignedlayer_deployment_output.json | pbcopy
-    ```
-
-    ```bash
-   # HOLESKY
-   jq -r ".addresses.batcherPaymentService" contracts/script/output/holesky/alignedlayer_deployment_output.json | pbcopy
-    ```
-
-    ```bash
-    # MAINNET
-    jq -r ".addresses.batcherPaymentService" contracts/script/output/mainnet/alignedlayer_deployment_output.json | pbcopy
-    ```
-
->    [!NOTE]
->    Make sure to set the path to the correct deployment output file.
+3. . Get the `BatcherPaymentService` address from ```contracts/script/output/mainnet/alignedlayer_deployment_output.json``` or ```contracts/script/output/holesky/alignedlayer_deployment_output.json``` or ```contracts/script/output/sepolia/alignedlayer_deployment_output.json```
 
-5. Paste the `BatcherPaymentService` address on `Enter Address or ENS Name`
+4. Paste the `BatcherPaymentService` address on `Enter Address or ENS Name`
 
    ![Enter Address](./images/4_b_1_pause_3.png)
 
-6. As this is a Proxy contract, choose `Use Implementation ABI`
+5. As this is a Proxy contract, choose `Use Implementation ABI`
 
-   ![Use Implementation ABI](./images/4_b_1_pause_7.png)
+   ![Use Implementation ABI](./images/4_b_1_pause_4.png)
 
-7. In `contract method selector` choose `pause()`
+6. In `contract method selector` choose `pause()`
 
    ![Choose pause](./images/4_b_1_pause_8.png)
 
-8. Then click on `+ Add new transaction`
+7. Then click on `+ Add new transaction`
 
    You should see the new transaction to be executed. Then click on `Create batch` to create the transaction.
 
    ![Add new transaction](./images/4_b_1_pause_9.png)
 
-9. Review and confirm you are interacting with the correct `BatcherPaymentService` contract and you are calling the `pause` function.
+8. Review and confirm you are interacting with the correct `BatcherPaymentService` contract and you are calling the `pause` function.
 
    ![Review transaction](./images/4_b_1_pause_10.png)
 
-10. Simulate the transaction by clicking on `Simulate`
+9. Simulate the transaction by clicking on `Simulate`
 
-11. If everything is correct, click on `Send batch` to send the transaction.
+10. If everything is correct, click on `Send batch` to send the transaction.
 
-12. Review the transaction and click on `Sign` to sign the transaction.
+11. Review the transaction and click on `Sign` to sign the transaction.
 
    ![Send batch](./images/4_b_1_pause_11.png)
 
-13. If the transaction is correctly created, you have to wait until the required Multisig member signs the transaction to send it.
+12. If the transaction is correctly created, you have to wait until the required Multisig member signs the transaction to send it.