Fixing HTML errors

www.i2p2/pages/how_garlicrouting.html

@@ -147,9 +147,7 @@ Delivery Instructions may specify a Destination, Router, or Tunnel.
 Generally, a Garlic Message will contain only one clove.
 However, the router will periodically bundle two additional
 cloves in the Garlic Message:
-<center>
-<img src="/_static/images/garliccloves.png" alt="Garlic Message Cloves" />
-</center>
+<img src="/_static/images/garliccloves.png" alt="Garlic Message Cloves" style="text-align:center;"/>
 
 <ol><li>
 A

www.i2p2/pages/how_intro.html

@@ -59,7 +59,7 @@ allocation ("lease") of some tunnels that will be used for sending and receiving
 network.  I2P has its own internal <a href="how_networkdatabase">network database</a> (using a modification of 
 the Kademlia algorithm) for distributing routing and contact information securely.</p>
 
-<center><div class="box"><img src="_static/images/net.png" alt="Network topology example" title="Network topology example" /></div></center><br/>
+<div class="box" style="text-align:center;"><img src="_static/images/net.png" alt="Network topology example" title="Network topology example" /></div>
 
 
 <p>In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on their 
@@ -98,7 +98,7 @@ Notice the different use of terms! All data from a to h is end-to-end encrypted,
 between the I2P router and the applications is not end-to-end encrypted!
 A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the applications running atop of I2P.</p>
 
-<center><div class="box"><img src="_static/images/endToEndEncryption.png" alt="End to end layered encryption" title="End to end layered encryption." /></div></center><br/>
+<div class="box" style="text-align:center;"><img src="_static/images/endToEndEncryption.png" alt="End to end layered encryption" title="End to end layered encryption." /></div>
 
 <p>The specific use of these algorithms are outlined <a href="how_cryptography">elsewhere</a>.</p>
 

www.i2p2/pages/how_intro_de.html

@@ -66,7 +66,7 @@ Tunneln, die zum Senden und Empfangen von Nachrichten durch das Netzwerk benutzt
 hat eine eigene <a href="how_networkdatabase">Netzwerk Datenbank</a> ("Floodfill") zum skalierbaren sicherem Verteilen von Routing
 und Kontaktinformationen.</p>
 
-<p><center><div class="box"><img src="_static/images/net.png" alt="Network topology example" title="Network topology example" /></div></center></p><br>
+<div class="box" style="text-align:center;"><img src="_static/images/net.png" alt="Network topology example" title="Network topology example" /></div>
 
 <p>Im oberen Bild betreiben Alice, Bob, Charlie und Dave je einen Router mit einer einzigen 
 Destination auf ihren lokalen Router. Sie haben alle ein paar 2-Hop Eingangstunnel je
@@ -110,7 +110,7 @@ der Ende-zu-Ende Verschl&uuml;sselung von Router zu Router, Alice und Bob hingeg
 die mittels(unverschl&uuml;sseltem) I2CP mit den I2P Routern kommunizieren! Sprich: bis zum I2P Router
 sind die Daten unverschl&uuml;sselt, ab dem I2P Router ist alles Ende-zu-Ende verschl&uuml;sselt.</p>
 
-<center><div class="box"><img src="_static/images/endToEndEncryption.png" alt="End to end layered encryption" title="End to end layered encryption." /></div></center><br>
+<div class="box" style="text-align:center;"><img src="_static/images/endToEndEncryption.png" alt="End to end layered encryption" title="End to end layered encryption." /></div>
 
 <p>Die genaue Anwendung dieser Algorhytmen sind <a href="how_cryptography">woanders</a> beschrieben.</p>
 

www.i2p2/pages/how_intro_es.html

@@ -67,7 +67,7 @@ Estos clientes pueden conectarse a cualquier router y autorizar la asignación
 temporal ("arrendamiento") de varios tuneles que serán usados para enviar y recibir mensaje a través de la red. I2P tiene su propia <a href="how_networkdatabase">base de datos de red</a> (utilizando una modificación del algoritmo Kademlia) para distribuir
 información de rutas y contactos de forma segura.</p>
 
-<center><div class="box"><img src="_static/images/net.png" alt="Network topology example" title="Network topology example" /></div></center><br/>
+<div class="box" style="text-align:center;"><img src="_static/images/net.png" alt="Network topology example" title="Network topology example" /></div>
 
 
 <p>En la imagen, Alice, Bob, Charlie and Dave están corriendo routers con un
@@ -119,7 +119,7 @@ conexiones I2CP entre el router I2P y las aplicaciones no son cifradas punto
 a punto. "A" y "h" son los routers de Alice y Bob, mientras que, y siguiendo 
 el diagrama, Alice y Bob son las aplicaciones corriendo encima de I2P.</p>
 
-<center><div class="box"><img src="_static/images/endToEndEncryption.png" alt="End to end layered encryption" title="End to end layered encryption." /></div></center><br/>
+<div class="box" style="text-align:center;"><img src="_static/images/endToEndEncryption.png" alt="End to end layered encryption" title="End to end layered encryption." /></div>
 
 <p>El uso específico de estos algoritmos está descrito en <a href="how_cryptography">otra parte</a>.</p>
 

www.i2p2/pages/how_intro_fr.html

@@ -61,9 +61,9 @@ autoriser l'allocation temporaire ("lease") de quelques tunnels qui seront utili
 (avec une modification de l'algorithme Kademlia) pour une distribution sécurisée 
 des informations de routage et de contacts.</p>
 
-<center><div class="box">
-<img src="_static/images/net_fr.png" alt="Exemple de topologie du réseau" 
-title="Exemple de topologie du réseau"/></div></center><br/>
+<div class="box" style="text-align:center;">
+<img src="_static/images/net_fr.png" alt="Exemple de topologie du réseau"
+title="Exemple de topologie du réseau"/></div>
 
 
 <p>Ci-dessus, Alice, Bob, Charlie, et Dave ont tous leur routeur, avec une seule Destination locale. 
@@ -106,8 +106,8 @@ bout, mais la connexion I2CP entre le routeur et les applications ne l'est pas!
 "a" et "h" sont les routeurs d'Alice et Bob, alors qu'Alice et Bob dans le schéma suivant <b>sont</b> les applications 
 qui tournent sur I2P.</p>
 
-<center><div class="box"><img src="_static/images/endToEndEncryption_fr.png" 
-alt="Cryptage en couches de bout en bout" title="Cryptage en couches de bout en bout" /></div></center><br/>
+<div class="box" style="text-align:center;"><img src="_static/images/endToEndEncryption_fr.png" 
+alt="Cryptage en couches de bout en bout" title="Cryptage en couches de bout en bout" /></div>
 
 <p>Les utilisations spécifiques de ces algorithmes sont précisées <a href="how_cryptography">ailleurs</a>.</p>
 

www.i2p2/pages/how_tunnelrouting.html

@@ -19,7 +19,7 @@ wants to send a message to Bob, she will (typically) send it out one of
 her existing outbound tunnels with instructions for that tunnel's endpoint
 to forward it to the gateway router for one of Bob's current inbound 
 tunnels, which in turn passes it to Bob.</p>
-<p><center>
+<p style="text-align:center;">
 <img src="/_static/images/tunnelSending.png" alt="Tunnel" />
 <pre>
 A: Outbound Gateway (Alice)
@@ -29,7 +29,7 @@ D: Inbound Gateway
 E: Inbound Participant
 F: Inbound Endpoint (Bob)
 </pre>
-</center></p>
+</p>
 
 <h2>Tunnel vocabulary</h2>
 <ul>

www.i2p2/pages/index.html

@@ -73,7 +73,7 @@ For more information about how I2P works, see the
 <a href="how_intro">Introduction</a>.
 </p>
 
-<div class="box" style="text-align:center">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" />
 </div>
 

www.i2p2/pages/index_ar.html

@@ -56,10 +56,8 @@ I2P هي مزيج من الشبكات قليلة التأخير و هناك حد
 لمعلومات أكثر عن عمل I2P انظر الرابط
 <a href="how_intro">المقدمة</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/index_cs.html

@@ -66,10 +66,8 @@ Síť I2P přenáší data prostřednictvím ostatních rovnocenných uzlů (pee
 obrázek. Všechna data jsou šifrována po celou dobu přenosu. Více informací o tom, jak síť funguje 
 naleznete v <a href="how_intro">úvodu</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/index_de.html

@@ -5,7 +5,7 @@
 <div class="version">
 <b>Aktuellste Version:</b>
 <div class="underline"></div>
-2011-11-08 - <strong>I2P 0.8.11</strong> - {{ urlify("release-0.8.11", "Ank&uuml;ndigung", "html")}}
+2011-11-08 - <strong>I2P 0.8.11</strong> - {{ urlify("release-0.8.11", "Ankündigung", "html")}}
 - <a href="download_de.html">Download</a>
 <div class="underline"></div>
 2007-09-28 - <strong>Syndie 1.101a</strong> -
@@ -23,8 +23,8 @@
 <a href="download"><img src="/_static/images/logo07c.jpg" alt="0.7 logo" border="none"/></a> -->
 </table>
 <div class="underline"></div>
-<p>I2P ist ein anonymisierendes Netzwerk, welches identit&auml;tskritischen Anwendungen eine einfache
-Schicht zur sicheren Kommunikation bietet. Alle Daten sind in mehreren Schritten verschl&uuml;sselt 
+<p>I2P ist ein anonymisierendes Netzwerk, welches identitätskritischen Anwendungen eine einfache
+Schicht zur sicheren Kommunikation bietet. Alle Daten sind in mehreren Schritten verschlüsselt 
 und das Netzwerk ist sowohl verteilt als auch dynamisch, ohne vertraute Parteien.</p>
 
 <p>
@@ -32,23 +32,21 @@ Es existieren viele Anwendungen, die mit über I2P laufen, unter anderem EMail,
 und IRC.
 </p>
 
-<p>Anonymit&auml;t ist nicht bin&auml;r - wir versuchen nicht, etwas absolut anonymes zu erstellen. Stattdessen
+<p>Anonymität ist nicht binär - wir versuchen nicht, etwas absolut anonymes zu erstellen. Stattdessen
 arbeiten wir daran, Angriffe auf das Netz immer schwerer zu machen. I2P an sich ist
-das, was man ein "Mixnetzwerk mit geringer Latenz" nennen kann, und es gibt Grenzen f&uuml;r die Anonymit&auml;t,
+das, was man ein "Mixnetzwerk mit geringer Latenz" nennen kann, und es gibt Grenzen für die Anonymität,
 die ein solches System bieten kann. Jedoch versuchen die darauf aufbauenden Applikationen wie <a href="http://syndie.i2p2.de/">Syndie</a>, die beiden EMail-Systeme in I2P und 
-I2PSnark, es zu erweitern, um mehr Funktionalit&auml;t und Sicherheit zu bieten.</p>
+I2PSnark, es zu erweitern, um mehr Funktionalität und Sicherheit zu bieten.</p>
 
 <p>I2P ist noch nicht fertig und sollte vor der Version 1.0 nur zum Testen oder zum Entwicklen 
 genutzt werden.
 </p>
 
 <p>
-I2P basiert darauf, dass es Daten &uuml;ber andere Knoten leitet, wie es in folgendem Bild dargestellt
-ist. Dabei sind alle Daten Ende-zu-Ende-verschlüsselt. F&uuml;r weitere Informationen zur Arbeitsweise von I2P, schau bitte in die <a href="how_intro_de">Einleitung</a>.
+I2P basiert darauf, dass es Daten über andere Knoten leitet, wie es in folgendem Bild dargestellt
+ist. Dabei sind alle Daten Ende-zu-Ende-verschlüsselt. Für weitere Informationen zur Arbeitsweise von I2P, schau bitte in die <a href="how_intro_de">Einleitung</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" />
 </div>
-</center>
 {% endblock %}

www.i2p2/pages/index_es.html

@@ -48,9 +48,7 @@ I2P se basa en que los datos se encaminan a través de otros nodos, mezclándose
 En este proceso todos los datos están cifrados desde el encaminador proveniente hasta él del destinatario.
 Para obtener más información sobre el funcionamiento de I2P, ¡échale un vistazo a la <a href="how_intro">introducción</a>!
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" />
 </div>
-</center>
 {% endblock %}

www.i2p2/pages/index_fr.html

@@ -62,10 +62,8 @@ I2P fonctionne en routant le traffic à travers les autres pairs connectés au r
 Tout le trafic est crypté de bout en bout. Pour plus d'informations sur le fonctionnement d'I2P, regardez 
 l'<a href="how_intro_fr">introduction</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption_fr.png" alt="Cryptage en couches de bout en bout" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/index_it.html

@@ -67,10 +67,8 @@ Tutto il traffico è crittografato end-to-end.
 Per altre informazione su come funziona I2P, controllate l'
 <a href="how_intro">Introduzione</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/index_nl.html

@@ -74,10 +74,8 @@ Al het verkeer is van begin tot eind geëncrypt.
 Voor meer informatie over de werking van I2P zie de
 <a href="how_intro">Introductie</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="van begin tot eind gelaagde encryptie" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/index_ru.html

@@ -46,10 +46,8 @@ I2P быстро растет! В 2009 году было выпущено дев
 
 <p>Весь трафик в сети I2P маршрутизируется через других пиров и шифруется от отправителя до получателя (см. ниже на иллюстрации). Подробнее о том, как работает I2P, читайте на странице <a href="how_intro">Introduction</a>.</p> 
 
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption.png" alt="многослойное сквозное шифрование" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/index_zh.html

@@ -41,10 +41,8 @@
 
 <p>I2P 的运行通过其他节点路由数据，其工作方式见下图。所有数据均经过端到端加密。关于 I2P 工作原理的更多信息请看 <a href="how_intro">介绍</a>.
 </p>
-<center>
-<div class="box">
+<div class="box" style="text-align:center;">
 <img src="/_static/images/endToEndEncryption_zh.png" alt="端到端加密" />
 </div>
-</center>
 
 {% endblock %}

www.i2p2/pages/protocols.html

@@ -91,13 +91,11 @@ We can order this based on the I2P stack layer they use.
 </ul>
 </p>
 
-<center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
         <img src="_static/images/protocol_stack.png" alt="I2P Network stack" title="I2P Network stack" />
         <br /><br />
         Figure 1: The layers in the I2P Network stack.
     </div>
-</center>
 <br/>
 
 <p>

www.i2p2/pages/protocols_fr.html

@@ -104,13 +104,11 @@ d'applications tournant sur I2P. On peut les ordonner suivant la couche de la pi
 </ul>
 </p>
 
-<center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
         <img src="_static/images/protocol_stack_fr.png" alt="Pile réseau I2P" title="Pile réseau I2P" />
         <br /><br />
         Figure 1: Les couches de la pile réseau d'I2P.
     </div>
-</center>
 <br/>
 
 <p>

www.i2p2/pages/techintro.html

@@ -2,11 +2,7 @@
 {% block title %}Introducing I2P{% endblock %}
 {% block content %}
 
-  <center>
-    <b class="title"> 
-    <h1>I2P: <font size="3">A scalable framework for anonymous communication</font></h1>
-    </b> 
-  </center>
+<h1 class="title">I2P: <span style="font-size:medium;">A scalable framework for anonymous communication</span></h1>
   <div id="toc">
     <h2>Table of Contents</h2>
       <ul>
@@ -114,13 +110,12 @@
     and an end point. Messages can be sent only in one way. To send messages back,
     another tunnel is required.
   </p>
-  <center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
       <img src="_static/images/tunnels.png" alt="Inbound and outbound tunnel schematic" title="Inbound and outbound tunnel schematic" />
       <br /><br />
       Figure 1: Two types of tunnels exist: inbound and outbound.
     </div>
-  </center><br/>
+  <br/>
   <p>
     Two types of tunnels exist:
     <b>"outbound" tunnels</b> send messages away from the tunnel creator,
@@ -163,15 +158,14 @@
     She can then send a build message to the first hop, requesting the construction of a tunnel and asking
     that router to send the construction message onward, until the tunnel has been constructed.
   </p>
-  <center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
       <img src="_static/images/netdb_get_routerinfo_1.png" alt="Request information on other routers" title="Request information on other routers" />
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
       <img src="_static/images/netdb_get_routerinfo_2.png" alt="Build tunnel using router information" title="Build tunnel using router information" />
       <br /><br />
       Figure 2: Router information is used to build tunnels.
     </div>
-  </center><br/>
+  <br/>
   <p>
     When Alice wants to send a message to Bob, she first does a lookup in the 
     netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. 
@@ -188,13 +182,12 @@
     recent leaseSet with the message so that Bob doesn't need to do a netDb lookup 
     for it when he wants to reply, but this is optional.
   </p>
-  <center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
       <img src="_static/images/netdb_get_leaseset.png" alt="Connect tunnels using leaseSets" title="Connect tunnels using leaseSets" />
       <br /><br />
       Figure 3: Leasesets are used to connect outbound and inbound tunnels.
     </div>
-  </center><br/>
+  <br/>
   <p>
     While the tunnels themselves have layered encryption to prevent unauthorized 
     disclosure to peers inside the network (as the transport layer itself does 

www.i2p2/pages/techintro_fr.html

@@ -2,11 +2,7 @@
 {% block title %}Présentation d'I2P{% endblock %}
 {% block content %}
 Traduction de mars 2011. <a href="techintro.html">Version anglaise actuelle</a>
-  <center>
-    <b class="title"> 
-    <h1>I2P: <font size="3">Une plate-forme modulaire pour la communication anonyme</font></h1>
-    </b> 
-  </center>
+	  <h1 class="title">I2P: <span style="font-size:medium,">Une plate-forme modulaire pour la communication anonyme</span></h1>
   <div id="toc">
     <h2>Table des matières</h2>
       <ul>
@@ -132,14 +128,13 @@ Traduction de mars 2011. <a href="techintro.html">Version anglaise actuelle</a>
     et un point terminal. Les messages ne peuvent être envoyés que dans un seul sens. Pour les réponses, 
     un autre tunnel est nécessaire.
   </p>
-  <center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
       <img src="_static/images/tunnels_fr.png" alt="Schéma de tunnels entrant et sortant" 
       title="Schéma de tunnels entrant et sortant" />
       <br /><br />
       Figure 1: Les deux types de tunnels: entrant et sortant.
     </div>
-  </center><br/>
+  <br/>
   <p>
     Il y deux types de tunnels:
     Les <b>tunnels "sortants"</b> expédient des messages depuis le créateur du tunnel, alors
@@ -182,8 +177,7 @@ Traduction de mars 2011. <a href="techintro.html">Version anglaise actuelle</a>
     Ensuite elle peut envoyer au premier saut un message élaboré, demandant la création d'un tunnel, et de faire passer
     cette demande plus loin, jusqu'à ce que le tunnel soit entièrement créé.
   </p>
-  <center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
       <img src="_static/images/netdb_get_routerinfo_1_fr.png" alt="Demande d'informations sur d'autres routeurs" 
        title="Demande d'informations sur d'autres routeurs" />
       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@@ -193,7 +187,7 @@ Traduction de mars 2011. <a href="techintro.html">Version anglaise actuelle</a>
       <br /><br />
       Figure 2: Les informations sur les routeurs servent à construire les tunnels.
     </div>
-  </center><br/>
+  <br/>
   <p>
     Quand Alice désire envoyer un message à Bob, elle recherche tout d'abord dans la netDb 
     un jeu de baux de Bob, ce qui lui donne ses passerelles entrantes de tunnels. 
@@ -208,14 +202,13 @@ Traduction de mars 2011. <a href="techintro.html">Version anglaise actuelle</a>
     Alice peut aussi raccourcir le temps de réponse en fournissant dans le message son jeu de baux le plus récent, 
     en sorte que Bob soit dispensé d'une requête à netDb quand il voudra répondre. Mais ceci est optionnel.
   </p>
-  <center>
-    <div class="box">
+    <div class="box" style="text-align:center;">
       <img src="_static/images/netdb_get_leaseset_fr.png" alt="Connexion de tunnels grâce au jeux de baux" 
 title="Connexion de tunnels grâce au jeux de baux" />
       <br /><br />
       Figure 3: Les jeux de baux sont utilisés pour connecter les tunnels sortants et entrants.
     </div>
-  </center><br/>
+  <br/>
   <p>
     De même que les tunnels ont eux-mêmes un cryptage étagé pour empêcher un dévoilement non autorisé  
     par les pairs au sein du réseau (comme la couche transport le fait elle-même pour protéger des pairs 

www.i2p2/pages/tunnel-alt.html

@@ -6,7 +6,7 @@ This page documents the current tunnel implementation.
 Updated October 2010 for release 0.8
 
 
-<h2><a name="tunnel.overview">Tunnel overview</a></h2>
+<h2 id="tunnel.overview">Tunnel overview</h2>
 
 <p>Within I2P, messages are passed in one direction through a virtual
 tunnel of peers, using whatever means are available to pass the 
@@ -53,7 +53,7 @@ An overview of I2P tunnel terminology is
 <a href="how_tunnelrouting.html">on the tunnel overview page</a>.
 </p>
 
-<h2><a name="tunnel.operation">Tunnel Operation (Message Processing)</a></h2>
+<h2 id="tunnel.operation">Tunnel Operation (Message Processing)</h2>
 <h3>Overview</h3>
 
 <p>After a tunnel is built, <a href="i2np.html">I2NP messages</a> are processed and passed through it.
@@ -129,8 +129,8 @@ so that the plaintext is revealed at the outbound endpoint.
 
 
 
-<h3><a name="tunnel.gateway">Gateway Processing</a></h3>
-<h4><a name="tunnel.preprocessing">Message Preprocessing</a></h4>
+<h3 id="tunnel.gateway">Gateway Processing</h3>
+<h4 id="tunnel.preprocessing">Message Preprocessing</h4>
 
 <p>A tunnel gateway's function is to fragment and pack
 <a href="i2np.html">I2NP messages</a> into fixed-size
@@ -167,7 +167,7 @@ Details are in the
 
 
 
-<h4>Gateway Encryption</h3>
+<h3>Gateway Encryption</h3>
 
 <p>After the preprocessing of messages into a padded payload, the gateway builds
 a random 16 byte IV value, iteratively encrypting it and the tunnel message as
@@ -182,7 +182,7 @@ data with the IV and layer keys for all hops in the tunnel.  The result of the o
 tunnel encryption is that when each peer encrypts it, the endpoint will recover 
 the initial preprocessed data.</p>
 
-<h3><a name="tunnel.participant">Participant Processing</a></h3>
+<h3 id="tunnel.participant">Participant Processing</h3>
 
 <p>When a peer receives a tunnel message, it checks that the message came from
 the same previous hop as before (initialized when the first message comes through
@@ -205,7 +205,7 @@ false positive.  The unique value fed into the Bloom filter is the XOR of the IV
 and the first block so as to prevent nonsequential colluding peers in the tunnel 
 from tagging a message by resending it with the IV and first block switched.</p>
 
-<h3><a name="tunnel.endpoint">Endpoint Processing</a></h3>
+<h3 id="tunnel.endpoint">Endpoint Processing</h3>
 
 <p>After receiving and validating a tunnel message at the last hop in the tunnel,
 how the endpoint recovers the data encoded by the gateway depends upon whether 
@@ -220,7 +220,7 @@ which it may then parse out into the included I2NP messages and forwards them as
 requested in their delivery instructions.</p>
 
 
-<h2><a name="tunnel.building">Tunnel Building</a></h2>
+<h2 id="tunnel.building">Tunnel Building</h2>
 
 <p>When building a tunnel, the creator must send a request with the necessary
 configuration data to each of the hops and wait for all of them to agree before
@@ -231,14 +231,14 @@ reply.  There are three important dimensions to keep in mind when producing
 the tunnels: what peers are used (and where), how the requests are sent (and 
 replies received), and how they are maintained.</p>
 
-<h3><a name="tunnel.peerselection">Peer Selection</a></h3>
+<h3 id="tunnel.peerselection">Peer Selection</h3>
 
 <p>Beyond the two types of tunnels - inbound and outbound - there are two styles
 of peer selection used for different tunnels - exploratory and client.
 Exploratory tunnels are used for both network database maintenance and tunnel
 maintenance, while client tunnels are used for end to end client messages.  </p>
 
-<h4><a name="tunnel.selection.exploratory">Exploratory tunnel peer selection</a></h4>
+<h4 id="tunnel.selection.exploratory">Exploratory tunnel peer selection</h4>
 
 <p>Exploratory tunnels are built out of a random selection of peers from a subset
 of the network.  The particular subset varies on the local router and on what their
@@ -253,7 +253,7 @@ Exploratory peer selection is discussed further on the
 <a href="how_peerselection.html">Peer Profiling and Selection page</a>.
 
 
-<h4><a name="tunnel.selection.client">Client tunnel peer selection</a></h4>
+<h4 id="tunnel.selection.client">Client tunnel peer selection</h4>
 
 <p>Client tunnels are built with a more stringent set of requirements - the local
 router will select peers out of its "fast and high capacity" profile category so
@@ -265,7 +265,7 @@ should be adhered to, depending upon the client's anonymity needs.</p>
 Client peer selection is discussed further on the
 <a href="how_peerselection.html">Peer Profiling and Selection page</a>.
 
-<h4><a name="ordering">Peer Ordering within Tunnels</a></h4>
+<h4 id="ordering">Peer Ordering within Tunnels</h4>
 
 Peers are ordered within tunnels to
 to deal with the <a href="http://prisms.cs.umass.edu/brian/pubs/wright-tissec.pdf">predecessor 
@@ -294,7 +294,7 @@ within a single pool but not between different pools.
 New keys are generated at each router restart.
 
 
-<h3><a name="tunnel.request">Request delivery</a></h3>
+<h3 id="tunnel.request">Request delivery</h3>
 
 <p>
 A multi-hop tunnel is built using a single build message which is repeatedly
@@ -326,7 +326,7 @@ the router in question.
 For more information on peer profiling, see the
 <a href="how_peerselection.html">Peer Profiling and Selection page</a>.
 
-<h3><a name="tunnel.pooling">Tunnel Pools</a></h3>
+<h3 id="tunnel.pooling">Tunnel Pools</h3>
 
 <p>To allow efficient operation, the router maintains a series of tunnel pools,
 each managing a group of tunnels used for a specific purpose with their own
@@ -380,7 +380,7 @@ run out of tunnels) are prioritized.
 </p>
 
 
-<h2><a name="tunnel.throttling">Tunnel Message Throttling</a></h2>
+<h2 id="tunnel.throttling">Tunnel Message Throttling</h2>
 
 <p>Even though the tunnels within I2P bear a resemblance to a circuit switched
 network, everything within I2P is strictly message based - tunnels are merely
@@ -413,8 +413,8 @@ dropping those messages is lower.
 </p>
 
 
-<h2><a name="future">Future Work</a></h3>
-<h3><a name="tunnel.mixing">Mixing/batching</a></h3>
+<h2 id="future">Future Work</h3>
+<h3 id="tunnel.mixing">Mixing/batching</h3>
 
 <p>What strategies could be used at the gateway and at each hop for delaying,
 reordering, rerouting, or padding messages?  To what extent should this be done