diff --git a/specification/docs/implementation-solidity.md b/specification/docs/implementation-solidity.md
index be3390a..c2fd53d 100644
--- a/specification/docs/implementation-solidity.md
+++ b/specification/docs/implementation-solidity.md
@@ -3,8 +3,8 @@
 flowchart TD
     Homeserver[Matrix\nHomeserver]
     Contracts <-- Node.js blockchain\nclient library (ethers) --> API
-    Contracts <-- Web-based blockchain client library\n(MetaMask / Casper Wallet)--> WebApp
-    Contracts <-- Web-based blockchain client library\n(MetaMask / Casper Wallet)--> Widget
+    Contracts <-- Web-based blockchain client library\n(MetaMask)--> WebApp
+    Contracts <-- Web-based blockchain client library\n(MetaMask)--> Widget
     WebApp <-- HTTPS --> API
     Widget <-- HTTPS --> API
     Widget <-- Element-web Widget API\n(npm matrix-widget-api) --> Homeserver
diff --git a/specification/docs/system-design.md b/specification/docs/system-design.md
index eb8fc1a..ca479f1 100644
--- a/specification/docs/system-design.md
+++ b/specification/docs/system-design.md
@@ -1,5 +1,3 @@
-# System Design
-
 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. Our application uses the Client-Server protocol to communicate with a Matrix Homeserver.