Hello,
i found typo in I2P Browser page. I made a patch.
a42l>From fb29fcaeb1c0e13cbc7d2b2e6e6e6b2b63cb871d Mon Sep 17 00:00:00 2001
From: a42l <a42l@???>
Date: Fri, 18 Dec 2015 20:54:35 +0000
Subject: [PATCH] Fix typo in I2P Browser page
---
wiki/src/contribute/design/I2P_Browser.mdwn | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/wiki/src/contribute/design/I2P_Browser.mdwn b/wiki/src/contribute/design/I2P_Browser.mdwn
index c0432a8..5a327b0 100644
--- a/wiki/src/contribute/design/I2P_Browser.mdwn
+++ b/wiki/src/contribute/design/I2P_Browser.mdwn
@@ -4,7 +4,7 @@ Allowed Access
The HTTP Proxy is set to 127.0.0.1 on port 4444 with an exception made for
http://127.0.0.1 which does not go through the proxy. With this set-up, only eepsites (`.i2p`
-TLD), offline Tails documentation, and the router console are acessible from I2P Browser.
+TLD), offline Tails documentation, and the router console are accessible from I2P Browser.
Also, do note that Tails'
[[netfilter-based
blocking|Tor_enforcement/Network_filter]] ensures that no Internet
@@ -21,7 +21,7 @@ exceptions added to ferm. The ports accessible by the i2pbrowser user include:
* 7657, I2P router console: The router console is accessible in the web browser at <
http://127.0.0.1:7657>
* 7658, local 'eepsite': Each I2P installation is configured out of the box
with the possibility to host one's own website (or *eepsite*) on the I2P
- network. The eepsite will not be acessible remotely unless its
+ network. The eepsite will not be accessible remotely unless its
[tunnel](
http://127.0.0.1:7657/i2ptunnel#localServerTunnelList) is started.
Note: These ports will only be opened if the user explicitly requests I2P at the boot prompt.
--
1.7.10.4
