diff --git a/14_encrypted_transport.asciidoc b/14_encrypted_transport.asciidoc
index ee823b6..e859c8c 100644
--- a/14_encrypted_transport.asciidoc
+++ b/14_encrypted_transport.asciidoc
@@ -37,7 +37,7 @@ custom encrypted message transport Lightning uses, commonly referred to as
 "Brontide" (more on that later) can be dropped into any context that requires
 encrypted communication between two parties.
 
-=== The Channel Graph As Decentralized Public Key Infrastructure
+=== The Channel Graph as Decentralized Public Key Infrastructure
 
 As we learned in the chapter on multi-hop forwarding, very node has a long-term
 identity that is used as the identifier for a vertex during path finding and
@@ -67,7 +67,7 @@ Lightning network is able to significantly simply its encrypted transport
 protocol as it doesn't need to deal with all the complexities that come along
 with TLS, the Transport Layer Security protocol.
 
-=== Why Not Tls?
+=== Why Not TLS?
 
 Readers familiar with the TLS system may be wondering at this point: why wasn't
 TLS used in spite of the drawbacks of the existing PKI system? It is indeed a
@@ -137,13 +137,13 @@ during a thunderstorm when very far away.
 
 In this section we will break down the Lightning Encrypted Transport protocol and delve into the details of the cryptographic algorithms and protocol used to establish encrypted, authenticated and integrity-assured communications between peers. Feel free to skip this section if you find this level of detail daunting.
 
-==== Noise Xk: Ln's Noise Handshake
+==== Noise XK: LN's Noise Handshake
 
 The Noise protocol is extremely flexible in that it advertises several
 handshakes, each with different security and privacy properties for a would be
 protocol implementer to select from. A deep exploration of each of the
 handshakes, and their various trade-offs is out of the scope of this chapter.
-With that said, the Lighting Network uses a specific handshake referred to as
+With that said, the Lightning Network uses a specific handshake referred to as
 `Noise_XK`. The unique property provided by this handshake is "identity
 hiding": in order for a node to initiate a connection with another node, it
 must first know it's public key. Mechanically, this means that the public key