[4.1] e124a58 Do not leak comments into the generated html

[Lasse Karstensen]

commit e124a585bf2b39e1d288f50a2192781f3f7953e1
Author: Federico G. Schwindt <fgsch at lodoss.net>
Date:   Wed Dec 23 10:40:37 2015 +0000

    Do not leak comments into the generated html

diff --git a/doc/sphinx/users-guide/increasing-your-hitrate.rst b/doc/sphinx/users-guide/increasing-your-hitrate.rst
index fe9219c..08eb09d 100644
--- a/doc/sphinx/users-guide/increasing-your-hitrate.rst
+++ b/doc/sphinx/users-guide/increasing-your-hitrate.rst
@@ -193,7 +193,9 @@ A somewhat simpler example that can accomplish almost the same functionality can
 found below. Instead of filtering out "other" cookies it instead picks out
 "the one" cookie that is needed, copies it to another header and then
 copies it back to the request, deleting the original cookie header.
+
 .. XXX:Verify correctness of request above! benc
+
 ::
 
     sub vcl_recv {
@@ -298,11 +300,9 @@ Normalizing your namespace
 Some sites are accessed via lots of hostnames.
 http://www.varnish-software.com/, http://varnish-software.com/ and
 http://varnishsoftware.com/ all point at the same site. Since Varnish
-doesn't know they are the same,
-.. XXX: heavy meaning change above. benc
-Varnish will cache different versions of every page for every
-hostname. You can mitigate this in your web server configuration
-by setting up redirects or by using the following VCL::
+doesn't know they are the same, Varnish will cache different versions of
+every page for every hostname. You can mitigate this in your web server
+configuration by setting up redirects or by using the following VCL::
 
     if (req.http.host ~ "(?i)^(www.)?varnish-?software.com") {
         set req.http.host = "varnish-software.com";
diff --git a/doc/sphinx/users-guide/operation-logging.rst b/doc/sphinx/users-guide/operation-logging.rst
index bb4c7cc..e6b58f2 100644
--- a/doc/sphinx/users-guide/operation-logging.rst
+++ b/doc/sphinx/users-guide/operation-logging.rst
@@ -31,8 +31,8 @@ You'll see lines like these scrolling slowly by.::
 These is the Varnish master process checking up on the caching process
 to see that everything is OK.
 
-Now go to the browser and reload the page displaying your web
-app.
+Now go to the browser and reload the page displaying your web app.
+
 .. XXX:Doesn't this require a setup of a running varnishd and a web application being cached? benc
 
 You'll see lines like these.::
diff --git a/doc/sphinx/users-guide/operation-statistics.rst b/doc/sphinx/users-guide/operation-statistics.rst
index 7a4827d..af062bd 100644
--- a/doc/sphinx/users-guide/operation-statistics.rst
+++ b/doc/sphinx/users-guide/operation-statistics.rst
@@ -29,11 +29,9 @@ varnishhist
 The :ref:`varnishhist(1)` utility reads :ref:`varnishd(1)` shared
 memory logs and presents a continuously updated histogram showing the
 distribution of the last N requests by their processing.
-.. XXX:1? benc
-The value of N and the
-vertical scale are displayed in the top left corner.  The horizontal
-scale is logarithmic.  Hits are marked with a pipe character ("|"),
-and misses are marked with a hash character ("#").
+The value of N and the vertical scale are displayed in the top left
+corner.  The horizontal scale is logarithmic.  Hits are marked with a
+pipe character ("|"), and misses are marked with a hash character ("#").
 
 varnishstat
 ~~~~~~~~~~~