diff --git a/docs/devs/hacking.md b/docs/devs/hacking.md
index d36c953..0339ea5 100644
--- a/docs/devs/hacking.md
+++ b/docs/devs/hacking.md
@@ -1,5 +1,5 @@
 
-# Hacking on I2PD
+# Hacking on i2pd
 
 This document contains notes compiled from hacking on i2pd
 
@@ -8,7 +8,7 @@ This document contains notes compiled from hacking on i2pd
 This guide assumes:
 
 * a decent understanding of c++ 
-* basic understanding of how i2p works at i2np level and up
+* basic understanding of how I2P works at i2np level and up
 
 ## general structure
 
@@ -38,7 +38,7 @@ For Pending RouterInfo/LeaseSet lookup and store requests
 
 #### ClientContext.h
 
-`i2p::client::ClientContext` spawns all destinations used by the i2p router including the shared local destination.
+`i2p::client::ClientContext` spawns all destinations used by the I2P router including the shared local destination.
 
 global singleton at `i2p::client::context` as of 2.10.1
 
@@ -48,7 +48,7 @@ global singleton at `i2p::client::context` as of 2.10.1
 
 File: Daemon.cpp
 
-`i2p::util::Daemon_Singleton_Private` subclasses implement the daemon start-up and tear-down, creates Http Webui and i2p control server.
+`i2p::util::Daemon_Singleton_Private` subclasses implement the daemon start-up and tear-down, creates Http Webui and I2P control server.
 
 
 
diff --git a/docs/tutorials/floodfill-bootstrap.md b/docs/tutorials/floodfill-bootstrap.md
index 2ddfd7c..60bccb9 100644
--- a/docs/tutorials/floodfill-bootstrap.md
+++ b/docs/tutorials/floodfill-bootstrap.md
@@ -1,9 +1,9 @@
 Bootstrapping without Reseed Servers
 ==============================================
 
-In some cases i2p's default reseed servers (servers used to fill i2p router's netdb with initial peers) are blocked.
+In some cases I2P's default reseed servers (servers used to fill I2P router's netdb with initial peers) are blocked.
 
-I2PD has a unique feature that allows it to bootstrap off of any i2p router that is participating in the DHT, they are called floodfill routers and have the router capacity `f` in their router info.
+i2pd has a unique feature that allows it to bootstrap off of any I2P router that is participating in the DHT, they are called floodfill routers and have the router capacity `f` in their router info.
 
 ## How To
 
diff --git a/docs/user-guide/FAQ.md b/docs/user-guide/FAQ.md
index 69effb5..98393be 100644
--- a/docs/user-guide/FAQ.md
+++ b/docs/user-guide/FAQ.md
@@ -76,7 +76,7 @@ Use any open source browser - for example, Firefox or Chromium based. Create sep
 
 Good idea is to configure [privoxy](https://wiki.archlinux.org/index.php/Privoxy) for I2P/onion/clearnet browsing at the same time.
 
-i2pd socks proxy has an option to pass all non-i2p traffic to Tor socks proxy. Make sure you know what are you doing!
+i2pd socks proxy has an option to pass all non-I2P traffic to Tor socks proxy. Make sure you know what are you doing!
 
 ## What is a floodfill mode?
 
diff --git a/docs/user-guide/configuration.md b/docs/user-guide/configuration.md
index 406b681..15dc873 100644
--- a/docs/user-guide/configuration.md
+++ b/docs/user-guide/configuration.md
@@ -113,7 +113,7 @@ socksproxy.inbound.length              | Inbound tunnels length if keys is set.
 socksproxy.inbound.quantity            | Inbound tunnels quantity if keys is set. 5 by default  
 socksproxy.outbound.length             | Outbound tunnels length if keys is set. 3 by default  
 socksproxy.outbound.quantity           | Outbound tunnels quantity if keys is set. 5 by default  
-socksproxy.outproxy                    | Address of outproxy. requests outside i2p will go there  
+socksproxy.outproxy                    | Address of outproxy. requests outside I2P will go there  
 socksproxy.outproxyport                | Outproxy remote port  
 
 ### SAM interface