diff --git a/developer-docs-site/docs/issues-and-workarounds.md b/developer-docs-site/docs/issues-and-workarounds.md
index 6e2285761fbaa..e541dcae2962e 100644
--- a/developer-docs-site/docs/issues-and-workarounds.md
+++ b/developer-docs-site/docs/issues-and-workarounds.md
@@ -41,7 +41,7 @@ If your node cannot state sync, and the logs are showing "NoAvailablePeers", it'
 
 #### Workaround
 
-You can try add some extra upstream peers for your fullnode to state sync from. See the guide [Add upstream seed peers](/nodes/full-node/fullnode-source-code-or-docker#add-upstream-seed-peers).
+You can try add some extra upstream peers for your fullnode to state sync from. See the guide [Add upstream seed peers](nodes/full-node/fullnode-source-code-or-docker.md#add-upstream-seed-peers).
 
 ### Starting a node throws a YAML-parsing error
 
@@ -68,7 +68,7 @@ The devnet validator fullnodes will accept only a maximum of connections. If Apt
 You can workaround this by:
 
 1. Checking your network configuration.
-2. Adding a seed peer to connect to, in your `public_full_node.yaml` file. See [Add upstream seed peers](/nodes/full-node/fullnode-source-code-or-docker#add-upstream-seed-peers).
+2. Adding a seed peer to connect to, in your `public_full_node.yaml` file. See [Add upstream seed peers](nodes/full-node/fullnode-source-code-or-docker.md#add-upstream-seed-peers).
 
 For example, after you add a single peer to the `seeds` section in your `public_full_node.yaml` file like below, restart the `cargo run -p ...` command: