X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=eb75d4e3dd78e4c62acdf8ad4edbc6477d018b2c;hb=2b9f7cb23aaa6c1d08cf5ebbb58d8801421bb1fa;hp=2933d0433eb883469a323db42665af7f976762e6;hpb=2d0848de83fcb47a300f26554084a2df8519b8b0;p=privoxy.git

diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml
index 2933d043..eb75d4e3 100644
--- a/doc/source/p-config.sgml
+++ b/doc/source/p-config.sgml
@@ -1018,7 +1018,7 @@ actionsfile
     <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     4 # show tagging-related messages
   debug     8 # show header parsing
   debug    16 # log all data written to the network
   debug    32 # debug force feature
@@ -3903,6 +3903,12 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
 <sect2 id="https-inspection-directives">
 <title>HTTPS Inspection (Experimental)</title>
 
+<para>
+  HTTPS inspection allows to filter encrypted requests.
+  This is only supported when <application>Privoxy</application>
+  has been built with FEATURE_HTTPS_INSPECTION.
+</para>
+
 <!--   ~~~~~       New section      ~~~~~     -->
 
 <sect3 renderas="sect4" id="ca-directory"><title>ca-directory</title>
@@ -4018,7 +4024,7 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
    </para>
    <para>
     The file can be generated with:
-    openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.crt -days 3650
+    <command>openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.crt -days 3650</command>
    </para>
   </listitem>
  </varlistentry>
@@ -4074,9 +4080,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
   <term>Notes:</term>
   <listitem>
    <para>
-    This directive specifies the name of the CA key file
-    in ".pem" format. See the <ulink url="#CA-CERT-FILE">ca-cert-file</ulink>
-    for a command to generate it.
+    This directive specifies the name of the CA key file in ".pem" format.
+    The <ulink url="#CA-CERT-FILE">ca-cert-file section</ulink> contains
+    a command to generate it.
    </para>
   </listitem>
  </varlistentry>
@@ -4353,7 +4359,7 @@ ECDHE-RSA-AES256-GCM-SHA384:\
 AES128-SHA
    </screen>
    <screen>
-    # Use keywords instead of explicity naming the ciphers (Does not work with MbedTLS)
+    # Use keywords instead of explicitly naming the ciphers (Does not work with MbedTLS)
     cipher-list ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
    </screen>
   </listitem>