Sphinx formatting.

docsite/latest/rst/index.rst

@@ -49,7 +49,7 @@ IT tasks in the core distribution.  This means modules are well up-to-date and y
 that will work on your platform.  You may think of the module library as a toolbox full of useful system management tools, 
 and playbooks as the instructions for buildilng something using those tools.
 
-.. toctree:
+.. toctree::
    modules
 
 .. _overview:
@@ -130,7 +130,7 @@ installed using Ansible playbooks!
 Detailed Guides
 ```````````````
 
-This section is new and evolving.  The idea here is explore particular use cases in greater depth and provide a more "top down" explanation of some basic features::
+This section is new and evolving.  The idea here is explore particular use cases in greater depth and provide a more "top down" explanation of some basic features.
 
 .. toctree::
    :maxdepth: 1

docsite/latest/rst/intro_patterns.rst

@@ -1,11 +1,9 @@
-.. _patterns:
+Patterns
+++++++++
 
 .. contents::
    :depth: 2
 
-Patterns
-++++++++
-
 Patterns in Ansible are how we decide which hosts to manage.  This can mean what hosts to communicate with, but in terms
 of :doc:`playbooks` it actually means what hosts to apply a particular configuration or IT process to.
 

docsite/latest/rst/playbooks.rst

@@ -92,7 +92,7 @@ For each play in a playbook, you get to choose which machines in your infrastruc
 to target and what remote user to complete the steps (called tasks) as.
 
 The `hosts` line is a list of one or more groups or host patterns,
-separated by colons, as described in the :ref:`intro_patterns`
+separated by colons, as described in the :doc:`intro_patterns`
 documentation.  The `remote_user` is just the name of the user account::
 
     ---

docsite/latest/rst/playbooks_variables.rst

@@ -669,7 +669,7 @@ The contents of each variables file is a simple YAML dictionary, like this::
 
 .. note::
    It's also possible to keep per-host and per-group variables in very
-   similar files, this is covered in :ref:`patterns`.
+   similar files, this is covered in :ref:`intro_patterns`.
 
 .. _passing_variables_on_the_command_line: