diff --git a/installer/resources/readme/readme.html b/installer/resources/readme/readme.html
index 1b27b685b..daeccb0ce 100644
--- a/installer/resources/readme/readme.html
+++ b/installer/resources/readme/readme.html
@@ -49,18 +49,17 @@
-
Your Own Anonymous Webserver
+Anonymous Encrypted Webserving
-- I2P comes built-in with a ready-to-go webserver for hosting your own anonymous content: a Jetty instance listening on http://127.0.0.1:7658/.
+- Ready to roll!
I2P comes built-in with a ready-to-go webserver for hosting your own anonymous website (eepsite) on the I2P darknet: a Jetty instance listening on http://127.0.0.1:7658/.
- - Start your tunnel!
- After starting up an eepsite tunnel pointing at
- it, your eepsite will be visible to others. Detailed instructions for starting
- your eepsite are on your temporary eepsite
- page.
- - Host your own content!
To host your own content
+ - Start your tunnel
+ After starting up your pre-configured I2P Webserver tunnel,
+your eepsite will be visible to others. Detailed instructions for starting
+ your eepsite are on eepsite quickstart guide.
+ - Host your own content
To host your own content
simply place your files in the eepsite/docroot/
directory (or place
any standard JSP/Servlet .war
files under eepsite/webapps
,
or standard CGI script under eepsite/cgi-bin
) and they'll show
@@ -71,7 +70,7 @@
- Be patient
I2P may be slow to start the first time as it searches for peers.
If, after 30 minutes, your Active: connected/recent count has less than 10 connected
peers, you should open I2P's port on your firewall for better connectivity.
- - Check your proxy setttings!
If
+ - Check your proxy setttings
If
you cannot see any eepsites at all (even www.i2p2.i2p),
be sure your browser proxy is set to 127.0.0.1 port 4444
.