Browse Source

Merge pull request #58 from rex4539/typos

Fix typos
pull/59/head
orignal 3 years ago committed by GitHub
parent
commit
042efce546
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      docs/devs/building/android.md
  2. 2
      docs/devs/i2pd-specifics.md
  3. 2
      docs/user-guide/FAQ.md
  4. 2
      docs/user-guide/install.md
  5. 2
      docs/user-guide/tunnels.md

2
docs/devs/building/android.md

@ -60,7 +60,7 @@ Building the app without QT
Creating release .apk 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). 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': Change file 'build.gradle':

2
docs/devs/i2pd-specifics.md

@ -2,7 +2,7 @@ i2pd-specific changes to I2P protocols
====================================== ======================================
# SAM # 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 new values for SIGNATURE_TYPE
GOST_GOSTR3411256_GOSTR3410CRYPTOPROA or 9 GOST_GOSTR3411256_GOSTR3410CRYPTOPROA or 9

2
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? ## 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 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 is shut down, or experiences connectivity problems, it can take some time for your
I2P router to discover and fix that issue. I2P router to discover and fix that issue.

2
docs/user-guide/install.md

@ -42,7 +42,7 @@ Install apt-transport-https package
sudo apt-get install apt-transport-https 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 - wget -q -O - https://repo.i2pd.xyz/.help/add_repo | sudo bash -s -

2
docs/user-guide/tunnels.md

@ -100,7 +100,7 @@ Optional parameters:
* cryptotype -- crypto type for new keys. Experimental. Should be always 0 * cryptotype -- crypto type for new keys. Experimental. Should be always 0
* destinationport -- connect to particular port at destination. 0 by default * 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 Server/generic tunnels
---------------------- ----------------------

Loading…
Cancel
Save