[tor-commits] [stem/master] Update links in tutorials

[atagar@xxxxxxxxxxxxxx]

commit 947c0c115085120181fd8c456238249a2f13f344
Author: hannelorestetx <hannelores.x@xxxxxxxxxxx>
Date:   Tue Dec 10 18:12:28 2019 -0500

    Update links in tutorials
---
 docs/tutorials/east_of_the_sun.rst             | 3 +--
 docs/tutorials/mirror_mirror_on_the_wall.rst   | 4 ++--
 docs/tutorials/the_little_relay_that_could.rst | 2 +-
 3 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/docs/tutorials/east_of_the_sun.rst b/docs/tutorials/east_of_the_sun.rst
index fe09c4d3..4303170f 100644
--- a/docs/tutorials/east_of_the_sun.rst
+++ b/docs/tutorials/east_of_the_sun.rst
@@ -73,8 +73,7 @@ function provides an easy method for accessing this information, with a few
 caveats...
 
 * Connection resolvers are platform specific. We `support several
-  <../api/util/connection.html#stem.util.connection.Resolver>`_ but not not
-  all, most notably Windows (:trac:`9850`).
+  <../api/util/connection.html#stem.util.connection.Resolver>`_ platforms but not all.
 
 * By default Tor runs with a feature called **DisableDebuggerAttachment**. This
   prevents debugging applications like gdb from analyzing Tor unless it is run
diff --git a/docs/tutorials/mirror_mirror_on_the_wall.rst b/docs/tutorials/mirror_mirror_on_the_wall.rst
index f16df19b..0d8b0b57 100644
--- a/docs/tutorials/mirror_mirror_on_the_wall.rst
+++ b/docs/tutorials/mirror_mirror_on_the_wall.rst
@@ -80,7 +80,7 @@ easy as...
 
 **Please remember that Tor is a shared resource!** If you're going to
 contribute much load please consider `running a relay
-<https://www.torproject.org/docs/tor-doc-relay.html.en>`_ to offset your use.
+<https://community.torproject.org/relay/>`_ to offset your use.
 
 **ORPorts** communicate through the `tor protocol
 <https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt>`_, and can be
@@ -144,7 +144,7 @@ against Tor you may want to set some of the following in your `torrc
 <https://www.torproject.org/docs/faq.html.en#torrc>`_. Keep in mind that these
 add a small burden to the network, so don't set them in a widely distributed
 application. And, of course, please consider `running Tor as a relay
-<https://www.torproject.org/docs/tor-doc-relay.html.en>`_ so you give back to
+<https://community.torproject.org/relay/>`_ so you give back to
 the network!
 
 .. code-block:: lighttpd
diff --git a/docs/tutorials/the_little_relay_that_could.rst b/docs/tutorials/the_little_relay_that_could.rst
index 57782d23..34bfe9e0 100644
--- a/docs/tutorials/the_little_relay_that_could.rst
+++ b/docs/tutorials/the_little_relay_that_could.rst
@@ -2,7 +2,7 @@ The Little Relay that Could
 ===========================
 
 Let's say you just set up your very first `Tor relay
-<https://www.torproject.org/docs/tor-doc-relay.html.en>`_ (thank you!), and now
+<https://community.torproject.org/relay/>`_ (thank you!), and now
 you want to write a script that tells you how much it is being used.
 
 First, for any script to talk with your relay it will need to have a control

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits