X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=b1135b5ddfd5b0c552e7d17b43d8c60c6234f347;hb=78b9ddc7014a3a7d0cc38f7019a695a1c6139dc4;hp=e2b205bc5c6d5e0527431f2a10e3069074af00d2;hpb=662c02e3ab1cab69b67f869aba490c147fc7741e;p=privoxy.git
diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml
index e2b205bc..b1135b5d 100644
--- a/doc/source/p-config.sgml
+++ b/doc/source/p-config.sgml
@@ -1677,7 +1677,7 @@ ACLs: permit-access and deny-access
If your system implements
RFC 3493, then
src_addr and dst_addr can be IPv6 addresses delimeted by
+ class="parameter">dst_addr can be IPv6 addresses delimited by
brackets, port can be a number
or a service name, and
src_masklen and
@@ -3235,13 +3235,13 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
Under high load incoming connection may queue up before Privoxy
- gets around to serve them. The queue length is limitted by the
+ gets around to serve them. The queue length is limited by the
operating system. Once the queue is full, additional connections
are dropped before Privoxy can accept and serve them.
Increasing the queue length allows Privoxy to accept more
- incomming connections that arrive roughly at the same time.
+ incoming connections that arrive roughly at the same time.
Note that Privoxy can only request a certain queue length,