diff --git a/www.i2p2/pages/plugins.html b/www.i2p2/pages/plugins.html
index fbd1d9a0..04467698 100644
--- a/www.i2p2/pages/plugins.html
+++ b/www.i2p2/pages/plugins.html
@@ -86,7 +86,7 @@ Plugins are a great way to learn more about I2P or easily add some feature.
Getting Started
To create a plugin from an existing binary package you will need to get
makeplugin.sh from
-the i2p.scripts branch in monotone.
+the i2p.scripts branch in monotone.
Known Issues
@@ -98,23 +98,23 @@ Updates of a plugin with included jars (not wars) won't be recognized if the plu
it requires class loader trickery to flush the class cache;
a full router restart is required.
-Automatic updates (and check-for-updates) unimplemented.
+Automatic updates (and check-for-updates) are currently unimplemented.
-Stop button displayed even if there is nothing to stop.
+The stop button is displayed even if there is nothing to stop.
Plugins running in a separate JVM create a logs/ directory in $CWD.
-No initial keys except for jrandom and zzz (using same keys as for router update),
+No initial keys are present, except for jrandom and zzz (using the same keys as for router update),
so the first key seen for a signer is automatically accepted - there is no signing key authority.
When deleting a plugin, the directory is not always deleted, especially on Windows.
Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a "plugin is corrupt"
-message if pack200 is used.
+message if pack200 compression of the plugin file is used.
Theme and translation plugins are untested.
-Disabling autostart doesn't always work
+Disabling autostart doesn't always work.
{% endblock %}