tor-webwml.git

@@ -588,7 +588,8 @@ href="<page verifying-signatures>">verifying signatures</a> page for details.

 Windows?</a></h3>

 <p>

-Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt>"<gitblob>doc/tor-win32-mingw-creation.txt</a>.

+Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">

+tor-win32-mingw-creation.txt</a>.

 </p>

 <p>

@@ -806,7 +807,9 @@ leave the Address config option blank, and Tor will try to guess.

 </li>

 <li>If your relay is behind a NAT and it doesn't know its public

 IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port

-forwarding. Forwarding TCP connections is system dependent but <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> offers some examples on how to do this.

+forwarding. Forwarding TCP connections is system dependent but 

+<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> 

+offers some examples on how to do this.

 </li>

 <li>Your relay will passively estimate and advertise its recent

 bandwidth capacity, so high-bandwidth relays will attract more users than

@@ -833,20 +836,20 @@ will automatically avoid picking exit relays that would refuse to

 exit to their intended destination. This way each relay can decide

 the services, hosts, and networks he wants to allow connections to,

 based on abuse potential and his own situation. Read the FAQ entry on 

-<a href="<page faq-abuse>#TypicalAbuses">issues you might encounter

-if you use the default exit policy</a>, and then read Mike Perry's 

+<a href="<page faq-abuse>#TypicalAbuses">issues you might encounter</a> 

+if you use the default exit policy, and then read Mike Perry's 

 <a href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">tips

 for running an exit node with minimal harassment</a>.

 </p>

 <p>

-The default exit policy allows access to many popular services (e.g. web browsing), but <a

-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>

+The default exit policy allows access to many popular services (e.g. web browsing), but 

+<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>

 some due to abuse potential (e.g. mail) and some since

 the Tor network can't handle the load (e.g. default

 file-sharing ports). You can change your exit policy

-using Vidalia's "Sharing" tab, or by manually editing your <a

-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a>

+using Vidalia's "Sharing" tab, or by manually editing your 

+<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a>

 file. If you want to avoid most if not all abuse potential, set it to

 "reject *:*" (or un-check all the boxes in Vidalia). This setting means

 that your relay will be used for relaying traffic inside the Tor network,

@@ -890,8 +893,8 @@ public Tor relay IP address they're contacting.

 <p>So should you run a normal relay or bridge relay? If you have

 lots of bandwidth, you should definitely run a normal relay —

-bridge relays see very little use these days. If you're willing to <a

-href="#ExitPolicies">be an exit</a>, you should definitely run a normal

+bridge relays see very little use these days. 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, then flip a coin. Thanks for volunteering!

 </p>