summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-07-11 19:58:38 +0000
committerNick Mathewson <nickm@torproject.org>2008-07-11 19:58:38 +0000
commitc77d00d777c0fd80a22b99d75a8459f886cf4607 (patch)
tree9e70e1f26b80ecdb33309eba819df8f9e7b7e896
parentc3194978866ff09d7d074b7863c45e5c92eb05d5 (diff)
downloadtor-c77d00d777c0fd80a22b99d75a8459f886cf4607.tar.gz
tor-c77d00d777c0fd80a22b99d75a8459f886cf4607.zip
r16926@tombo: nickm | 2008-07-11 15:58:34 -0400
fix spelling error spotted by qbi. svn:r15846
-rw-r--r--doc/spec/proposals/150-exclude-exit-nodes.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/spec/proposals/150-exclude-exit-nodes.txt b/doc/spec/proposals/150-exclude-exit-nodes.txt
index 10f972fabc..3d2b1382e9 100644
--- a/doc/spec/proposals/150-exclude-exit-nodes.txt
+++ b/doc/spec/proposals/150-exclude-exit-nodes.txt
@@ -35,7 +35,7 @@ Security implications:
Risks:
- Use of this option can make users partitionable under certain attak
+ Use of this option can make users partitionable under certain attack
assumptions. However, ExitNodes already creates this possibility,
so there isn't much increased risk in ExcludeExitNods.