diff --git a/i2p2www/pages/site/docs/apis/i2ptunnel.html b/i2p2www/pages/site/docs/api/i2ptunnel.html similarity index 100% rename from i2p2www/pages/site/docs/apis/i2ptunnel.html rename to i2p2www/pages/site/docs/api/i2ptunnel.html diff --git a/i2p2www/pages/site/docs/apis/socks.html b/i2p2www/pages/site/docs/api/socks.html similarity index 100% rename from i2p2www/pages/site/docs/apis/socks.html rename to i2p2www/pages/site/docs/api/socks.html diff --git a/i2p2www/pages/site/docs/index.html b/i2p2www/pages/site/docs/index.html index bd9fce6f..32ed553f 100644 --- a/i2p2www/pages/site/docs/index.html +++ b/i2p2www/pages/site/docs/index.html @@ -25,7 +25,7 @@ If you find any inaccuracies in the documents linked below, please
Here is the protocol stack for I2P. -See also the Index to Technical Documentation. +See also the Index to Technical Documentation. Updated August 2010, current for router version 0.8.
@@ -28,9 +28,9 @@ The capabilities are listed below, starting at the bottom of the protocol stack.
I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.
Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP.
- NTCP: NIO-based TCP
+ NTCP: NIO-based TCP
- SSU: Secure Semi-reliable UDP
+ SSU: Secure Semi-reliable UDP