diff --git a/www.i2p2/pages/how_garlicrouting.html b/www.i2p2/pages/how_garlicrouting.html
index 6fba2314..0f1ea0e0 100644
--- a/www.i2p2/pages/how_garlicrouting.html
+++ b/www.i2p2/pages/how_garlicrouting.html
@@ -248,7 +248,7 @@ see Section 8.1.1 authored by
 </li><li>
 <a href="http://en.wikipedia.org/wiki/Garlic_routing">Garlic Routing on Wikipedia</a>
 </li><li>
-<a href="meeting58.html#delivery">I2P Meeting 58</a> (2003) discussing the implementation of garlic routing
+<a href="meeting58.html">I2P Meeting 58</a> (2003) discussing the implementation of garlic routing
 </li><li>
 <a href="https://www.torproject.org/">Tor</a>
 </li><li>
diff --git a/www.i2p2/pages/i2cp.html b/www.i2p2/pages/i2cp.html
index 30bdfb2b..8a40c9c8 100644
--- a/www.i2p2/pages/i2cp.html
+++ b/www.i2p2/pages/i2cp.html
@@ -105,7 +105,8 @@ a <a href="i2cp_spec.html#type_SessionConfig">SessionConfig</a> contained in a <
      two routers should not be in the same tunnel. 0 to disable.
 <tr><td>i2cp.dontPublishLeaseSet <td>true, false<td>&nbsp;<td>false<td>Should generally be set to true for clients
      and false for servers
-<tr><td>i2cp.messageReliability <td>&nbsp;<td>BestEffort, Guaranteed<td>BestEffort<td>Guaranteed is disabled
+<tr><td>i2cp.messageReliability <td>&nbsp;<td>BestEffort, Guaranteed, None<td>BestEffort<td>Guaranteed is disabled;
+     None implemented in 0.8.1; the streaming lib default is None as of 0.8.1
 <tr><td>explicitPeers<td>&nbsp;<td>&nbsp;<td>null<td>Comma-separated list of Base 64 Hashes of peers to build tunnels through; for debugging only
 </table>
 <p>
diff --git a/www.i2p2/pages/i2cp_spec.html b/www.i2p2/pages/i2cp_spec.html
index 23fb0082..983a0241 100644
--- a/www.i2p2/pages/i2cp_spec.html
+++ b/www.i2p2/pages/i2cp_spec.html
@@ -95,7 +95,10 @@ Bandwidth Limits Message  <---------------------
   (succeeded)
 {% endfilter %}
 </pre>
-
+<p>
+Note: As of release 0.8.1, the router does not send either Message Status Message if
+i2cp.messageReliability=none.
+</p>
 
 
 
@@ -798,6 +801,8 @@ That message will contain the same nonce sent here.
 Later on,
 based on the delivery guarantees of the session configuration, the router may
 additionally send back another MessageStatusMessage updating the status.
+Note: As of release 0.8.1, the router does not send either Message Status Message if
+i2cp.messageReliability=none.
 </p>