diff options
| author | Michael Christen <Orbiter@users.noreply.github.com> | 2020-02-07 09:19:21 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-02-07 09:19:21 +0100 |
| commit | 749671d945f085f42d81614116d127dbafa7261b (patch) | |
| tree | 9bbd33c5f5a7afe57b7f763eb579be2bca9254d3 | |
| parent | 89497e22e3c2281199d4e3d78bd96b5368001b33 (diff) | |
| parent | a251727b96bd910776457027dd6f93446e3b4a71 (diff) | |
Merge pull request #327 from parnikkapore/pr_typos
Typo fix in yacy.network.readme
| -rw-r--r-- | defaults/yacy.network.readme | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/defaults/yacy.network.readme b/defaults/yacy.network.readme index c17760cde..73bdf90d4 100644 --- a/defaults/yacy.network.readme +++ b/defaults/yacy.network.readme @@ -54,8 +54,8 @@ # In contrast also a list of IPs may be given to be not allowed to access the peers at all # The YaCy-httpd will not respond on any request from IPs given in the blacklist # Entries in whitelist take precedence over blacklist entries -# 1. whitlist is checked if match - access is allowed -# 2. blacklist ist checked if match - access is denied +# 1. whitelist is checked if match - access is allowed +# 2. blacklist is checked if match - access is denied # By default both lists should be empty to provide a basic search functionality for everyone. # When running a private YaCy network, all peers that are in the own network should be configured # in the whitelist. Otherwise the access from whitelisted clients is allowed, but the executing |