diff --git a/README.md b/README.md
index 3a552495ad..0ebc6a4f49 100644
--- a/README.md
+++ b/README.md
@@ -63,7 +63,7 @@ The celestia-node public API is documented [here](https://node-rpc-docs.celestia
 - **Full** nodes - fully reconstruct and store blocks by sampling the DA network for shares
 - **Light** nodes - verify the availability of block data by sampling the DA network for shares
 
-More information can be found [here](https://github.com/celestiaorg/celestia-node/blob/main/docs/adr/adr-003-march2022-testnet.md#legend).
+More information can be found [here](/docs/adr/adr-003-march2022-testnet.md#legend).
 
 ## Run a node
 
diff --git a/docs/adr/adr-010-incentivized-testnet-monitoring.md b/docs/adr/adr-010-incentivized-testnet-monitoring.md
index 2d197bb920..5f07365e7c 100644
--- a/docs/adr/adr-010-incentivized-testnet-monitoring.md
+++ b/docs/adr/adr-010-incentivized-testnet-monitoring.md
@@ -279,7 +279,7 @@ In the case where a node operator wants to send data from celestia-node to an OT
             key_file: /home/cert-key.pem
     ```
 
-1. Ensure that celestia-node runs with a TLS config that contains the Root CA created in step 1. See [sample code](https://github.com/celestiaorg/celestia-node/blob/rp/tracing-with-tls/cmd/flags_misc.go#L173-L199)
+1. Ensure that celestia-node runs with a TLS config that contains the Root CA created in step 1. See [sample code](/rp/tracing-with-tls/cmd/flags_misc.go#L173-L199)
 
 #### What are the resource requirements of OTEL collector?