[tor-commits] r26927: {website} Reworded the faq's no filters explanation. (website/trunk/docs/en)

[Matt Pagan]

Author: mttp
Date: 2014-08-22 11:52:13 +0000 (Fri, 22 Aug 2014)
New Revision: 26927

Modified:
   website/trunk/docs/en/faq.wml
Log:
Reworded the faq's no filters explanation.



Modified: website/trunk/docs/en/faq.wml
===================================================================
--- website/trunk/docs/en/faq.wml	2014-08-21 14:52:07 UTC (rev 26926)
+++ website/trunk/docs/en/faq.wml	2014-08-22 11:52:13 UTC (rev 26927)
@@ -2327,21 +2327,24 @@
 
     <a id="OutgoingFirewall"></a>
     <h3><a class="anchor" href="#OutgoingFirewall">How should I configure
-    my outgoing filters?</a></h3>
+    the outgoing filters on my relay?</a></h3>
 
     <p>
-    Tor design assumes that any relay can reach every other relays. So
-    all <em>outgoing</em> connections must be allowed.
+    All <em>outgoing</em> connections must be allowed, so that each relay can 
+    communicate with every other relay.
     </p>
     <p>
-    Tor is promoting free network access without interference.
-    Exit nodes must not attempt to filter any traffic coming from the
-    Tor network. Selecting outgoing traffic is likely to forfeit the
-    protections usually given to <em>common carriers</em> in many
-    jurisdictions.
+    In many jurisdictions, Tor relay operators are legally protected by the 
+    same <em>common carrier</em> regulations that prevent internet service 
+    providers from being held liable for third-party content that passes 
+    through their network. Exit relays that filter some traffic would 
+    likely forfeit those protections. 
     </p>
     <p>
-    Exit nodes which filter traffic will get the <a
+    Tor promotes free network access without interference. 
+    Exit relays must not filter the traffic 
+    that passes through them to the internet. 
+    Exit relays found to be filtering traffic will get the <a 
     href="#WhatIsTheBadExitFlag">BadExit</a> flag once detected.
     </p>