[master] 5f267a4 Restructure the chapter headings in the performance doc in the User's Guide. It had subsections of the Cookies chapter that had nothing to do with them.

[Geoff Simmons]

commit 5f267a48f6b4c96023d13c327abf3f12d13f6dc8
Author: Geoff Simmons <geoff at uplex.de>
Date:   Mon Mar 6 07:14:16 2017 +0100

    Restructure the chapter headings in the performance doc in the User's Guide.
    It had subsections of the Cookies chapter that had nothing to do with them.

diff --git a/doc/sphinx/users-guide/increasing-your-hitrate.rst b/doc/sphinx/users-guide/increasing-your-hitrate.rst
index 38dcc86..fdfbd22 100644
--- a/doc/sphinx/users-guide/increasing-your-hitrate.rst
+++ b/doc/sphinx/users-guide/increasing-your-hitrate.rst
@@ -102,7 +102,7 @@ https://addons.mozilla.org/en-US/firefox/addon/3829/ or by googling
 
 
 The role of HTTP Headers
-~~~~~~~~~~~~~~~~~~~~~~~~
+------------------------
 
 Along with each HTTP request and response comes a bunch of headers
 carrying metadata. Varnish will look at these headers to determine if
@@ -122,7 +122,7 @@ Let's take a look at the important headers you should be aware of:
 .. _users-guide-cookies:
 
 Cookies
--------
+~~~~~~~
 
 Varnish will, in the default configuration, not cache an object coming
 from the backend with a 'Set-Cookie' header present. Also, if the client
@@ -135,7 +135,7 @@ cookie is used by the client side javascript and is therefore of no
 interest to the server.
 
 Cookies from the client
-~~~~~~~~~~~~~~~~~~~~~~~
++++++++++++++++++++++++
 
 For a lot of web applications it makes sense to completely disregard the
 cookies unless you are accessing a special part of the web site. This
@@ -216,7 +216,7 @@ Varnish Cache Wiki.
 
 
 Cookies coming from the backend
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
++++++++++++++++++++++++++++++++
 
 If your backend server sets a cookie using the 'Set-Cookie' header
 Varnish will not cache the page when using the default configuration.