Browse code

normalize whitespace

no actual content changes

Roger Dingledine authored on19/04/2018 00:05:07
Showing1 changed files
... ...
@@ -27,7 +27,7 @@
27 27
     <h3><a class="anchor" href="#support">Support</a></h3>
28 28
 
29 29
     <!--
30
-     <p><i>help@rt.torproject.org</i> is the address to use for
30
+    <p><i>help@rt.torproject.org</i> is the address to use for
31 31
     questions about all things Tor, volunteering, and offering
32 32
     resources. This is best effort service with no guarantees. We
33 33
     generally respond within 48 hours. For support in other languages,
... ...
@@ -84,49 +84,49 @@
84 84
     <a id="twitter"></a>
85 85
     <h3><a class="anchor" href="#twitter">Twitter</a></h3>
86 86
     <p>Follow us on Twitter:
87
-	<ul>
88
-	  <li>English account: <a href="https://twitter.com/TorProject">@TorProject</a></li>
89
-    	  <li>Farsi (Persian) account: <a href="https://twitter.com/torproject_fa">@TorProject_fa</a></li>
90
-	</ul>
87
+    <ul>
88
+      <li>English account: <a href="https://twitter.com/TorProject">@TorProject</a></li>
89
+      <li>Farsi (Persian) account: <a href="https://twitter.com/torproject_fa">@TorProject_fa</a></li>
90
+    </ul>
91
+    </p>
92
+
93
+    <a id="bugs"></a>
94
+    <h3><a class="anchor" href="#bugs">Bug Tracker</a></h3>
95
+    <p>You can report bugs other than <a href="#security">security
96
+    issues</a> using our <a href="https://trac.torproject.org/projects/tor"
97
+    >bug tracker</a>. Our
98
+    <a href="<page getinvolved/volunteer>">volunteer page</a> has
99
+    convenient links to <a href="<page getinvolved/volunteer>#Projects">
100
+    project-related queries</a>.</p>
101
+
102
+    <a id="security"></a>
103
+    <h3><a class="anchor" href="#security">Security Issues</a></h3>
104
+    <p>If you've found a security issue in one of our projects or in our
105
+    infrastructure, please email tor-security@lists.torproject.org.
106
+    You can get the GPG public key for the list by contacting
107
+    tor-security-sendkey@lists.torproject.org or from
108
+    pool.sks-keyservers.net. Here is the fingerprint:
109
+<blockquote><pre>
110
+gpg --fingerprint tor-security@lists.torproject.org
111
+pub   4096R/1A7BF184 2017-03-13
112
+      Key fingerprint = 8B90 4624 C5A2 8654 E453  9BC2 E135 A8B4 1A7B F184
113
+uid                  tor-security@lists.torproject.org <tor-security@lists.torproject.org>
114
+uid                  tor-security@lists.torproject.org <tor-security-owner@lists.torproject.org>
115
+uid                  tor-security@lists.torproject.org <tor-security-request@lists.torproject.org>
116
+sub   4096R/C00942E4 2017-03-13
117
+</pre></blockquote>
91 118
     </p>
92 119
 
93
-	<a id="bugs"></a>
94
-	<h3><a class="anchor" href="#bugs">Bug Tracker</a></h3>
95
-	<p>You can report bugs other than <a href="#security">security 
96
-	issues</a> using our <a href="https://trac.torproject.org/projects/tor"
97
-	>bug tracker</a>. Our 
98
-	<a href="<page getinvolved/volunteer>">volunteer page</a> has 
99
-	convenient links to <a href="<page getinvolved/volunteer>#Projects"> 
100
-	project-related queries</a>.</p>
101
-    
102
-	<a id="security"></a>
103
-	<h3><a class="anchor" href="#security">Security Issues</a></h3>
104
-	<p>If you've found a security issue in one of our projects or in our
105
-	infrastructure, please email tor-security@lists.torproject.org. 
106
-	You can get the GPG public key for the list by contacting 
107
-	tor-security-sendkey@lists.torproject.org or from 
108
-	pool.sks-keyservers.net. Here is the fingerprint:
109
-	<blockquote><pre>
110
-	gpg --fingerprint tor-security@lists.torproject.org
111
-	pub   4096R/1A7BF184 2017-03-13
112
-	      Key fingerprint = 8B90 4624 C5A2 8654 E453  9BC2 E135 A8B4 1A7B F184
113
-	uid                  tor-security@lists.torproject.org <tor-security@lists.torproject.org>
114
-	uid                  tor-security@lists.torproject.org <tor-security-owner@lists.torproject.org>
115
-	uid                  tor-security@lists.torproject.org <tor-security-request@lists.torproject.org>
116
-	sub   4096R/C00942E4 2017-03-13
117
-	</pre></blockquote>
118
-	</p>
119
-
120
-	<a id="badrelays"></a>
121
-	<h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3>
122
-	<p>If you find a relay that you think is malicious, misconfigured, 
123
-	or otherwise broken, please check out our 
124
-	<a href="https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays">
125
-	wiki page</a> and <a href="https://blog.torproject.org/how-report-bad-relays"
126
-	>blog post</a> on how to report it.</p>
127
-
128
-
129
-	<a id="email"></a>
120
+    <a id="badrelays"></a>
121
+    <h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3>
122
+    <p>If you find a relay that you think is malicious, misconfigured,
123
+    or otherwise broken, please check out our
124
+    <a href="https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays">
125
+    wiki page</a> and <a href="https://blog.torproject.org/how-report-bad-relays"
126
+    >blog post</a> on how to report it.</p>
127
+
128
+
129
+    <a id="email"></a>
130 130
     <h3><a class="anchor" href="#email">Email</a></h3>
131 131
     <p>If you have Tor questions, please try to help yourself via the
132 132
     above support venues. Please don't use this contact address