diff --git a/docs/MEV-relay-list.md b/docs/MEV-relay-list.md
index 184baa8..208320e 100644
--- a/docs/MEV-relay-list.md
+++ b/docs/MEV-relay-list.md
@@ -65,4 +65,4 @@ Selecting your relays **can be an important decision** for some stakers. You sho
 
 # Configuring MEV boost software
 
-If you need help installing and configuring mev-boost on your machine, check out our [Guide on how to prepare a staking machine for the Merge](https://github.com/eth-educators/ethstaker-guides/blob/main/prepare-for-the-merge.md#choosing-and-configuring-an-mev-solution)
+If you need help installing and configuring mev-boost on your machine, check out our [Guide on how to prepare a staking machine for the Merge](https://github.com/eth-educators/ethstaker-guides/blob/main/docs/prepare-for-the-merge.md#choosing-and-configuring-an-mev-solution)
diff --git a/docs/alerting.md b/docs/alerting.md
index f532cc6..1da0834 100644
--- a/docs/alerting.md
+++ b/docs/alerting.md
@@ -426,7 +426,7 @@ I created a simple script to ease the pain of updating Alertmanager. You can fin
 You can easily download this script with:
 
 ```console
-$ wget https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/scripts/update-alertmanager.py
+$ wget https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/docs/scripts/update-alertmanager.py
 ```
 
 To run the Alertmanager update script, use this command:
diff --git a/docs/monitoring.md b/docs/monitoring.md
index dc00994..6521fd6 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -516,7 +516,7 @@ Aug 09 12:34:05 remy-MINIPC-PN50 systemd[1]: Reloaded Prometheus.
 Aug 09 12:34:05 remy-MINIPC-PN50 prometheus[1934]: level=info ts=2021-08-09T16:34:05.304Z caller=main.go:981 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
 Aug 09 12:34:05 remy-MINIPC-PN50 prometheus[1934]: level=info ts=2021-08-09T16:34:05.311Z caller=main.go:1012 msg="Completed loading of configuration file" filename=/etc/prometheus/prometheus.yml totalDuration=7.822144ms remote_storage=4.305µs web_handler=6.249µs query_engine=1.734µs scrape=1.831998ms scrape_sd=83.865µs notify=618.619µs notify_sd=51.754µs rules=1.993µs
 ```
-3. Import [a good Geth dashboard for Prometheus](https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/dashboards/geth-grafana.json) in Grafana.
+3. Import [a good Geth dashboard for Prometheus](https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/docs/dashboards/geth-grafana.json) in Grafana.
 
 ### Prysm
 
@@ -726,8 +726,8 @@ I created some simple scripts to ease the pain of updating Prometheus and Node E
 You can easily download those scripts with:
 
 ```console
-$ wget https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/scripts/update-prometheus.py
-$ wget https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/scripts/update-node-exporter.py
+$ wget https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/docs/scripts/update-prometheus.py
+$ wget https://raw.githubusercontent.com/eth-educators/ethstaker-guides/main/docs/scripts/update-node-exporter.py
 ```
 
 To run the Prometheus update script, use this command:
diff --git a/docs/prepare-for-the-merge.md b/docs/prepare-for-the-merge.md
index e197dff..e2ac724 100644
--- a/docs/prepare-for-the-merge.md
+++ b/docs/prepare-for-the-merge.md
@@ -101,7 +101,7 @@ If you used a guide or a tool to setup your staking machine, you should first ch
 
 ## Using the new configuration options for your Ethereum clients
 
-The communication between your consensus client and your execution client is going to change with the Merge. They will use this [new Engine API](https://github.com/ethereum/execution-apis/tree/main/src/engine) which will be served at a port independent from the JSON-RPC API currently in use.
+The communication between your consensus client and your execution client is going to change with the Merge. They will use this [new Engine API](https://github.com/ethereum/execution-apis/tree/main/docs/src/engine) which will be served at a port independent from the JSON-RPC API currently in use.
 
 You are likely going to need to use a new configuration option for this endpoint or at least update it on your consensus client beacon node. The default port for the Engine API is 8551 and the default port for the JSON-RPC API is 8545. You might not need to change any configuration option on your execution client, but you will likely need to modify your beacon node configuration. Here are the common values you will likely need to add or modify for each consensus client assuming your execution client engine API endpoint is at `http://localhost:8551`:
 
@@ -115,7 +115,7 @@ As usual, when changing the configuration for your consensus client, you will ne
 
 ## Configuring a JWT token file
 
-The new Engine API used to communicate between the execution client and the consensus client requires [authentication](https://github.com/ethereum/execution-apis/blob/main/src/engine/authentication.md) which is provided with a JWT token stored in a file. There are various ways to configure this. Here is a simple one.
+The new Engine API used to communicate between the execution client and the consensus client requires [authentication](https://github.com/ethereum/execution-apis/blob/main/docs/src/engine/authentication.md) which is provided with a JWT token stored in a file. There are various ways to configure this. Here is a simple one.
 
 ### Creating the JWT token file