diff --git a/i2p2www/pages/site/docs/protocol/i2cp.html b/i2p2www/pages/site/docs/protocol/i2cp.html
index 99ce1c8d..c7cdd74a 100644
--- a/i2p2www/pages/site/docs/protocol/i2cp.html
+++ b/i2p2www/pages/site/docs/protocol/i2cp.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}I2CP{% endblock %}
-{% block lastupdated %}{% trans %}January 2014{% endtrans %}{% endblock %}
-{% block accuratefor %}0.9.10{% endblock %}
+{% block lastupdated %}{% trans %}June 2014{% endtrans %}{% endblock %}
+{% block accuratefor %}0.9.13{% endblock %}
 {% block content %}
 <p>{% trans -%}
 The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
@@ -108,6 +108,18 @@ a <a href="{{ i2cp }}#struct_SessionConfig">SessionConfig</a> contained in a <a
 <th>{% trans %}Description{% endtrans %}</th>
 </tr>
 
+<tr>
+<td>clientMessageTimeout
+<td>&nbsp;
+<td>&nbsp;
+<td>8*1000 - 120*1000
+<td>60*1000
+<td>{% trans -%}
+The timeout (ms) for all sent messages. Unused.
+See the protocol specification for per-message settings.
+{%- endtrans %}</td>
+</tr>
+
 <tr>
 <td>crypto.lowTagThreshold
 <td>0.9.2</td>
diff --git a/i2p2www/pages/site/docs/spec/i2cp.html b/i2p2www/pages/site/docs/spec/i2cp.html
index 6cb54d7e..ba0433e0 100644
--- a/i2p2www/pages/site/docs/spec/i2cp.html
+++ b/i2p2www/pages/site/docs/spec/i2cp.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}I2CP Specification{% endblock %}
-{% block lastupdated %}March 2014{% endblock %}
-{% block accuratefor %}0.9.12{% endblock %}
+{% block lastupdated %}June 2014{% endblock %}
+{% block accuratefor %}0.9.13{% endblock %}
 {% block content %}
 <h2>Overview</h2>
 <p>
@@ -664,7 +664,7 @@ The version string is included as of release 0.8.7.
 This is only useful if the client and router are not in the same JVM.
 If it is not present, the client is version 0.8.6 or earlier.
 </li><li>
-Preliminary: As of release 0.9.11, the authentication
+As of release 0.9.11, the authentication
 <a href="{{ site_url('docs/spec/common-structures') }}#type_Mapping">Mapping</a>
 may be included, with the keys i2cp.username and i2cp.password.
 The Mapping need not be sorted as this message is not signed.
@@ -711,7 +711,7 @@ host name <a href="{{ site_url('docs/spec/common-structures') }}#struct_String">
 
 <h4>Notes</h4>
 <ul><li>
-Preliminary. As of release 0.9.11.
+As of release 0.9.11.
 Use <a href="#msg_DestLookup">Dest Lookup Message</a> for older routers.
 </li><li>
 The session ID and request ID will be returned in the <a href="#msg_HostReply">Host Reply Message</a>.
@@ -749,7 +749,7 @@ only present if result code is zero.
 
 <h4>Notes</h4>
 <ul><li>
-Preliminary. As of release 0.9.11.
+As of release 0.9.11.
 See Host Lookup notes.
 </li><li>
 The session ID and request ID are those from the Host Lookup.
@@ -1156,7 +1156,7 @@ Bit order: 15...0
 </p><p>
 Bits 15-11: Unused, must be zero
 </p><p>
-Bits 10-9: Message Reliability Override (scheduled for release 0.9.11)
+Bits 10-9: Message Reliability Override (Preliminary, unimplemented, subject to change)
 <table border=1>
 <tr><th>Field value<th>Description
 <tr><td align="center">00<td>Use session setting i2cp.messageReliabiltiy (default)