Reseed guide updates

i2p2www/pages/site/get-involved/guides/reseed.html

@@ -1,6 +1,6 @@
 {% extends "global/layout.html" %}
 {% block title %}{{ _('How to Set up a Reseed Server') }}{% endblock %}
-{% block lastupdated %}2020-07{% endblock %}
+{% block lastupdated %}2021-11{% endblock %}
 {% block content %}
 
 <h2>{% trans %}Overview{% endtrans %}</h2>
@@ -44,7 +44,7 @@ This necessitates that you run fail2ban or an equivalent solution.
 
 <p>{% trans -%}
 When your setup is complete and ready for testing, we will need the HTTPS URL,
-the SSL public key certificate, and the "su3" bundle public key.
+the SSL public key certificate (only if selfsigned), and the "su3" bundle public key.
 After testing is complete, these will be added to the hardcoded entries in the Java and C++ routers in the next release,
 and you will start seeing traffic.
 We also will need your email address so we may continue to contact you about reseed administration issues.
@@ -938,13 +938,15 @@ Do a real reseed test on *another* I2P router machine:
 <h3>8. Contact Reseed Maintainer</h3>
 
 <p>
-Contact us per email zzz at mail.i2p (fallback is the reseed section at zzz's forum)
+Contact us via email zzz at mail.i2p (alternatively, post in the reseed section on the zzz.i2p forum)
 Provide us with details about the new
 <ul>
-<li>Reseed website URL,
+<li>Reseed website URL
 <li>Public part of SSL-certificate
-<li>Public su3-key
+    (Only required if selfsigned, which is not recommended. Please use Lets Encrypt or other CA)
+<li>Public reseed su3 key
 <li>Your contact email
+<li>A statement that you agree to the privacy policy above
 </ul>
 <p>
 Feel free to contact zzz at mail.i2p in case of questions or problems or post your question at zzz's forum in the reseed section.