Fix lints

Author: MauroToscano

docs/0_internal/2_deploy_contracts.md

@@ -9,11 +9,13 @@ Also, you will be able to deploy the Batcher Payment Service contract.
 - You need to have installed `git` and `make`.
 
 - Clone the repository
-   ```
+
+   ```sh
    git clone https://github.com/yetanotherco/aligned_layer.git
    ```
 
 - Install foundry
+
     ```shell
     make install_foundry
     foundryup -v nightly-a428ba6ad8856611339a6319290aade3347d25d9
@@ -65,7 +67,6 @@ Also, you will be able to deploy the Batcher Payment Service contract.
     - Holesky: `contracts/script/output/holesky/alignedlayer_deployment_output.json`
     - Sepolia: `contracts/script/output/sepolia/alignedlayer_deployment_output.json`
 
-
 ## BatcherPaymentsService Contracts
 
 1. You should have a keystore for the Batcher, with the Seedphrase saved on paper.
@@ -78,7 +79,7 @@ Also, you will be able to deploy the Batcher Payment Service contract.
 
 5. Set the ```PRIVATE_KEY``` and ```ETHERSCAN_API_KEY```on the ```.env``` used to deploy. ```contracts/scripts/.env.mainnet``` or ```contracts/scripts/.env.holesky``` or ```contracts/scripts/.env.sepolia```
 
-6. Set `owner` value of `contracts/script/deploy/config/mainnet/batcher-payment-service.mainnet.config.json` or `contracts/script/deploy/config/holesky/batcher-payment-service.holesky.config.json` or `contracts/script/deploy/config/sepolia/batcher-payment-service.sepolia.config.json` to the multisig controlling this contract, or the owner of the deploying address, depending on what you want. 
+6. Set `owner` value of `contracts/script/deploy/config/mainnet/batcher-payment-service.mainnet.config.json` or `contracts/script/deploy/config/holesky/batcher-payment-service.holesky.config.json` or `contracts/script/deploy/config/sepolia/batcher-payment-service.sepolia.config.json` to the multisig controlling this contract, or the owner of the deploying address, depending on what you want.
 
 7. Set `batcherWallet` value of `contracts/script/deploy/config/mainnet/batcher-payment-service.mainnet.config.json` or `contracts/script/deploy/config/holesky/batcher-payment-service.holesky.config.json` or `contracts/script/deploy/config/sepolia/batcher-payment-service.sepolia.config.json` to the address from step 1.
 

docs/0_internal/3_b_1_deploy_new_impl.md

@@ -7,12 +7,12 @@ To deploy a new implementation, you can follow the steps below.
 1. Make sure you have set variables as specified in the [Deploy Contracts Guide](./2_deploy_contracts.md).
 
 2. Add the following variables to the `.env` file:
-    
+
     ```makefile
     MULTISIG=true
     ```
-   
-## Deploy New Implementation
+
+## What contracts can be upgraded?
 
 You can deploy the new implementation of the following contracts:
 
@@ -23,58 +23,55 @@ You can deploy the new implementation of the following contracts:
 ### Deploy New Implementation for AlignedLayerServiceManager
 
 1. Deploy the new implementation by running:
-          
-   ```shell
+
+   ```sh
    make upgrade_aligned_contracts
    ```
-   
+
    If the new implementation is correctly deployed, the script will show the following message:
-    
-   ```
+
+   ```sh
    The new aligned layer service manager implementation is <new_aligned_layer_service_manager_implementation>
 
    You can propose the upgrade transaction with the multisig using this calldata
     <calldata>
     ```
-   
+
    You should save this `calldata` for later use.
-   
+
 2. Get the `upgrade` function signature:
 
-   ```
+   ```sh
    cast sig "upgrade(address, address)"
    ```
 
    This will show the `upgrade` signature hash: `0x99a88ec4`.
 
 3. Validate the `calldata` by running:
-   
-   ```
+
+   ```sh
    cast calldata-decode "upgrade(address, address)" <calldata>
    ```
 
    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. 
-
+>
+> Make sure the `alignedServiceManagerImplementation` address is the same as the one you deployed in this guide.
 
 ### Deploy New Implementation for BatcherPaymentService
 
 1. Deploy the new implementation by running:
-    
+
     ```shell
     make upgrade_batcher_payment_service
     ```
 
     If the new implementation is correctly deployed, the script will show the following message:
-    
-    ```
-    You can propose the upgrade transaction with the multisig using this calldata
-    <calldata>
-    ```
+
+    `You can propose the upgrade transaction with the multisig using this calldata
+    <calldata>`
 
    You should save this `calldata` for later use.
 
@@ -88,7 +85,7 @@ You can deploy the new implementation of the following contracts:
 
 3. Validate the `calldata` by running:
 
-   ```
+   ```shell
    cast calldata-decode "upgradeTo(address)" <calldata>
    ```
 
@@ -97,21 +94,20 @@ You can deploy the new implementation of the following contracts:
 > [!NOTE]
 > Make sure the `batcherPaymentServiceImplementation` address is the same as the one you deployed in this guide.
 
-
 ### Deploy New Implementation for RegistryCoordinator
 
 1. Deploy the new implementation by running:
-    
-    ```shell
+
+    ```sh
     make upgrade_registry_coordinator
     ```
 
     If the new implementation is correctly deployed, the script will show the following message:
-    
-    ```
+
+    `
     You can propose the upgrade transaction with the multisig using this calldata
     <calldata>
-    ```
+    `
 
    You should save this `calldata` for later use.
 
@@ -125,7 +121,7 @@ You can deploy the new implementation of the following contracts:
 
 3. Validate the `calldata` by running:
 
-   ```
+   ```sh
    cast calldata-decode "upgrade(address, address)" <calldata>
    ```
 
@@ -136,7 +132,6 @@ You can deploy the new implementation of the following contracts:
 >
 > Make sure the `registryCoordinatorImplementation` address is the same as the one you deployed in this guide.
 
-   
 ## Next Steps
 
 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).