aboutsummaryrefslogtreecommitdiff
path: root/proposals/291-two-guard-nodes.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2022-10-24 04:38:36 -0400
committerRoger Dingledine <arma@torproject.org>2022-10-24 04:38:36 -0400
commit78a1722164337e9f11078c8d1dca88020c8e0520 (patch)
treea78497842d5dfb68519d775996aebebba30f40bc /proposals/291-two-guard-nodes.txt
parente5cd03e38e25ddb10f3138ac25ec684890f97f00 (diff)
downloadtorspec-78a1722164337e9f11078c8d1dca88020c8e0520.tar.gz
torspec-78a1722164337e9f11078c8d1dca88020c8e0520.zip
fix typo in proposal 291
Diffstat (limited to 'proposals/291-two-guard-nodes.txt')
-rw-r--r--proposals/291-two-guard-nodes.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/291-two-guard-nodes.txt b/proposals/291-two-guard-nodes.txt
index 43885e3..a9554c6 100644
--- a/proposals/291-two-guard-nodes.txt
+++ b/proposals/291-two-guard-nodes.txt
@@ -154,7 +154,7 @@ Status: Needs-Revision
However, while removing path restrictions will solve the immediate
problem, it will not address other instances where Tor temporarily opts
- use a second guard due to congestion, OOM, or failure of its primary
+ to use a second guard due to congestion, OOM, or failure of its primary
guard, and we're still running into bugs where this can be adversarially
controlled or just happen randomly[5].