fix: notes

Author: JuArce

docs/0_internal/3_b_1_deploy_new_impl.md

@@ -56,9 +56,7 @@ You can deploy the new implementation of the following contracts:
    This will show two addresses. The first one is the `alignedLayerServiceManager` address, and the second one is the new implementation address of `alignedServiceManagerImplementation`.
 
    > [!NOTE]
-   > 
    > Make sure the `alignedLayerServiceManager` address is the same as the one you deployed in the [Deploy Contracts Guide](./2_deploy_contracts.md).
-   > 
    > Make sure the `alignedServiceManagerImplementation` address is the same as the one you deployed in this guide. 
 
 
@@ -96,7 +94,6 @@ You can deploy the new implementation of the following contracts:
    This will show the `batcherPaymentServiceImplementation` address.
 
    > [!NOTE]
-   >
    > Make sure the `batcherPaymentServiceImplementation` address is the same as the one you deployed in this guide.
 
 
@@ -134,9 +131,7 @@ You can deploy the new implementation of the following contracts:
    This will show two addresses. The first one is the `registryCoordinator` address, and the second one is the new implementation address of `registryCoordinatorImplementation`.
 
    > [!NOTE]
-   >
    > Make sure the `registryCoordinator` address is the same as the one you deployed in the [Deploy Contracts Guide](./2_deploy_contracts.md).
-   >
    > Make sure the `registryCoordinatorImplementation` address is the same as the one you deployed in this guide.
 
 

docs/0_internal/3_b_2_propose_upgrade.md

@@ -45,11 +45,8 @@ To propose the upgrade transaction you can follow the steps below:
     If you are upgrading the RegistryCoordinator, the first one is the `registryCoordinator` address, and the second one is the new implementation address of `registryCoordinatorImplementation`.
 
    > [!NOTE]
-   > 
    > The first 10 characters must be the same the signature hash obtained in the previous step.
-   >
    > Make sure the `alignedLayerServiceManager` address is the same as the one you deployed in the [Deploy Contracts Guide](./2_deploy_contracts.md).
-   >
    > Make sure the `alignedServiceManagerImplementation` address is the same as the one you deployed in this guide.
 
     Else, if you are upgrading the BatcherPaymentService, you can validate the calldata by running:
@@ -61,9 +58,7 @@ To propose the upgrade transaction you can follow the steps below:
     This will show the `batcherPaymentServiceImplementation` address.
 
     > [!NOTE]
-    > 
     > The first 10 characters must be the same the signature hash obtained in the previous step.
-    >
     > Make sure the `batcherPaymentServiceImplementation` address is the same as the one you deployed in this guide. 
 
 3. Verify the contract bytecode running the following command:
@@ -102,7 +97,6 @@ To propose the upgrade transaction you can follow the steps below:
     ```
 
    >    [!NOTE]
-   > 
    >    Make sure to set the path to the correct deployment output file.
 
 8. Once you paste the `ProxyAdmin` address, the ABI should be automatically filled.

docs/0_internal/3_b_3_approve_upgrade.md

@@ -35,7 +35,6 @@ To approve the upgrade transaction, you can follow the steps below:
 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.