diff --git a/specification/docs/requirements.md b/specification/docs/requirements.md
index 8625e4e..1d3ddef 100644
--- a/specification/docs/requirements.md
+++ b/specification/docs/requirements.md
@@ -233,4 +233,4 @@ The Rollup contract can be thought of as a specialized form of Work Contract (WS
 
     1. The DAO members should stake against the VP, in order to punish the batch worker for failing to complete their work
 
-In this requirements section, we omit any details of the mechanisms for implementing the necessary off-chain validation that leads to the production and verification of the Rollup Post. We will provide those details in the [System Design](./system-design/index.md) section.
\ No newline at end of file
+In this requirements section, we omit any details of the mechanisms for implementing the necessary off-chain validation that leads to the production and verification of the Rollup Post. We will provide those details in the [System Design](./system-design.md) section.
\ No newline at end of file
diff --git a/specification/docs/system-design.md b/specification/docs/system-design.md
index fcdaf27..07012c5 100644
--- a/specification/docs/system-design.md
+++ b/specification/docs/system-design.md
@@ -1,6 +1,6 @@
 # System Design
 
-In the [Requirements](../requirements.md) section, we identified the need for the following smart contracts: Reputation, Bench, Forum, Work, Proposal, and Rollup.
+In the [Requirements](./requirements.md) section, we identified the need for the following smart contracts: Reputation, Bench, Forum, Work, Proposal, and Rollup.
 
 We also identified the need for a mechanism for coordinating Rollup Post validation. To address this need, we introduce [Matrix](https://matrix.org), a federated messaging protocol with multiple implementations. Our application uses the Client-Server protocol to communicate with a Matrix Homeserver.
 
@@ -137,7 +137,7 @@ Rather than submit every Post on-chain and conduct every Validation Pool on-chai
 
 With this Rollup Post, we have the opportunity to attribute credit to multiple authors, with a weight assigned to each author. We can express this weight as parts per million (PPM), for a balance between numerical precision, and ease of visual recognition.
 
-The Rollup Post can weight authorship in accordance with the off-chain Validation Pools that have taken place. The off-chain system can fully model the Forum and Bench outlined in the [Requirements](../requirements.md) section. For demonstration purposes, our prototype makes some simplifying assumptions. Work Evidence Posts (WEV) are assumed to contain no references to prior Posts. In reality, we want WEV to be able to reference prior Posts, such as those representing policies of the DAO, prior work by other DAO members, prior art outside the DAO, and so on. So, a proper implementation of this system should account for these references, just as the Forum contract must.
+The Rollup Post can weight authorship in accordance with the off-chain Validation Pools that have taken place. The off-chain system can fully model the Forum and Bench outlined in the [Requirements](./requirements.md) section. For demonstration purposes, our prototype makes some simplifying assumptions. Work Evidence Posts (WEV) are assumed to contain no references to prior Posts. In reality, we want WEV to be able to reference prior Posts, such as those representing policies of the DAO, prior work by other DAO members, prior art outside the DAO, and so on. So, a proper implementation of this system should account for these references, just as the Forum contract must.
 
 To achieve the Rollup requirements, the contract must do the following: