Section headers, update info on large leasesets

i2p2www/pages/site/docs/protocol/i2cp.html

@@ -89,6 +89,7 @@ The client may now initiate or receive connections from other I2P destinations.
 {%- endtrans %}</p>
 
 <h2 id="options">{% trans %}I2CP Options{% endtrans %}</h2>
+<h3>{% trans %}Router-side Options{% endtrans %}</h3>
 <p>{% trans i2cp=site_url('docs/spec/i2cp') -%}
 The following options are traditionally passed to the router via
 a <a href="{{ i2cp }}#struct_SessionConfig">SessionConfig</a> contained in a <a href="{{ i2cp }}#msg_CreateSession">CreateSession Message</a> or a <a href="{{ i2cp }}#msg_ReconfigureSession">ReconfigureSession Message</a>.
@@ -344,8 +345,8 @@ Higher is higher priority.
 <td>2</td>
 <td>{% trans -%}
 Number of tunnels in.
-Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are not
-currently recommended, as this is untested and is incompatible with older releases.
+Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are
+incompatible with older releases.
 {%- endtrans %}</td>
 </tr>
 
@@ -430,6 +431,7 @@ Since options are encoded in a <a href="{{ commonstructures }}#type_Mapping">Map
 all option names and values are limited to 255 bytes (not characters) maximum.
 {%- endtrans %}</p>
 
+<h3>{% trans %}Client-side Options{% endtrans %}</h3>
 <p>{% trans -%}
 The following options are interpreted on the client side,
 and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.