diff --git a/content/docs/rfcs/1/README.md b/content/docs/rfcs/1/README.md
index 9e038cd..4f362e1 100644
--- a/content/docs/rfcs/1/README.md
+++ b/content/docs/rfcs/1/README.md
@@ -31,7 +31,7 @@ You should have received a copy of the GNU General Public License along with thi
 
 ## Change Process
 
-This document is governed by the [1/COSS](../1/README.md) (COSS).
+This document is governed by the [1/COSS](spec/1) (COSS).
 
 ## Language
 
diff --git a/content/docs/rfcs/3/README.md b/content/docs/rfcs/3/README.md
index b9e8fb1..03a6d4a 100644
--- a/content/docs/rfcs/3/README.md
+++ b/content/docs/rfcs/3/README.md
@@ -204,7 +204,7 @@ in time.
 
 ### Interaction with MVDS
 
-[vac.mvds.Message](mvds.md#payloads) payloads are the only payloads that MUST be uploaded. Other messages types MAY be uploaded, depending on the implementation.
+[vac.mvds.Message](/spec/2#payloads) payloads are the only payloads that MUST be uploaded. Other messages types MAY be uploaded, depending on the implementation.
 
 ## Acknowledgments
 
diff --git a/content/docs/rfcs/4/README.md b/content/docs/rfcs/4/README.md
index 48f4d66..203019b 100644
--- a/content/docs/rfcs/4/README.md
+++ b/content/docs/rfcs/4/README.md
@@ -9,7 +9,7 @@ contributors:
   - Andrea Maria Piana <andreap@status.im>
 ---
 
-In this specification, we describe a method to construct message history that will aid the consistency guarantees of [2/MVDS](specs/2). Additionally, we explain how data sync can be used for more lightweight messages that do not require full synchronization.
+In this specification, we describe a method to construct message history that will aid the consistency guarantees of [2/MVDS](/spec/2). Additionally, we explain how data sync can be used for more lightweight messages that do not require full synchronization.
 
 ## Motivation
 
@@ -28,7 +28,7 @@ message Metadata {
 }
 ```
 
-Nodes MAY transmit a `Metadata` message by extending the MVDS [message](specs/2#payloads) with a `metadata` field.
+Nodes MAY transmit a `Metadata` message by extending the MVDS [message](/spec/2#payloads) with a `metadata` field.
 
 ```diff
 message Message {
@@ -43,14 +43,14 @@ message Message {
 
 | Name                   |   Description                                                                                                                    |
 | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| `parents`               |   list of parent [`message identifier`s](specs/2#payloads) for the specific message. |            
+| `parents`               |   list of parent [`message identifier`s](/spec/2#payloads) for the specific message. |            
 | `ephemeral`         |   indicates whether a message is ephemeral or not.                                                             |
 
 ## Usage
 
 ### `parents`
 
-This field contains a list of parent [`message identifier`s](specs/2#payloads) for the specific message. It MUST NOT contain any messages as parent whose `ack` flag was set to `false`. This establishes a directed acyclic graph (DAG)[^1] of persistent messages.
+This field contains a list of parent [`message identifier`s](/spec/2#payloads) for the specific message. It MUST NOT contain any messages as parent whose `ack` flag was set to `false`. This establishes a directed acyclic graph (DAG)[^1] of persistent messages.
 
 Nodes MAY buffer messages until dependencies are satisfied for causal consistency[^2], they MAY also pass the messages straight away for eventual consistency[^3].