minor fixes

i2p2www/pages/spec/index.html

@@ -13,7 +13,7 @@ documents that track changes to these specifications can be viewed
 "Last updated" is the last date when the specification given within a document
 was altered in any way, except for changes to the "accurate for" information.
 </li><li>
-The "accurate for" column gives the version of the I2P network and reference
+The "accurate for" column gives the API version of the I2P network and reference
 Java implementation that the document is verified to be valid for. Because the
 documents are usually only updated when changes are made, the listed versions
 can sometimes be several releases behind. This does not mean that documents with
@@ -52,15 +52,21 @@ If you find any inaccuracies in the documents linked below, please
 
 <h3>Other specification documents</h3>
 
-These will eventually be migrated to the new specifications system.
+Current specifications: These may eventually be migrated to the new format.
 
 <ul>
 <li><a href="{{ site_url('docs/how/elgamal-aes') }}">{{ _('ElGamal/AES+SessionTags') }}</a></li>
-<li><a href="{{ site_url('docs/transport/ntcp') }}">NTCP</a></li>
 <li><a href="{{ site_url('docs/api/i2pcontrol') }}">I2PControl</a></li>
 <li><a href="{{ site_url('docs/api/samv3') }}">SAM v3</a></li>
-<li><a href="{{ site_url('docs/api/bob') }}">BOB</a></li>
 <li><a href="{{ site_url('docs/applications/bittorrent') }}">{{ _('Bittorrent') }}</a></li>
 <li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Address Book') }}</a></li>
 </ul>
+
+Obsolete specifications:
+
+<ul>
+<li><a href="{{ site_url('docs/transport/ntcp') }}">NTCP</a></li>
+<li><a href="{{ site_url('docs/api/bob') }}">BOB</a></li>
+</ul>
+
 {% endblock %}

i2p2www/spec/ecies-routers.rst

@@ -1,7 +1,6 @@
 =============================
 ECIES-X25519 Router Messages
 =============================
-
 .. meta::
     :category: Protocols
     :lastupdated: 2021-01

i2p2www/spec/ntcp2.rst

@@ -1996,7 +1996,7 @@ Clock Skew Guidelines
 
 Peer timestamps are included in the first two handshake messages, Session Request and Session Created.
 A clock skew between two peers of greater than +/- 60 seconds is generally fatal.
-If Bob thinks that his local clock is bad, he may adjust her clock using the
+If Bob thinks that his local clock is bad, he may adjust his clock using the
 calculated skew, or some external source.
 Otherwise, Bob should reply with a Session Created even if the maximum skew is exceeded,
 rather than simply closing the connection. This allows Alice to get Bob's timestamp and

i2p2www/spec/tunnel-creation-ecies.rst

@@ -1,7 +1,6 @@
 =============================
 ECIES-X25519 Tunnel Creation
 =============================
-
 .. meta::
     :category: Protocols
     :lastupdated: 2021-07