Fix SAMv3 documentation for SIGNATURE_TYPE

i2p2www/pages/site/docs/api/samv3.html

 {% extends "global/layout.html" %}
 {% block title %}SAM V3{% endblock %}
-{% block lastupdated %}September 2016{% endblock %}
-{% block accuratefor %}0.9.26{% endblock %}
+{% block lastupdated %}April 2017{% endblock %}
+{% block accuratefor %}0.9.29{% endblock %}
 {% block content %}
 <p>Specified below is a simple client protocol for interacting with I2P.
 </p>
@@ -324,6 +324,7 @@ received through other forms are answered with an error message) :
           STYLE={STREAM,DATAGRAM,RAW}
           ID=$nickname
           DESTINATION={$privkey,TRANSIENT}
+          [SIGNATURE_TYPE=value]               # SAM 3.1 or higher only, for DESTINATION=TRANSIENT only, default DSA_SHA1
           [PORT=$port]                         # Required for DATAGRAM and RAW, invalid for STREAM
           [HOST=$host]                         # Optional for DATAGRAM and RAW, invalid for STREAM
           [FROM_PORT=nnn]                      # SAM 3.2 or higher only, default 0
@@ -1171,7 +1172,8 @@ Public and private base64 keys can be generated using the following
 message:
 
 <pre>
- DEST GENERATE
+-&gt;  DEST GENERATE
+          [SIGNATURE_TYPE=value]               # SAM 3.1 or higher only, default DSA_SHA1
 </pre>
 
 </p><p>
@@ -1184,7 +1186,7 @@ which is answered by
 </pre>
 
 </p><p>
-As of I2P 0.9.14, an optional parameter SIGNATURE_TYPE is supported.
+As of version 3.1 (I2P 0.9.14), an optional parameter SIGNATURE_TYPE is supported.
 The SIGNATURE_TYPE value may be any name (e.g. ECDSA_SHA256_P256, case insensitive) or number (e.g. 1)
 that is supported by <a href="{{ site_url('docs/spec/common-structures') }}#type_Certificate">Key Certificates</a>.
 The default is DSA_SHA1.