From f3fc28ff74cac9df7229ff868a4dff77863ff031 Mon Sep 17 00:00:00 2001
From: z3d <z3d@mail.i2p>
Date: Sun, 28 Nov 2010 13:29:28 +0000
Subject: [PATCH] Readme tweaks.
---
installer/resources/readme/readme.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/installer/resources/readme/readme.html b/installer/resources/readme/readme.html
index 51828d968e..2e9fa42f8b 100644
--- a/installer/resources/readme/readme.html
+++ b/installer/resources/readme/readme.html
@@ -13,7 +13,7 @@
</div>
</div>
<div class="welcome"><h2>Welcome to the Invisible Internet</h2></div>
-<ul class="links"><li class="tidylist"><b>Starting Up…</b><br>If you've just started I2P, the number of <i>Active Peers</i> indicated under the <i>Peers Section</i> in the sidepanel on the left should start to grow over the next few minutes and you'll see a <i>Local Destination</i> named <i>Shared Clients</i> listed at the bottom of the lefthand sidepanel and possibly other clients and servers depending on how I2P is configured
+<ul class="links"><li class="tidylist"><b>Starting Up…</b><br>If you've just started I2P, the number of <i>Active Peers</i> indicated under the <i>Peers Section</i> in the lefthand sidepanel should start to grow over the next few minutes and you'll also see a <i>Local Destination</i> named <i>Shared Clients</i> listed there, and possibly other clients and servers depending on how I2P is configured
(if not, <a href="#trouble">see below</a>). These <i>Local Destinations</i> provide connections on different ports (and sometimes protocols) to the I2P network enabling your bittorrent, e-mail, web proxy and other services to function.</li>
<li class="tidylist"><b>Network integration</b><br> The first time you start I2P it may take a few minutes to bootstrap (integrate) you into the network and find additional peers to optimize your integration, so please be patient. Once green stars are indicated next to your <i>Local Destinations</i>, there is a wide variety of things you can do with I2P, and below we introduce you to some of them.</ul>
@@ -71,7 +71,7 @@ your eepsite will be visible (but not discoverable) to others. Detailed instruct
<ul class="links">
<li class="tidylist"><b>Be patient!</b><br>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 <a href="http://127.0.0.1:7657/config">I2P's port</a> on your modem, router and/or firewall(s) for better connectivity. More information on how to go about port forwarding can be found at <a href="http://portforward.com" target="_blank">portforward.com</a>, in addition to our forums and irc channels listed below.</li>
+ peers, you should open <a href="http://127.0.0.1:7657/config">I2P's port</a> on your modem, router and/or firewall(s) for better connectivity. More information on how to go about port forwarding can be found at <a href="http://portforward.com" target="_blank">portforward.com</a>, in addition to our forums and IRC channels listed below.</li>
<li class="tidylist"><b>Check your proxy setttings</b><br>If
you cannot see any eepsites at all (even <a href="http://www.i2p2.i2p/" target="_blank">www.i2p2.i2p</a>),
be sure your browser proxy is set to access http traffic (<i>not</i> https, <i>not</i> socks) via <code>127.0.0.1 port 4444</code>. If you need some help, there's <a href="http://www.i2p2.i2p/htproxyports.html" target="_blank">a guide</a> to configuring your browser for I2P use, also <a href="http://www.i2p2.de/htproxyports.html" target="_blank">available</a> on the normal net. </li>
--
GitLab