PurpleI2P
/
i2pd_docs_en
mirror of https://github.com/PurpleI2P/i2pd_docs_en
1
0
Fork 0
Code Issues Releases Wiki Activity
Browse Source

Corrected a typo in configuration.md

pull/54/head
jerzybrzoska 3 years ago committed by GitHub
parent
50b22bccbf
commit
e7d9876118
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      docs/user-guide/configuration.md

2
docs/user-guide/configuration.md
Unescape View File

@ -10,7 +10,7 @@ There are two separate config files: `i2pd.conf` and `tunnels.conf`. `i2pd.conf`
you configure all options. `tunnels.conf` is the tunnel configuration file, where you configure I2P hidden services you configure all options. `tunnels.conf` is the tunnel configuration file, where you configure I2P hidden services
and client tunnels. the `tunnels.conf` options are documented [here](tunnels.md). and client tunnels. the `tunnels.conf` options are documented [here](tunnels.md).
`i2pd.conf` accets INI-like syntax, such as the following : <key> = <value>. `i2pd.conf` accepts INI-like syntax, such as the following : <key> = <value>.
Comments are "#", not ";" as you might expect. See [boost ticket](https://svn.boost.org/trac/boost/ticket/808) Comments are "#", not ";" as you might expect. See [boost ticket](https://svn.boost.org/trac/boost/ticket/808)
All command-line parameters are allowed as keys, but for those which contains dot (.), there is a special syntax. All command-line parameters are allowed as keys, but for those which contains dot (.), there is a special syntax.

Write Preview
Loading…
Cancel
Save