From bb89fecc9f76e3cabf2fba943e7a66afad8e4467 Mon Sep 17 00:00:00 2001
From: mikeua <2239742+mikeua@users.noreply.github.com>
Date: Tue, 13 Oct 2026 11:50:37 -0400
Subject: [PATCH] docs: fix broken links

- sharding.md linked config.md#configuring-ethereum-providers; that
  section is now "Configuring Chains" (#configuring-chains).
- implementation/README.md linked ./add-chain.md, which doesn't exist,
  and ./dump.md, which lives one level up at docs/dump.md.
---
 docs/implementation/README.md | 3 +--
 docs/sharding.md              | 2 +-
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/docs/implementation/README.md b/docs/implementation/README.md
index d54a39babbe..44bcba3f044 100644
--- a/docs/implementation/README.md
+++ b/docs/implementation/README.md
@@ -8,6 +8,5 @@ the code should go into comments.
 * [Schema Generation](./schema-generation.md)
 * [Time-travel Queries](./time-travel.md)
 * [SQL Query Generation](./sql-query-generation.md)
-* [Adding support for a new chain](./add-chain.md)
 * [Pruning](./pruning.md)
-* [Dump Format](./dump.md)
+* [Dump Format](../dump.md)
diff --git a/docs/sharding.md b/docs/sharding.md
index de2015be22a..37df1105980 100644
--- a/docs/sharding.md
+++ b/docs/sharding.md
@@ -67,7 +67,7 @@ Data can be added to new shards by setting up [deployment
 rules](./config.md#controlling-deployment) that send certain subgraphs to
 the new shard. It is also possible to store the block cache for new chains
 in a new shard by setting the `shard` attribute of the [chain
-definition](./config.md#configuring-ethereum-providers)
+definition](./config.md#configuring-chains)
 
 With shards, there are many possibilities how data can be split between
 them. One possible setup is: