aboutsummaryrefslogtreecommitdiff
path: root/address-spec.txt
diff options
context:
space:
mode:
authorAndrew Lewman <andrew@torproject.org>2007-10-29 01:08:22 +0000
committerAndrew Lewman <andrew@torproject.org>2007-10-29 01:08:22 +0000
commit3a34db931feb8932c051afb7c6c07b832ce15574 (patch)
treecc6a5c7535437e43c18fad53c81276462b32626e /address-spec.txt
parent826e0223888a8efee1ad12def6a62fd4c97c3872 (diff)
downloadtorspec-3a34db931feb8932c051afb7c6c07b832ce15574.tar.gz
torspec-3a34db931feb8932c051afb7c6c07b832ce15574.zip
And more places with the wrong url, now updated.
svn:r12267
Diffstat (limited to 'address-spec.txt')
-rw-r--r--address-spec.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/address-spec.txt b/address-spec.txt
index 92651a0..966f34c 100644
--- a/address-spec.txt
+++ b/address-spec.txt
@@ -6,8 +6,8 @@ $Id$
1. Overview
Most of the time, Tor treats user-specified hostnames as opaque: When the
- user connects to tor.eff.org, Tor picks an exit node and uses that node to
- connect to "tor.eff.org". Some hostnames, however, can be used to override
+ user connects to www.torproject.org, Tor picks an exit node and uses that node to
+ connect to "www.torproject.org". Some hostnames, however, can be used to override
Tor's default behavior and circuit-building rules.
These hostnames can be passed to Tor as the address part of a SOCKS4a or