From fa6b52201eb4ed7459886a496da34b37366e0fb2 Mon Sep 17 00:00:00 2001
From: AlienTornadosaurusHex <>
Date: Thu, 8 Jun 2023 18:25:58 +0000
Subject: [PATCH 1/3] locking must show up

Signed-off-by: AlienTornadosaurusHex <>
---
 SUMMARY.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SUMMARY.md b/SUMMARY.md
index 4222f1f..7f13263 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -6,7 +6,7 @@
 * [How does it work?](general/how-does-it-work.md)
 * [TORN](general/token/index.md)
 * [Governance](general/community/governance.md)
-* [Staking](general/token/staking.md)
+* [Locking](general/token/locking.md)
 * [Contributing](general/community/contributing.md)
 
 ## Guides

From ae22f7450ac3158309a8dac78919fa804c947274 Mon Sep 17 00:00:00 2001
From: AlienTornadosaurusHex <>
Date: Thu, 8 Jun 2023 18:29:17 +0000
Subject: [PATCH 2/3] formatting

Signed-off-by: AlienTornadosaurusHex <>
---
 general/guides/local-ui.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/general/guides/local-ui.md b/general/guides/local-ui.md
index 1f39994..fbb3567 100644
--- a/general/guides/local-ui.md
+++ b/general/guides/local-ui.md
@@ -11,6 +11,7 @@ _If you have privacy concerns about using this extension in this tutorial, you [
 For this part you'll need to be able to open .zip files, most operating systems allow this. Head to either the Nova or Classic release page on the community git to download the static files. 
 
 Nova: https://git.tornado.ws/tornadocash/nova-ui-minified/releases
+
 Classic: https://git.tornado.ws/tornadocash/classic-ui/releases
 
 Click the version named zip file download option to download the zip file, as seen below. It should download locally to your machine. 

From f80f0cf0cdda1a4165a97b9993c5014eead76022 Mon Sep 17 00:00:00 2001
From: AlienTornadosaurusHex <>
Date: Thu, 8 Jun 2023 19:53:18 +0000
Subject: [PATCH 3/3] change back naming

Signed-off-by: AlienTornadosaurusHex <>
---
 SUMMARY.md                               | 2 +-
 general/token/{locking.md => staking.md} | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)
 rename general/token/{locking.md => staking.md} (99%)

diff --git a/SUMMARY.md b/SUMMARY.md
index 7f13263..4222f1f 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -6,7 +6,7 @@
 * [How does it work?](general/how-does-it-work.md)
 * [TORN](general/token/index.md)
 * [Governance](general/community/governance.md)
-* [Locking](general/token/locking.md)
+* [Staking](general/token/staking.md)
 * [Contributing](general/community/contributing.md)
 
 ## Guides
diff --git a/general/token/locking.md b/general/token/staking.md
similarity index 99%
rename from general/token/locking.md
rename to general/token/staking.md
index eb4dd60..5a76fb0 100644
--- a/general/token/locking.md
+++ b/general/token/staking.md
@@ -1,5 +1,7 @@
 # Locking in Governance
 
+### Why? (See below on how to lock)
+
 All Governance systems converge towards the same pattern of consensus systems based on some form of pluralism-based voting. This is for the reason, that large-scale coordination problems can only be resolved by giving "users" or "nodes" or "validators" (however you want to call it) an incentive to cooperate, and then bind that incentive within a ruleset which ultimately the "users/nodes/validators" will prefer because it encourages the stability of the system which actually supplies them the incentives, meaning that it economically guarantees them future income.
 
 For this reason, since the prime directive of the Governance "community" surrounding Tornado Cash is ensuring protocol and service stability, mechanisms must exist by which Governance can incentivize "users/validators/nodes" to configure a system around the core protocol contracts, which must act as a bridge between them and users wanting to interface with the protocol. Specifically, this is necessary due to the fee dilemma which has been mentioned in the guide for relayers, which states that a third party must be providing ether on the withdrawal side of a run through Tornado.