[or-cvs] commit tweaks to the tor legal faq

[arma@xxxxxxxx (Roger Dingledine)]

Update of /home2/or/cvsroot/website/eff
In directory moria.mit.edu:/home2/arma/work/onion/cvs/website/eff

Modified Files:
	tor-legal-faq.html 
Log Message:
commit tweaks to the tor legal faq


Index: tor-legal-faq.html
===================================================================
RCS file: /home2/or/cvsroot/website/eff/tor-legal-faq.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- tor-legal-faq.html	2 Jan 2005 07:15:13 -0000	1.3
+++ tor-legal-faq.html	5 Jan 2005 01:05:34 -0000	1.4
@@ -44,18 +44,19 @@
 
 <h2>Legal FAQ for Tor Server Operators</h2>
 <hr />
-<p>FAQ written by <a href="http://www.eff.org/";>The Electronic Frontier
-Foundation (EFF)</a>. Last updated 23 Dec 2004.</p>
+<p>FAQ written by the Electronic Frontier
+Foundation (<a href="http://www.eff.org/";>EFF</a>). Last updated 23 Dec 2004.</p>
 
 <p><strong>NOTE:</strong> This FAQ is for informational purposes only
 and does not constitute legal advice.  EFF has not analyzed any
-particular factual situation or laws in drafting this FAQ, but rather
-has tried to give a general description of the legal issues surrounding
-Tor for a general audience.  Different factual situations and different
-legal jurisdictions will result in different answers.  Therefore, please
-do not act on this information alone; instead seek a complete review of
-your situation with a lawyer licensed to practice in your jurisdiction
-if you have any specific issues or questions.</p>
+particular factual situation or laws in drafting this FAQ. Our aim is
+to provide a general description of the legal issues surrounding
+Tor.  Different factual situations and different legal jurisdictions will
+result in different answers to a number of questions.  Therefore, please
+do not act on this information alone; if you have any
+specific legal problems, issues, or questions, seek a complete review of
+your situation with a lawyer licensed to practice in your jurisdiction.
+</p>
 
 <p>Also, if you received this document from anywhere besides <a
 href="http://tor.eff.org/eff/legal-faq.html";>http://tor.eff.org/eff/legal-faq.html</a>,
@@ -74,14 +75,14 @@
 infringement?</h2>
 
 <p><strong>No.</strong> Tor has been developed to be a tool for free
-speech, privacy and human rights.  It is not a tool designed or intended
+speech, privacy, and human rights.  It is not a tool designed or intended
 to be used to break the law, either by Tor users or Tor server
 operators.</p>
 
 <p>We further recommend that you not keep any potentially illegal files
-on the same machine you use for Tor, nor use that machine for any
-illegal purpose.  Although no Tor server has ever been seized or
-subpoenaed, the future possibility cannot be ruled out and if that
+on the same machine you use for Tor, nor use that machine for any illegal
+purpose.  Although no Tor server has ever been seized, nor any server
+operator subpoenaed, the future possibility cannot be ruled out. If that
 happens, you will want your machine to be clean.</p>
 
 
@@ -89,7 +90,7 @@
 server?</h2>
 
 <p><strong>No.</strong> All new technologies create legal uncertainties,
-and Tor is no different.  Presently, no court has ever considered any
+and Tor is no exception to the rule. Presently, no court has ever considered any
 case involving the Tor technology, and we therefore cannot guarantee
 that you will never face any legal liability as a result of running a
 Tor server.</p>
@@ -154,7 +155,7 @@
 server?</h2>
 
 <p><strong>No.</strong> You are technically capable of monitoring or
-logging plaintext that exits your node, if you modify the Tor source
+logging plaintext that exits your node if you modify the Tor source
 code or install additional software to enable such snooping.  However,
 Tor server operators in the U.S. can create legal and possibly even
 criminal liability for themselves under state or federal wiretap laws if
@@ -184,7 +185,7 @@
 download and reproduced below:</p>
 
 <p>Copyright (c) 2001-2004, Roger Dingledine<br />
-Copyright (c) 2004, Roger Dingledine, Nick Mathewson</p>
+Copyright (c) 2004-2005, Roger Dingledine, Nick Mathewson</p>
 
 <p>Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are