aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--address-spec.txt4
-rw-r--r--control-spec.txt4
-rw-r--r--rend-spec.txt2
3 files changed, 5 insertions, 5 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
diff --git a/control-spec.txt b/control-spec.txt
index d1cab4f..a282624 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -317,8 +317,8 @@ $Id$
address.
Example:
- C: MAPADDRESS 0.0.0.0=tor.eff.org 1.2.3.4=tor.freehaven.net
- S: 250-127.192.10.10=tor.eff.org
+ C: MAPADDRESS 0.0.0.0=torproject.org 1.2.3.4=tor.freehaven.net
+ S: 250-127.192.10.10=torproject.org
S: 250 1.2.3.4=tor.freehaven.net
{Note: This feature is designed to be used to help Tor-ify applications
diff --git a/rend-spec.txt b/rend-spec.txt
index 44aefe7..3f8b57a 100644
--- a/rend-spec.txt
+++ b/rend-spec.txt
@@ -4,7 +4,7 @@ $Id$
0. Overview and preliminaries
- Read http://tor.eff.org/doc/design-paper/tor-design.html#sec:rendezvous
+ Read https://www.torproject.org/doc/design-paper/tor-design.html#sec:rendezvous
before you read this specification. It will make more sense.
Rendezvous points provide location-hidden services (server