Commit 84ff9637 authored by JesseW's avatar JesseW Committed by sajolida

3 small native English fixes for the I2P pages

parent b14c3af7
......@@ -72,7 +72,7 @@ The I2P router is configured to run in hidden mode: killing I2P
ungracefully is bad for the I2P network, and this is most likely
a prevalent behaviour among Tails users. For I2P to shutdown
gracefully, it needs up to 11 minutes to let all its current
participatory tunnels to expire. Killing I2P before that makes peers
participatory tunnels expire. Killing I2P before that makes peers
using these participatory tunnels experience timeouts and disconnects,
which most definitely is bad for the network. Since Tails users are
likely to shutdown Tails quickly without waiting these 11 minutes,
......
......@@ -5,7 +5,7 @@ which supports most common Internet activities like web browsing,
email, filesharing etc. Unlike Tor, whose main focus arguably is on
accessing sites from the "normal" Internet, I2P is more oriented
towards being a closed [[!wikipedia darknet]], separate from the
"normal" Internet. Any one running I2P can run an anonymous server, a
"normal" Internet. Anyone running I2P can run an anonymous server, a
so called Eepsite, that is only accessible within I2P using the `.i2p`
top level domain (similar to `.onion` for Tor hidden services). For
instance, the I2P homepage can also be accessed through I2P via
......@@ -37,5 +37,5 @@ desktop, choose <span class="menuchoice">
The router console shows I2P's current status, links to many useful I2P resources
(forums, email, filesharing, etc.) and offers the possibility to
shutdown I2P. Starting with Tails 1.2, `.i2p` addresses are only accessible
from within I2P Browser. Internet resources cannot be reached from within I2P
from within I2P Browser. Internet resources cannot be reached from within the I2P
Browser.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment