commit b42016e8ae7826b5ac457ec4d9e213cca3662394
Author: nusenu <nusenu-github(a)riseup.net>
Date: Sat Feb 10 16:55:34 2018 +0000
FAQ (relay section): link to new relay guide; link to obfs4 bridge guide
---
docs/en/faq.wml | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/docs/en/faq.wml b/docs/en/faq.wml
index a5c3038d..d96f33c3 100644
--- a/docs/en/faq.wml
+++ b/docs/en/faq.wml
@@ -2556,7 +2556,7 @@ relay or bridge relay?</a></h3>
<p><a href="<page docs/bridges>">Bridge relays</a> (or "bridges" for
short)
- are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't
+ are <a href="<wiki>TorRelayGuide">Tor relays</a> that aren't
listed in the public Tor directory.
That means that ISPs or governments trying to block access to the
Tor network can't simply block all bridges.
@@ -2586,9 +2586,10 @@ lots
of bandwidth, you should definitely run a normal relay.
If you're willing
to <a href="#ExitPolicies">be an exit</a>, you should definitely
- run a normal relay, since we need more exits. If you can't be an
- exit and only have a little bit of bandwidth, be a bridge. Thanks
- for volunteering!
+ run an exit relay, since we need more exits. If you can't be an
+ exit and only have a little bit of bandwidth, setup an
+ <a href="<page docs/pluggable-transports>#operator">obfs4 bridge</a>.
+ Thanks for volunteering!
</p>
<hr>