less should just do

README.md

@@ -12,8 +12,8 @@ A protocol for a secure message stream, after you've done a secure key exchange.
 
 - The channel must be reliable and ordered: i.e. TCP.
 - Each channel key must be an ephemeral key for a single channel and discarded when the channel ends.
-  - To get an ephemeral key for a session, you should do a secure key exchange, such as [Noise](https://noiseprotocol.org/noise.html) or [Secret Handshake](https://dominictarr.github.io/secret-handshake-paper/shs.pdf).
-  - For a duplex (bi-directional) connection between peers, you should create two secret channels (with separate keys), one in each direction.
+  - To get an ephemeral key for a session, do a secure key exchange, such as [Noise](https://noiseprotocol.org/noise.html) or [Secret Handshake](https://dominictarr.github.io/secret-handshake-paper/shs.pdf) first.
+  - For a duplex (bi-directional) connection between peers, create two secret channels (with two separate keys), one in each direction.
 - A (key, nonce) pair must NEVER be re-used.
 
 ## Security Guarantees

SPEC.md

@@ -7,7 +7,7 @@ Streaming authenticated encryption using [ChaCha20-Poly1305](https://en.wikipedi
 - The channel must be reliable and ordered: i.e. TCP.
 - Each channel key must be an ephemeral key for a single channel and discarded when the channel ends.
   - To get an ephemeral key for a session, do a secure key exchange, such as [Noise](https://noiseprotocol.org/noise.html) or [Secret Handshake](https://dominictarr.github.io/secret-handshake-paper/shs.pdf) first.
-  - For a duplex (bi-directional) connection between peers, create two secret channels (with separate keys), one in each direction.
+  - For a duplex (bi-directional) connection between peers, create two secret channels (with two separate keys), one in each direction.
 - A (key, nonce) pair must NEVER be re-used.
 
 ## Security Guarantees