Made why's sections headings again, but limited the depth in the corr…

…esponding toctree.

docs/index.rst

@@ -67,6 +67,7 @@ About Clize
 -----------
 
 .. toctree::
+    :maxdepth: 1
 
     why
     history
@@ -81,9 +82,9 @@ This section contains tutorials for the most commonly used features of Clize.
 
 .. toctree::
 
-   basics
-   dispatching
-   compositing
+    basics
+    dispatching
+    compositing
 
 
 .. _guides:
@@ -95,9 +96,9 @@ These documents document specific aspects or usages of Clize.
 
 .. toctree::
 
-   parser
-   porting
-   interop
+    parser
+    porting
+    interop
 
 
 .. _references:
@@ -109,5 +110,5 @@ The user reference lists all capabilities of each kind of parameter. The API ref
 
 .. toctree::
 
-   reference
-   api
+    reference
+    api

docs/why.rst

@@ -102,7 +102,8 @@ With Clize, you start simple but you remain flexible throughout, with options fo
 
 .. _other parsers:
 
-.. rubric:: "Why not use an existing parser instead of making your own?"
+"Why not use an existing parser instead of making your own?"
+------------------------------------------------------------
 
 Argument parsing is a rather common need for Python programs. As such, there
 are many argument parsers in existence, including no less than three in the
@@ -125,7 +126,8 @@ by external code and made usable the same way as `clize.parameters.multi` or
 
 .. _wrapper around argparse:
 
-.. rubric:: "Why not create a thin wrapper around argparse?"
+"Why not create a thin wrapper around argparse?"
+------------------------------------------------
 
 Back in Clize's first release, ``argparse``'s parser would have been
 sufficientfor what Clize proposed. I wasn't really interested in dealing with