aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2022-06-06 23:47:18 -0400
committerRoger Dingledine <arma@torproject.org>2022-06-06 23:47:18 -0400
commitb29e64e5617f83131bc56b5d851c4dd6c27e510d (patch)
treec59a2836a4ce546be99950dd8fa462ce2d4b463a
parentf9e386e42623d82954a3f973cf58f6987e66f8f8 (diff)
downloadtorspec-b29e64e5617f83131bc56b5d851c4dd6c27e510d.tar.gz
torspec-b29e64e5617f83131bc56b5d851c4dd6c27e510d.zip
proof-reading on prop 266
-rw-r--r--proposals/266-removing-current-obsolete-clients.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/proposals/266-removing-current-obsolete-clients.txt b/proposals/266-removing-current-obsolete-clients.txt
index bc3592b..a4cc75c 100644
--- a/proposals/266-removing-current-obsolete-clients.txt
+++ b/proposals/266-removing-current-obsolete-clients.txt
@@ -110,7 +110,7 @@ Superseded-by: 264, 272.
2.1. Dropping connections based on link protocols.
- Tor versions before before 0.2.3.6-alpha use a renegotiation-based
+ Tor versions before 0.2.3.6-alpha use a renegotiation-based
handshake instead of our current handshake. We could detect these
handshakes and close the connection at the relay side if the client
attempts to renegotiate.
@@ -137,7 +137,7 @@ Superseded-by: 264, 272.
behavior would probably be the same, though.)
If we throttled connections rather than closing them, we'd only get
- one connnection per authority per hour, but authorities would have to
+ one connection per authority per hour, but authorities would have to
keep open a potentially huge number of sockets.
2.2. Blocking circuit creation under certain circumstances
@@ -210,7 +210,7 @@ A. How to "pull the switch."
TIME 0:
Implement the client/relay side of proposal 264, backported
- to every currently existant Tor version that we still
+ to every currently extant Tor version that we still
support.
At the same time, add support for the new consensus type to
@@ -227,7 +227,7 @@ A. How to "pull the switch."
LATER:
- At some point after nearly all clients and relays hav
+ At some point after nearly all clients and relays have
upgraded to the versions released at Time 0 or later, we
could make the switchover to publishing the new consensus
type.