diff --git a/i2p2www/pages/site/docs/api/samv3.html b/i2p2www/pages/site/docs/api/samv3.html
index 7c902d91..6eaf6b59 100644
--- a/i2p2www/pages/site/docs/api/samv3.html
+++ b/i2p2www/pages/site/docs/api/samv3.html
@@ -1,7 +1,7 @@
 {% extends "global/layout.html" %}
 {% block title %}SAM V3{% endblock %}
-{% block lastupdated %}2020-11{% endblock %}
-{% block accuratefor %}0.9.48{% endblock %}
+{% block lastupdated %}2021-01{% endblock %}
+{% block accuratefor %}0.9.49{% endblock %}
 {% block content %}
 <p>SAM is a simple client protocol for interacting with I2P.
 SAM is the recommended protocol for non-Java applications to connect to the I2P network,
@@ -652,6 +652,10 @@ whose ID is $nickname to the specified peer.
 The target is $destination, which is the base 64 of the <a href="{{ site_url('docs/spec/common-structures') }}#type_Destination">Destination</a>,
 which is 516 or more base 64 characters (387 or more bytes in binary),
 depending on signature type.
+<b>NOTE:</b>
+Since about 2014 (SAM v3.1), Java I2P has also supported hostnames and b32 addresses for the $destination, but this was previously undocumented.
+Hostnames and b32 addresses are now officially supported by Java I2P as of release 0.9.48.
+The i2pd router does not currently support hostnames and b32 addresses; support may be added in a future release.
 </p>
 
 <h4>Connect Response</h4>
@@ -937,6 +941,10 @@ This is all on one line (space separated), shown on multiple lines for clarity:
  The target is $destination, which is the base 64 of the <a href="{{ site_url('docs/spec/common-structures') }}#type_Destination">Destination</a>,
    which is 516 or more base 64 characters (387 or more bytes in binary),
    depending on signature type.
+  <b>NOTE:</b>
+  Since about 2014 (SAM v3.1), Java I2P has also supported hostnames and b32 addresses for the $destination, but this was previously undocumented.
+  Hostnames and b32 addresses are now officially supported by Java I2P as of release 0.9.48.
+  The i2pd router does not currently support hostnames and b32 addresses; support may be added in a future release.
 </li><li>
  All options are per-datagram settings that override the defaults specified in the SESSION CREATE.
 </li><li>