aboutsummaryrefslogtreecommitdiff
path: root/doc/spec
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-03-27 17:20:13 +0000
committerNick Mathewson <nickm@torproject.org>2008-03-27 17:20:13 +0000
commit3bc512cfe2ad26870407d1365028aa5d1c40a73a (patch)
tree8cab3edf640b62016ac9d06b0faf30c804b0cf55 /doc/spec
parent9ee7f6e826c63c1138a5e5a07f97ba13860939ea (diff)
downloadtor-3bc512cfe2ad26870407d1365028aa5d1c40a73a.tar
tor-3bc512cfe2ad26870407d1365028aa5d1c40a73a.tar.gz
r19107@catbus: nickm | 2008-03-27 13:20:09 -0400
Fix typos in proposal 131 spotted by Jens Kubieziel on or-dev. svn:r14221
Diffstat (limited to 'doc/spec')
-rw-r--r--doc/spec/proposals/131-verify-tor-usage.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/spec/proposals/131-verify-tor-usage.txt b/doc/spec/proposals/131-verify-tor-usage.txt
index bbc0b3634..268713918 100644
--- a/doc/spec/proposals/131-verify-tor-usage.txt
+++ b/doc/spec/proposals/131-verify-tor-usage.txt
@@ -125,14 +125,14 @@ Security and resiliency implications:
What attacks are possible?
- If the IP addressed used for this feature moves there will be two
+ If the IP address used for this feature moves there will be two
consequences:
- A new website at this IP address will remain inaccessible over
Tor
- Tor users who are leaking DNS will be informed that Tor is not
working, rather than that it is active but leaking DNS
We should thus attempt to find an IP address which we reasonably
- belive can remain static.
+ believe can remain static.
Open issues: