[tor-commits] [torspec/master] fix a typo twice

[arma at torproject.org]

commit c95c1bb1ed18447ec679d3d19ca90a073108dcf9
Author: Roger Dingledine <arma at torproject.org>
Date:   Mon Aug 6 15:54:27 2018 -0400

    fix a typo twice
---
 proposals/224-rend-spec-ng.txt | 2 +-
 rend-spec-v3.txt               | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt
index b2c0fea..1dfe87b 100644
--- a/proposals/224-rend-spec-ng.txt
+++ b/proposals/224-rend-spec-ng.txt
@@ -1655,7 +1655,7 @@ Table of contents:
    If the cell is not a replay, it decrypts the ENCRYPTED field,
    establishes a shared key with the client, and authenticates the whole
    contents of the cell as having been unmodified since they left the
-   client. There may be multiple ways of decrypting the ENCRYTPED field,
+   client. There may be multiple ways of decrypting the ENCRYPTED field,
    depending on the chosen type of the encryption key. Requirements for
    an introduction handshake protocol are described in
    [INTRO-HANDSHAKE-REQS]. We specify one below in section
diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt
index 705dc0d..dbd3103 100644
--- a/rend-spec-v3.txt
+++ b/rend-spec-v3.txt
@@ -1680,7 +1680,7 @@ Table of contents:
    If the cell is not a replay, it decrypts the ENCRYPTED field,
    establishes a shared key with the client, and authenticates the whole
    contents of the cell as having been unmodified since they left the
-   client. There may be multiple ways of decrypting the ENCRYTPED field,
+   client. There may be multiple ways of decrypting the ENCRYPTED field,
    depending on the chosen type of the encryption key. Requirements for
    an introduction handshake protocol are described in
    [INTRO-HANDSHAKE-REQS]. We specify one below in section