get rid of trailing whitespace; no real changes
Roger Dingledine

Roger Dingledine commited on 2011-02-02 05:58:23
Zeige 1 geänderte Dateien mit 27 Einfügungen und 24 Löschungen.

... ...
@@ -551,13 +550,16 @@ encryption, what data you're sending to the destination.</dd>
551 550
     </p>
552 551
 
553 552
     <a id="Metrics"></a>
554
-		<h3><a class="anchor" href="#Metrics">How many people use Tor?  How many relays or exit nodes are there?</a></h3>
553
+    <h3><a class="anchor" href="#Metrics">How many people use Tor?
554
+    How many relays or exit nodes are there?</a></h3>
555 555
 
556
-		<p>All this and more about measuring Tor can be found at the <a href="https://metrics.torproject.org">Tor Metrics Portal</a>.</p>
556
+    <p>All this and more about measuring Tor can be found at the <a
557
+    href="https://metrics.torproject.org">Tor Metrics Portal</a>.</p>
557 558
     <hr>
558 559
 
559 560
     <a id="HowUninstallTor"></a>
560
-    <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall Tor?</a></h3>
561
+    <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall
562
+    Tor?</a></h3>
561 563
 
562 564
     <p>
563 565
     This depends entirely on how you installed it and which operating system you
... ...
@@ -916,31 +918,30 @@ for more information on how to remove the Tor service.
916 918
     <p>
917 919
     <em>We recommend you do not use these</em>
918 920
     &mdash; they are intended for testing and may disappear in future versions.
919
-    You get the best security that Tor can provide when you leave the route selection to Tor; 
920
-    overriding the entry / exit nodes can mess up your anonymity in ways we don't understand.
921
+    You get the best security that Tor can provide when you leave the
922
+    route selection to Tor; overriding the entry / exit nodes can mess
923
+    up your anonymity in ways we don't understand.
921 924
     </p>
922 925
     <p>
923
-    The <tt>EntryNodes</tt> and <tt>ExitNodes</tt> config options are treated as a request, 
924
-    meaning if the nodes are down or seem slow, Tor will still avoid them. 
925
-    You can make the option mandatory by setting 
926
-    <tt>StrictExitNodes 1</tt> or <tt>StrictEntryNodes 1</tt> 
926
+    The <tt>EntryNodes</tt> and <tt>ExitNodes</tt> config options are
927
+    treated as a request, meaning if the nodes are down or seem slow,
928
+    Tor will still avoid them. You can make the option mandatory by
929
+    setting <tt>StrictExitNodes 1</tt> or <tt>StrictEntryNodes 1</tt>
927 930
     &mdash; but if you do, your Tor connections will stop working
928 931
     if all of the nodes you have specified become unreachable.
929 932
     See the <a href="<page docs/documentation>#NeatLinks">Tor status pages</a>
930 933
     for some nodes you might pick.
931 934
     </p>
932 935
     <p>
933
-    Instead of <tt>$fingerprint</tt> you can also specify 
934
-    a 2 letter ISO3166 country code in curly braces 
935
-    (for example {de}), 
936
-    or an ip address pattern (for example 255.254.0.0/8), 
937
-    or a node nickname. 
938
-    Make sure there are no spaces between the commas and the list items. 
936
+    Instead of <tt>$fingerprint</tt> you can also specify a 2 letter
937
+    ISO3166 country code in curly braces (for example {de}), or an ip
938
+    address pattern (for example 255.254.0.0/8), or a node nickname. Make
939
+    sure there are no spaces between the commas and the list items.
939 940
     </p>
940 941
     <p>
941 942
     If you want to access a service directly through Tor's SOCKS interface
942
-    (eg. using ssh via connect.c), another option is to 
943
-    set up an internal mapping in your configuration file using <tt>MapAddress</tt>. 
943
+    (eg. using ssh via connect.c), another option is to set up an
944
+    internal mapping in your configuration file using <tt>MapAddress</tt>.
944 945
     See the manual page for details.
945 946
     </p>
946 947
 
... ...
@@ -1100,8 +1101,8 @@ recent logins and wondering if you actually logged in at those times.
1100 1101
     </p>
1101 1102
 
1102 1103
     <p>
1103
-    The default exit policy allows access to many popular services (e.g. web browsing), but 
1104
-    <a href="<wikifaq>#DefaultPorts">restricts</a>
1104
+    The default exit policy allows access to many popular services
1105
+    (e.g. web browsing), but <a href="<wikifaq>#DefaultPorts">restricts</a>
1105 1106
     some due to abuse potential (e.g. mail) and some since
1106 1107
     the Tor network can't handle the load (e.g. default
1107 1108
     file-sharing ports). You can change your exit policy
... ...
@@ -1205,7 +1206,8 @@ recent logins and wondering if you actually logged in at those times.
1205 1206
     <hr>
1206 1207
 
1207 1208
     <a id="WhyNotNamed"></a>
1208
-    <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3>
1209
+    <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not
1210
+    named?</a></h3>
1209 1211
 
1210 1212
     <p>
1211 1213
     We currently use these metrics to determine if your relay should be named:<br>
... ...
@@ -1378,8 +1380,8 @@ recent logins and wondering if you actually logged in at those times.
1378 1380
     <hr>
1379 1381
 
1380 1382
     <a id="Criminals"></a>
1381
-    <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals to do bad
1382
-    things?</a></h3>
1383
+    <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals
1384
+    to do bad things?</a></h3>
1383 1385
 
1384 1386
     <p>
1385 1387
     For the answer to this question and others, please see our <a
... ...
@@ -1389,8 +1391,8 @@ recent logins and wondering if you actually logged in at those times.
1389 1391
     <hr>
1390 1392
 
1391 1393
     <a id="RespondISP"></a>
1392
-    <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP about my
1393
-    exit relay?</a></h3>
1394
+    <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP
1395
+    about my exit relay?</a></h3>
1394 1396
 
1395 1397
     <p>
1396 1398
     A collection of templates for successfully responding to ISPs is <a
1397 1399