diff --git a/www.i2p2/pages/i2cp_spec.html b/www.i2p2/pages/i2cp_spec.html
index bab1e486..fc0ff53a 100644
--- a/www.i2p2/pages/i2cp_spec.html
+++ b/www.i2p2/pages/i2cp_spec.html
@@ -836,8 +836,14 @@ 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
+</p><p>
+As of release 0.8.1, the router does not send either Message Status Message if
 i2cp.messageReliability=none.
+</p><p>
+Prior to release 0.9.4, a nonce value of 0 was not allowed.
+As of release 0.9.4, a nonce value of 0 is allowed, and tells to the router
+that it should not send either Message Status Message, i.e. it acts as if
+i2cp.messageReliability=none for this message only.
 </p>
 
 
@@ -868,6 +874,21 @@ truncated from 8 bytes to 6 bytes
 <p>
 As of release 0.7.1.
 </p><p>
+As soon as the SendMessageExpiresMessage arrives fully intact, the router should return
+a MessageStatusMessage stating that it has been accepted for delivery.
+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.
+</p><p>
+As of release 0.8.1, the router does not send either Message Status Message if
+i2cp.messageReliability=none.
+</p><p>
+Prior to release 0.9.4, a nonce value of 0 was not allowed.
+As of release 0.9.4, a nonce value of 0 is allowed, and tells the router
+that it should not send either Message Status Message, i.e. it acts as if
+i2cp.messageReliability=none for this message only.
+</p><p>
 As of release 0.8.4, the upper two bytes of the Date are redefined to contain
 flags. The flags must default to all zeros for backward compatibility.
 The Date will not encroach on the flags field until the year 10889.