diff --git a/installer/resources/readme/readme.html b/installer/resources/readme/readme.html
index d3652b56f..593a1fcf8 100644
--- a/installer/resources/readme/readme.html
+++ b/installer/resources/readme/readme.html
@@ -78,9 +78,7 @@ your eepsite will be visible (but not discoverable) to others. Detailed instruct
 
 <h2>Troubleshooting &amp; Further Assistance</h2><a name="trouble"></a>
     <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 still has less than 10 connected 
-  peers, there are several things you can do to check for problems: 
+      <li class="tidylist"><b>Be Patient!</b><br>I2P may be slow to start the first time, as it searches for peers. The longer your I2P router is running, the better it will perform, so try and keep your router on as long as you can, 24/7 if possible! If, after 30 minutes, your <i>Active: [connected/recent]</i> count still has less than 10 peers, or your total number of <i>Integrated</i> peers is less than 10, there are several things you can do to check for problems: 
   </li>
 
   <li class="tidylist"><b>Check your Configuration &amp; Bandwidth Allocation</b><br>I2P functions best when you can accurately reflect the speed of your network connection in the <a href="/config">bandwidth configuration section</a>. By default I2P is configured with some fairly conservative values that will not suit many use cases, so please take time to review these settings and correct where necessary. The more bandwidth you allocate and <i>specifically</i> upstream bandwidth, the more you benefit from the network.