From 78e02ad1a129b056721f6cd3899cafbfc99ad590 Mon Sep 17 00:00:00 2001
From: zzz <zzz@i2pmail.org>
Date: Sun, 4 Dec 2022 08:47:25 -0500
Subject: [PATCH] SSU2 typo

---
 i2p2www/spec/proposals/159-ssu2.rst | 2 +-
 i2p2www/spec/ssu2.rst               | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/i2p2www/spec/proposals/159-ssu2.rst b/i2p2www/spec/proposals/159-ssu2.rst
index fad78b895..c22e773fd 100644
--- a/i2p2www/spec/proposals/159-ssu2.rst
+++ b/i2p2www/spec/proposals/159-ssu2.rst
@@ -4292,7 +4292,7 @@ Bob may perform several required checks:
 
 Unfortunately, the Router Info, even when gzip compressed in the RI block, may exceed the MTU.
 Therefore, the Session Confirmed may be fragmented across two or more packets.
-This is the ONLY case in the SSU2 protcol where an AEAD-protected payload is fragmented
+This is the ONLY case in the SSU2 protocol where an AEAD-protected payload is fragmented
 across two or more packets.
 
 The headers for each packet are constructed as follows:
diff --git a/i2p2www/spec/ssu2.rst b/i2p2www/spec/ssu2.rst
index e3329d020..180fa3f34 100644
--- a/i2p2www/spec/ssu2.rst
+++ b/i2p2www/spec/ssu2.rst
@@ -1902,7 +1902,7 @@ Bob may perform several required checks:
 
 Unfortunately, the Router Info, even when gzip compressed in the RI block, may exceed the MTU.
 Therefore, the Session Confirmed may be fragmented across two or more packets.
-This is the ONLY case in the SSU2 protcol where an AEAD-protected payload is fragmented
+This is the ONLY case in the SSU2 protocol where an AEAD-protected payload is fragmented
 across two or more packets.
 
 The headers for each packet are constructed as follows:
-- 
GitLab