diff --git a/core/node/db_pruner/README.md b/core/node/db_pruner/README.md
index ee1317d01e46..eaf8caa27da7 100644
--- a/core/node/db_pruner/README.md
+++ b/core/node/db_pruner/README.md
@@ -10,7 +10,7 @@ There are two types of objects that are not fully cleaned:
 
 ## Pruning workflow
 
-_(See [node docs](../../../docs/guides/external-node/08_pruning.md) for a high-level pruning overview)_
+_(See [node docs](https://matter-labs.github.io/zksync-era/core/latest/guides/external-node/08_pruning.html) for a high-level pruning overview)_
 
 There are two phases of pruning an L1 batch, soft pruning and hard pruning. Every batch that would have its records
 removed if first _soft-pruned_. Soft-pruned batches cannot safely be used. One minute (this is configurable) after soft
diff --git a/docs/src/announcements/attester_commitee.md b/docs/src/announcements/attester_commitee.md
index 148e51a4f976..556245b6fd12 100644
--- a/docs/src/announcements/attester_commitee.md
+++ b/docs/src/announcements/attester_commitee.md
@@ -36,7 +36,7 @@ Participants can leave the committee at any time.
 The only action that is required to participate is to share your attester public key with the Main Node operator (by
 opening an issue in this repo or using any other communication channel). You can find it in the comment in the
 `consensus_secrets.yaml` file (that was - in most cases - generated by the tool described
-[here](https://github.com/matter-labs/zksync-era/blob/main/docs/guides/external-node/10_decentralization.md#generating-secrets))
+[here](https://matter-labs.github.io/zksync-era/core/latest/guides/external-node/10_decentralization.html)
 
 > [!WARNING]
 >
diff --git a/docs/src/guides/external-node/03_running.md b/docs/src/guides/external-node/03_running.md
index caa528238aea..93be44630d56 100644
--- a/docs/src/guides/external-node/03_running.md
+++ b/docs/src/guides/external-node/03_running.md
@@ -44,7 +44,7 @@ Besides running Postgres, you are expected to have a DB dump from a correspondin
 `pg_restore -O -C <DUMP_PATH> --dbname=<DB_URL>`.
 
 You can also refer to
-[ZKsync Node configuration management blueprint](https://github.com/matter-labs/zksync-era/blob/main/docs/guides/external-node/00_quick_start.md#advanced-setup)
+[ZKsync Node configuration management blueprint](https://matter-labs.github.io/zksync-era/core/latest/guides/external-node/00_quick_start.html)
 for advanced DB instance configurations.
 
 [host_docker_internal](https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host)
diff --git a/zkstack_cli/README.md b/zkstack_cli/README.md
index e81165088218..fab5b4d51969 100644
--- a/zkstack_cli/README.md
+++ b/zkstack_cli/README.md
@@ -5,7 +5,7 @@ Commands are interactive but can also accept arguments via the command line.
 
 ### Dependencies
 
-Follow [these instructions](https://github.com/matter-labs/zksync-era/blob/main/docs/guides/setup-dev.md) to set up
+Follow [these instructions](https://matter-labs.github.io/zksync-era/core/latest/guides/setup-dev.html) to set up
 dependencies on your machine. Ignore the Environment section for now.
 
 ### Installation