summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorMukund Sivaraman <muks@banu.com>2010-01-25 19:35:30 +0530
committerMukund Sivaraman <muks@banu.com>2010-01-25 19:35:30 +0530
commit41d80861e30ebd9d0a2b69b9aad41cde3db98eed (patch)
tree1436fa44a236a8274f08efc33ce6dfa9fb6ed1bb
parent19b9bff88809429f82632da7e499790a6ea4d846 (diff)
Fix typo in manpage
-rw-r--r--docs/man5/tinyproxy.conf.txt.in4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/man5/tinyproxy.conf.txt.in b/docs/man5/tinyproxy.conf.txt.in
index 902d04f..e7ffcd1 100644
--- a/docs/man5/tinyproxy.conf.txt.in
+++ b/docs/man5/tinyproxy.conf.txt.in
@@ -210,9 +210,9 @@ The possible keywords and their descriptions are as follows:
which clients are allowed to access Tinyproxy. `Allow` and `Deny`
lines can be specified multiple times to build the access control
list for Tinyproxy. The order in the config file is important.
- If there are no `Access` or `Deny` lines, then all clients are
+ If there are no `Allow` or `Deny` lines, then all clients are
allowed. Otherwise, the default action is to deny access.
- The argument to `Access` or `Deny` can be a single IP address
+ The argument to `Allow` or `Deny` can be a single IP address
of a client host, like `127.0.0.1`, an IP address range, like
`192.168.0.1/24` or a string that will be matched against the
end of the client host name, i.e, this can be a full host name