diff --git a/i2p2www/pages/site/docs/applications/bittorrent.html b/i2p2www/pages/site/docs/applications/bittorrent.html
index 7089ea654bbc4c03a8af1c3af5e7d877629a28be..4ddc3bb62a8b5b3b741b7fea0484164fc86187d1 100644
--- a/i2p2www/pages/site/docs/applications/bittorrent.html
+++ b/i2p2www/pages/site/docs/applications/bittorrent.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}{% trans %}Bittorrent over I2P{% endtrans %}{% endblock %}
-{% block lastupdated %}{% trans %}May 2014{% endtrans %}{% endblock %}
-{% block accuratefor %}0.9.13{% endblock %}
+{% block lastupdated %}{% trans %}January 2017{% endtrans %}{% endblock %}
+{% block accuratefor %}0.9.28{% endblock %}
 {% block content %}
 
 <p>{% trans -%}
@@ -44,8 +44,8 @@ Other parameters are the same as in standard bittorrent.
 {%- endtrans %}</p>
 
 <p>{% trans -%}
-While all current Destinations for clients are exactly 387 bytes, a tracker should not
-presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.
+Current Destinations for clients are 387 or more bytes (516 or more in Base 64 encoding).
+A reasonable maximum to assume, for now, is 475 bytes.
 As the tracker must decode the Base64 to deliver compact responses (see below),
 the tracker should probably decode and reject bad Base64 when announced.
 {%- endtrans %}</p>