#2143 - Fix HTML tags

i2p2www/pages/site/docs/how/network-database.html

@@ -234,7 +234,7 @@ A LeaseSet for a destination used only for outgoing connections is <i>unpublishe
 It is never sent for publication to a floodfill router.
 "Client" tunnels, such as those for web browsing and IRC clients, are unpublished.
 Servers will still be able to send messages back to those unpublished destinations,
-because of <a href="#leaseset_storage_peers">I2NP storage messages</a>.
+because of <a href="#lsp">I2NP storage messages</a>.
 {%- endtrans %}</p>
 
 
@@ -293,7 +293,7 @@ for the entry to be sent, verifying its proper insertion / distribution. If the
 verification peer doesn't reply, or they don't have the entry, the sender 
 repeats the process. When the peer in the floodfill netDb receives a netDb 
 store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.
-The peers selected are the ones closest (according to the <a href="#kademlia_closeness">XOR-metric</a>) to a specific key.
+The peers selected are the ones closest (according to the <a href="#kad">XOR-metric</a>) to a specific key.
 {%- endtrans %}</p>
 
 <p>{% trans -%}
@@ -357,7 +357,7 @@ Since they are generally high-bandwidth, they are more likely to participate in
 {%- endtrans %}</p>
 
 
-<a name="kademlia_closeness"><h2 id="kad">{% trans %}Kademlia Closeness Metric{% endtrans %}</h2></a>
+<h2 id="kad">{% trans %}Kademlia Closeness Metric{% endtrans %}</h2>
 <p>{% trans -%}
 The netDb uses a simple Kademlia-style XOR metric to determine closeness.
 The SHA256 hash of the key being looked up or stored is XOR-ed with
@@ -388,7 +388,7 @@ or <a href="{{ ssu }}">SSU</a> transport connection.
 {%- endtrans %}</p>
 
 
-<a name="leaseset_storage_peers"><h3>{% trans %}LeaseSet Storage to Peers{% endtrans %}</h3></a>
+<h3 id="lsp">{% trans %}LeaseSet Storage to Peers{% endtrans %}</h3>
 <p>{% trans i2np=site_url('docs/protocol/i2np') -%}
 <a href="{{ i2np }}">I2NP</a> DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers
 by bundling them in a garlic message along with normal traffic from the related Destination.