summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-08-27 06:49:33 +0000
committerRoger Dingledine <arma@torproject.org>2006-08-27 06:49:33 +0000
commit7b3d048086c42e32884c37304e573bd08a7eb849 (patch)
treec74314a3728424b72265ee14e43c34dc7cccf015
parent94afe807ac08b646c5a568eb4336da47c68c0c35 (diff)
downloadtor-7b3d048086c42e32884c37304e573bd08a7eb849.tar.gz
tor-7b3d048086c42e32884c37304e573bd08a7eb849.zip
typo and whitespace
svn:r8237
-rw-r--r--doc/tor-spec.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index 50cbfc9e44..b59ecef278 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -292,7 +292,7 @@ when do we rotate which keys (tls, link, etc)?
other side has an obsolete certificate (organizationName equal to "Tor"
or "TOR"). If the other party presented an obsolete certificate,
we assume a v0 connection. Otherwise, both parties send VERSIONS
- cells listing all their supported versions. Upon receiving the
+ cells listing all their supported versions. Upon receiving the
other party's VERSIONS cell, the implementation begins using the
highest-valued version common to both cells. If the first cell from
the other party is _not_ a VERSIONS cell, we assume a v0 protocol.
@@ -382,7 +382,7 @@ when do we rotate which keys (tls, link, etc)?
As usual with DH, x and y MUST be generated randomly.
[
- To implement backwar-compatible version negotiation, parties MUST
+ To implement backward-compatible version negotiation, parties MUST
drop CREATE cells with all-[00] onion-skins.
]