diff --git a/docs/devs/building/android.md b/docs/devs/building/android.md
index da25795..f3d478d 100644
--- a/docs/devs/building/android.md
+++ b/docs/devs/building/android.md
@@ -60,7 +60,7 @@ Building the app without QT
 Creating release .apk
 ---------------------
 
-In order to create release .apk you must obtain a Java keystore file(.jks). Either you have in already, or you can generate it yourself using keytool, or from one of you existing well-know certificates.
+In order to create release .apk you must obtain a Java keystore file(.jks). Either you have in already, or you can generate it yourself using keytool, or from one of you existing well-known certificates.
 For example, i2pd release are signed with this [certificate](https://github.com/PurpleI2P/i2pd/blob/openssl/contrib/certificates/router/orignal_at_mail.i2p.crt).
 
 Change file 'build.gradle':
diff --git a/docs/devs/i2pd-specifics.md b/docs/devs/i2pd-specifics.md
index d6b9262..62c583e 100644
--- a/docs/devs/i2pd-specifics.md
+++ b/docs/devs/i2pd-specifics.md
@@ -2,7 +2,7 @@ i2pd-specific changes to I2P protocols
 ======================================
 
 # SAM
-SESSION CREATE and DEST GENERATE support additional parameter CRYPTO_TYPE specifing crypto type for new local destination  
+SESSION CREATE and DEST GENERATE support additional parameter CRYPTO_TYPE specifying crypto type for new local destination  
 
 new values for SIGNATURE_TYPE  
 GOST_GOSTR3411256_GOSTR3410CRYPTOPROA or 9  
diff --git a/docs/user-guide/FAQ.md b/docs/user-guide/FAQ.md
index bc21f50..3e2e2eb 100644
--- a/docs/user-guide/FAQ.md
+++ b/docs/user-guide/FAQ.md
@@ -27,7 +27,7 @@ While [Java I2P](https://geti2p.net) and i2pd are both clients for the I2P netwo
 ## Why is the I2P network so slow and unstable sometimes?
 
 By design, in the I2P network, your connection gets encrypted through a chain of 6 
-random computers in the way to it's final destination. If one of those computers
+random computers in the way to its final destination. If one of those computers
 is shut down, or experiences connectivity problems, it can take some time for your
 I2P router to discover and fix that issue. 
 
diff --git a/docs/user-guide/install.md b/docs/user-guide/install.md
index 161544c..deddf8d 100644
--- a/docs/user-guide/install.md
+++ b/docs/user-guide/install.md
@@ -42,7 +42,7 @@ Install apt-transport-https package
 
     sudo apt-get install apt-transport-https
 
-Automaticly add repository
+Automatically add repository
 
     wget -q -O - https://repo.i2pd.xyz/.help/add_repo | sudo bash -s -
 
diff --git a/docs/user-guide/tunnels.md b/docs/user-guide/tunnels.md
index 2834a5d..3876d8c 100644
--- a/docs/user-guide/tunnels.md
+++ b/docs/user-guide/tunnels.md
@@ -100,7 +100,7 @@ Optional parameters:
 * cryptotype       -- crypto type for new keys. Experimental. Should be always 0
 * destinationport -- connect to particular port at destination. 0 by default
 
-So, given the example above, if you connected to to 127.0.0.1:6668 on localhost, i2pd would tunnel that to irc.echelon.i2p:6668
+So, given the example above, if you connected to 127.0.0.1:6668 on localhost, i2pd would tunnel that to irc.echelon.i2p:6668
 
 Server/generic tunnels
 ----------------------