aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2004-05-18 15:50:26 +0000
committerNick Mathewson <nickm@torproject.org>2004-05-18 15:50:26 +0000
commit10d52c46cba55b74921e1788afd6bf8c44b779b6 (patch)
tree7983924c14943dc7f978db8ca3510151136bba8c
parent7511fbf993271312875d0648166694cc58117060 (diff)
downloadtor-10d52c46cba55b74921e1788afd6bf8c44b779b6.tar.gz
tor-10d52c46cba55b74921e1788afd6bf8c44b779b6.zip
Fix a spelling error
svn:r1890
-rw-r--r--doc/tor-design.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tor-design.tex b/doc/tor-design.tex
index 89399c6bb2..0a27a92525 100644
--- a/doc/tor-design.tex
+++ b/doc/tor-design.tex
@@ -1380,7 +1380,7 @@ simplifying assumption that all participants agree on the set of
directory servers. Second, while Mixminion needs to predict node
behavior, Tor only needs a threshold consensus of the current
state of the network. Third, we assume that we can fall back to the
-human administrators to discover and resolve problems when a concensus
+human administrators to discover and resolve problems when a consensus
directory cannot be reached. Since there are relatively few directory
servers (currently 3, but we expect as many as 9 as the network scales),
we can afford operations like broadcast to simplify the consensus-building