X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fconfig.html;h=83c92b8e84bc0d3823e298b53529fb9de64df624;hp=b229eb6086521ab53f9f558919cdfe208e045696;hb=32ac1bc634d600e8f788a4e49a634d598f5dd021;hpb=1020bde33b499928eb1be70c782422703eeb0e64

diff --git a/doc/webserver/user-manual/config.html b/doc/webserver/user-manual/config.html
index b229eb60..83c92b8e 100644
--- a/doc/webserver/user-manual/config.html
+++ b/doc/webserver/user-manual/config.html
@@ -547,8 +547,8 @@
               <table border="0" bgcolor="#E0E0E0" width="90%">
                 <tr>
                   <td>
-                    <pre class="PROGRAMLISTING">  debug     1 # Log the destination for each request <span class=
-                    "APPLICATION">Privoxy</span> let through. See also debug 1024.
+                    <pre class=
+                    "PROGRAMLISTING">  debug     1 # Log the destination for each request. See also debug 1024.
   debug     2 # show each connection status
   debug     4 # show I/O status
   debug     8 # show header parsing
@@ -947,7 +947,7 @@
               destination part are optional.</p>
               <p>If your system implements <a href="http://tools.ietf.org/html/rfc3493" target="_top">RFC 3493</a>,
               then <tt class="REPLACEABLE"><i>src_addr</i></tt> and <tt class="REPLACEABLE"><i>dst_addr</i></tt> can be
-              IPv6 addresses delimeted by brackets, <tt class="REPLACEABLE"><i>port</i></tt> can be a number or a
+              IPv6 addresses delimited by brackets, <tt class="REPLACEABLE"><i>port</i></tt> can be a number or a
               service name, and <tt class="REPLACEABLE"><i>src_masklen</i></tt> and <tt class=
               "REPLACEABLE"><i>dst_masklen</i></tt> can be a number from 0 to 128.</p>
             </dd>
@@ -1970,9 +1970,9 @@
             <dt>Notes:</dt>
             <dd>
               <p>Under high load incoming connection may queue up before Privoxy gets around to serve them. The queue
-              length is limitted by the operating system. Once the queue is full, additional connections are dropped
+              length is limited by the operating system. Once the queue is full, additional connections are dropped
               before Privoxy can accept and serve them.</p>
-              <p>Increasing the queue length allows Privoxy to accept more incomming connections that arrive roughly at
+              <p>Increasing the queue length allows Privoxy to accept more incoming connections that arrive roughly at
               the same time.</p>
               <p>Note that Privoxy can only request a certain queue length, whether or not the requested length is
               actually used depends on the operating system which may use a different length instead.</p>
@@ -2406,7 +2406,7 @@
       </div>
     </div>
     <div class="SECT2">
-      <h2 class="SECT2"><a name="TLS" id="TLS">7.7. TLS/SSL</a></h2>
+      <h2 class="SECT2"><a name="TLS" id="TLS">7.7. TLS/SSL Inspection</a></h2>
       <div class="SECT3">
         <h4 class="SECT3"><a name="CA-DIRECTORY" id="CA-DIRECTORY">7.7.1. ca-directory</a></h4>
         <div class="VARIABLELIST">
@@ -2465,8 +2465,8 @@
             <dd>
               <p>This directive specifies the name of the CA certificate file in ".crt" format.</p>
               <p>The file is used by <span class="APPLICATION">Privoxy</span> to generate website certificates when
-              https filtering is enabled with the <tt class="LITERAL"><a href="actions-file.html#ENABLE-HTTP-FILTERING"
-              target="_top">enable-https-filtering</a></tt> action.</p>
+              https inspection is enabled with the <tt class="LITERAL"><a href="actions-file.html#HTTPS-INSPECTION"
+              target="_top">https-inspection</a></tt> action.</p>
               <p><span class="APPLICATION">Privoxy</span> clients should import the certificate so that they can
               validate the generated certificates.</p>
               <p>The file can be generated with: openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out
@@ -2551,7 +2551,7 @@
           <dl>
             <dt>Specifies:</dt>
             <dd>
-              <p>Directory to safe generated keys and certificates.</p>
+              <p>Directory to save generated keys and certificates.</p>
             </dd>
             <dt>Type of value:</dt>
             <dd>
@@ -2568,8 +2568,8 @@
             <dt>Notes:</dt>
             <dd>
               <p>This directive specifies the directory where generated TLS/SSL keys and certificates are saved when
-              https filtering is enabled with the <tt class="LITERAL"><a href="actions-file.html#ENABLE-HTTP-FILTERING"
-              target="_top">enable-https-filtering</a></tt> action.</p>
+              https inspection is enabled with the <tt class="LITERAL"><a href="actions-file.html#HTTPS-INSPECTION"
+              target="_top">https-inspection</a></tt> action.</p>
               <p>The keys and certificates currently have to be deleted manually when changing the <a href=
               "#CA-CERT-FILE" target="_top">ca-cert-file</a> and the <a href="#CA-CERT-KEY" target=
               "_top">ca-cert-key</a>.</p>