cont.

documentation/docs/src/nodes/gateway.md

@@ -1 +1,12 @@
-# Gateway
+# Gateways
+
+> The gateway setup and maintenance guide has migrated to the [Operator Guides book](TO_DO).
+
+Gateways are key to both the usability of the mixnet, and the operation of the mixnet's tokenomics. They serve two main functions: 
+* (When the mixnet is no longer in 'free' mode) to act literally as gateways; checking for zkNym credentials (previously referred to as [Coconut Credentials](../bandwidth-credentials.md)) that prove a user has paid to send traffic through the mixnet. A % of the worth of these credentials will be distributed to the operator of the gateway periodically as payment for providing their service. The more credentials user clients 'spend' with them (because of their quality of service) the higher the rewards. The rest of this value will be sent to the Mixmining Pool, a pool of tokens from which `NYM` rewards are distributed to mix node operators. 
+* Act as a mailbox for connected clients. Clients create a lasting relationship with a gateway on initialisation, binding themselves to always use a particular gateway as their egress point for mixnet traffic, and always receive mixnet traffic from it (see the [mixnet traffic flow page](../architecture/traffic-flow.md) for further details). If a client is offline and the Gateway can't deliver packets addressed to it, they will hold these packets until the client comes back online. 
+
+## Further Reading 
+* TODO whitepaper section 
+* TODO loopix paper section
+* TODO blogpost 

documentation/docs/src/nodes/mixnode.md

@@ -1,4 +1,4 @@
-# Mix Node
+# Mix Nodes
 
 > The mix node setup and maintenance guide has migrated to the [Operator Guides book](TO_DO).
 
@@ -8,10 +8,13 @@ Mix nodes perform one task: receiving packets, decrypting their outer 'layer', a
 
 The aim of this mixing is to protect against timing-based deanonymisation attempts by a global adversary able to monitor the entire network with a 'God's Eye View'. 
 
+Mix nodes are rewarded according to their quality of service, and their inclusion in the active set (i.e. the nodes that mix traffic for the next epoch) affected by this (as well as their delegation-based reputation - see [further reading](#further-reading) for more on this). 
+
 ## (Coming soon) Mixing: a Step-by-Step Breakdown
 
 ## Further reading
 TODO 
-* <SECTION OF WHITEPAPER>
+* TODO SECTION OF WHITEPAPER
+* TODO LOOPIX PAPER SECTION 
 * <LINK TO CODEBASE> 
 * <ANY VIDEOS>

documentation/docs/src/nodes/validator.md

@@ -1,4 +1,4 @@
-# Validator
+# Validators
 
 > The validator setup and maintenance guide has moved to the [Operator Guides book](TO_DO).