From 6ae97a5cfd1985ebb94db2f2e77a6696c3a24494 Mon Sep 17 00:00:00 2001
From: ion- <itornaza@gmail.com>
Date: Tue, 18 Jun 2024 19:25:39 +0300
Subject: [PATCH] Fix minor typos

---
 04-Protocol-Security.md | 2 +-
 10-Discussion.md        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/04-Protocol-Security.md b/04-Protocol-Security.md
index 3085ec5..69eedf7 100644
--- a/04-Protocol-Security.md
+++ b/04-Protocol-Security.md
@@ -45,7 +45,7 @@ encoding as defined in BIP 340.<sup>[3](#reference-3)</sup>.
 2. When sharing keys during the handshake, whether in plain text or encrypted,
 we use the 64 byte ElligatorSwift x-only encoding as defined in BIP324<sup>[7](#reference-7)</sup> under "ElligatorSwift encoding of curve X coordinates". This encoding uses 64-bytes instead of 32-bytes in order to produce a
 pseudo-random bytesteam. This is useful because the protocol handshake starts with
-each side sending ther public key in plain text. Additionally the use of X-only
+each side sending their public key in plain text. Additionally the use of X-only
 ElligatorSwift ECDH removes the need to grind or negate private keys.
 
 3. The Authority public key is base58-check encoded as described in 4.7.
diff --git a/10-Discussion.md b/10-Discussion.md
index 483fe21..9ce8a54 100644
--- a/10-Discussion.md
+++ b/10-Discussion.md
@@ -70,7 +70,7 @@ The proxy:
 ...
 
 
-## 10.5. FAQ
+## 10.5 FAQ
 
 
 ### 10.5.1 Why is the protocol binary?