fix: docs tidyness

Author: uri-99

contracts/scripts/.env.example.holesky

@@ -1,6 +1,6 @@
 RPC_URL=<rpc_url>
 PRIVATE_KEY=<private_key>
-EXISTING_DEPLOYMENT_INFO_PATH=./script/output/holesky/Holesky_current_deployment.config.json
+EXISTING_DEPLOYMENT_INFO_PATH=./script/output/holesky/eigenlayer_deployment_output.json
 DEPLOY_CONFIG_PATH=./script/deploy/config/holesky/aligned.holesky.config.json
 OUTPUT_PATH=./script/output/holesky/alignedlayer_deployment_output.json
 ETHERSCAN_API_KEY=<etherscan_api_key>

docs/3_guides/setup_holesky.md

@@ -28,6 +28,8 @@ The necessary environment variables are:
 
 You can find an example `.env` file in [.env.example.holesky](../../contracts/scripts/.env.example.holesky)
 
+Note: all file paths must be inside the `script/` folder, as shown in `.env.example.holesky` because of `foundry`'s permissions to read and write files.
+
 You need to complete the `DEPLOY_CONFIG_PATH` file with the following information:
 
 ```json

docs/multisig.md

@@ -18,6 +18,7 @@ In this guide we make an upgrade of Aligned Layer Service Manager contract using
 - Multisig Wallet
   - You can create a Multisig wallet using [Safe](https://safe.global/). For this guide, I have created a 2/3 Multisig.
 - [jq](https://jqlang.github.io/jq/download/)
+  - `jq` is needed to programatically read contents of `.json` config files 
 
 ## Initial setup