diff --git a/i2p2www/pages/site/docs/spec/plugin.html b/i2p2www/pages/site/docs/spec/plugin.html
index 19fa89b568e670824ad7d13aac6caff7d14b2f46..6d4cc5735c09e43f1a4480e14cc67c3848369abd 100644
--- a/i2p2www/pages/site/docs/spec/plugin.html
+++ b/i2p2www/pages/site/docs/spec/plugin.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}I2P Plugin Specification{% endblock %}
-{% block lastupdated %}January 2014{% endblock %}
-{% block accuratefor %}0.9.9{% endblock %}
+{% block lastupdated %}August 2014{% endblock %}
+{% block accuratefor %}0.9.14.1{% endblock %}
 {% block content %}
 <h3>Overview</h3>
 <p> 
@@ -243,7 +243,8 @@ This lists what happens when a plugin is installed by I2P.
 
     <li>The .xpi2p file is downloaded.</li>
     <li>The .sud signature is verified against stored keys.
-        If there is no matching key, the .sud is extracted, the key is loaded from the properties, then verified and stored.</li>
+        As of release 0.9.14.1,
+        if there is no matching key, the installation fails, unless an advanced router property is set to allow all keys.</li>
     <li>Verify the integrity of the zip file.</li>
     <li>Extract the plugin.config file.</li>
     <li>Verify the I2P version, to make sure the plugin will work.</li>