From e09b3414937e4e4a05ab26ddaf62a0908053ca69 Mon Sep 17 00:00:00 2001
From: zzz <zzz@i2pmail.org>
Date: Mon, 8 Nov 2021 11:50:03 -0500
Subject: [PATCH] Reseed guide more updates
---
i2p2www/pages/site/get-involved/guides/reseed.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/i2p2www/pages/site/get-involved/guides/reseed.html b/i2p2www/pages/site/get-involved/guides/reseed.html
index f7b1381b8..511d0333e 100644
--- a/i2p2www/pages/site/get-involved/guides/reseed.html
+++ b/i2p2www/pages/site/get-involved/guides/reseed.html
@@ -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 (only if selfsigned), and the "su3" bundle public key.
+the SSL public key certificate (only if selfsigned), and the su3 public key certificate.
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.
@@ -942,9 +942,9 @@ Contact us via email zzz at mail.i2p (alternatively, post in the reseed section
Provide us with details about the new
<ul>
<li>Reseed website URL
-<li>Public part of SSL-certificate
+<li>Public SSL certificate
(Only required if selfsigned, which is not recommended. Please use Lets Encrypt or other CA)
-<li>Public reseed su3 key
+<li>Public reseed su3 certificate
<li>Your contact email
<li>A statement that you agree to the privacy policy above
</ul>
--
GitLab