[or-cvs] make registering your nickname its own section

[arma@xxxxxxxx]

Update of /home2/or/cvsroot/tor/doc
In directory moria:/home/arma/work/onion/cvs/tor/doc

Modified Files:
	tor-doc-server.html 
Log Message:
make registering your nickname its own section


Index: tor-doc-server.html
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor-doc-server.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- tor-doc-server.html	17 Aug 2005 07:03:40 -0000	1.3
+++ tor-doc-server.html	17 Aug 2005 07:13:26 -0000	1.4
@@ -163,18 +163,30 @@
 you informed of its progress.</p>
 
 <p>When it decides that it's reachable, it will upload a "server
-descriptor" to the directories. This will let other clients know
+descriptor" to the directories. This will let clients know
 what address, ports, keys, etc your server is using. You can <a
 href="http://belegost.seul.org/";>load the directory manually</a> and
 look through it to find the nickname you configured, to make sure it's
 there. You may need to wait a few seconds to give enough time for it to
 make a fresh directory.</p>
 
-<li>Once you are convinced it's working, <b>Register your server.</b>
+<hr />
+<a id="three"></a>
+<h2><a class="anchor" href="#three">Step Three: Register your nickname</a></h2>
+<br />
+
+<p>
+Once you are convinced it's working, you should register your server.
+This reserves your nickname so nobody else can take it, and lets us
+contact you if you need to upgrade or something goes wrong.
+</p>
+
+<p>
 Send mail to <a
 href="mailto:tor-ops@xxxxxxxxxxxxx";>tor-ops@xxxxxxxxxxxxx</a> with a
 subject of '[New Server] &lt;your server's nickname&gt;' and
 include the following information in the message:
+</p>
 <ul>
 <li>Your server's nickname</li>
 <li>The fingerprint for your server's key (the contents of the
@@ -186,17 +198,14 @@
 <li>Who you are, so we know whom to contact if a problem arises</li>
 <li>What kind of connectivity the new server will have</li>
 </ul>
-Registering your server reserves your nickname so nobody else can take it,
-and lets us contact you if you need to upgrade or something goes wrong.
-</li>
 
 <hr />
-<a id="three"></a>
-<h2><a class="anchor" href="#three">Step Three: Once it's working</a></h2>
+<a id="four"></a>
+<h2><a class="anchor" href="#four">Step Four: Once it's working</a></h2>
 <br />
 
 <p>
-Optionally, we recommend the following steps as well:
+We recommend the following steps as well:
 </p>
 
 <p>
@@ -239,7 +248,8 @@
 web, and this change will let them reach your Tor server. Win32
 servers can simply change their ORPort and DirPort directly
 in their torrc and restart Tor. OS X or Unix servers can't bind
-directly to these ports, so they will need to set up some sort of <a
+directly to these ports (since they don't run as root), so they will
+need to set up some sort of <a
 href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients";>
 port forwarding</a> so connections can reach their Tor server. If you are
 using ports 80 and 443 already but still want to help out, other useful