From: Fabian Keil <fk@fabiankeil.de> Date: Thu, 28 May 2020 09:19:57 +0000 (+0200) Subject: Fix typos X-Git-Tag: v_3_0_29~388 X-Git-Url: http://www.privoxy.org/gitweb/%22https:/@default-cgi@edit-actions-add-url-form?a=commitdiff_plain;h=8e0f19f1856e7840c0c4235f4e6e5d48311ad95c;p=privoxy.git Fix typos --- 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</title> If your system implements <ulink url="http://tools.ietf.org/html/rfc3493">RFC 3493</ulink>, then <replaceable class="parameter">src_addr</replaceable> and <replaceable - class="parameter">dst_addr</replaceable> can be IPv6 addresses delimeted by + class="parameter">dst_addr</replaceable> can be IPv6 addresses delimited by brackets, <replaceable class="parameter">port</replaceable> can be a number or a service name, and <replaceable class="parameter">src_masklen</replaceable> and @@ -3235,13 +3235,13 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title> <listitem> <para> 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. </para> <para> 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. </para> <para> Note that Privoxy can only request a certain queue length,