Jinja2 link doc fixes

docsite/latest/rst/intro_adhoc.rst

@@ -29,7 +29,7 @@ port over directly to the playbook language.
 
 (See :doc:`playbooks` for more information about those)
 
-If you haven't read `intro_inventroy` already, please look that over a bit first
+If you haven't read :doc:`intro_inventory` already, please look that over a bit first
 and then we'll get going.
 
 .. contents::
@@ -77,7 +77,7 @@ It is also possible to sudo to a user other than root using
 Ok, so those are basics.  If you didn't read about patterns and groups yet, go back and read :doc:`intro_patterns`.
 
 The ``-f 10`` in the above specifies the usage of 10 simultaneous
-processes to use.   You can also set this in `intro_config` to avoid setting it again.  The default is actually 5, which
+processes to use.   You can also set this in :doc:`intro_config` to avoid setting it again.  The default is actually 5, which
 is really small and conservative.  You are probably going to want to talk to a lot more simultaneous hosts so feel free
 to crank this up.  If you have more hosts than the value set for the fork count, Ansible will talk to them, but it will
 take a little longer.  Feel free to push this value as high as your system can handle it!
@@ -243,7 +243,7 @@ system.  These can be used to implement conditional execution of tasks but also
 
 Its also possible to filter this output to just export certain facts, see the "setup" module documentation for details.
 
-Read more about facts at `playbooks_variables` once you're ready to read up on `playbooks`. 
+Read more about facts at :doc:`playbooks_variables` once you're ready to read up on :doc:`playbooks`. 
 
 Limiting Selected Hosts
 ```````````````````````

docsite/latest/rst/intro_configuration.rst

@@ -57,7 +57,7 @@ different locations::
 
    action_plugins = /usr/share/ansible_plugins/action_plugins
 
-Most users will not need to use this feature.  See `developing_plugins` for more details.
+Most users will not need to use this feature.  See :doc:`developing_plugins` for more details.
 
 ansible_managed
 ===============
@@ -100,7 +100,7 @@ different locations::
 
    action_plugins = /usr/share/ansible_plugins/action_plugins
 
-Most users will not need to use this feature.  See `developing_plugins` for more details
+Most users will not need to use this feature.  See :doc:`developing_plugins` for more details
 
 connection_plugins
 ==================
@@ -110,7 +110,7 @@ different locations::
 
    action_plugins = /usr/share/ansible_plugins/action_plugins
 
-Most users will not need to use this feature.  See `developing_plugins` for more details
+Most users will not need to use this feature.  See :doc:`developing_plugins` for more details
 
 display_skipped_hosts
 =====================
@@ -164,7 +164,7 @@ Note that /usr/bin/ansible always requires a host pattern and does not use this
 poll_interval
 =============
 
-For asynchronous tasks in Ansible (covered in `playbooks_async`), this is how often to check back on the status of those
+For asynchronous tasks in Ansible (covered in :doc:`playbooks_async`), this is how often to check back on the status of those
 tasks when an explicit poll interval is not supplied.  The default is a reasonably moderate 15 seconds which is a tradeoff
 between checking in frequently and providing a quick turnaround when something may have completed::
 
@@ -173,7 +173,7 @@ between checking in frequently and providing a quick turnaround when something m
 hash_behavior
 =============
 
-Ansible by default will override variables in specific precedence orders, as described in `playbooks_variables`.  When a variable
+Ansible by default will override variables in specific precedence orders, as described in :doc:`playbooks_variables`.  When a variable
 of higher precedence wins, it will replace the other value.  
 
 Some users prefer that variables that are hashes (aka 'dictionaries' in Python terms) are merged together.  This setting is called 'merge'. This is not the default behavior and it does not affect variables whose values are scalars (integers, strings) or
@@ -195,7 +195,7 @@ to talk to::
 host_key_checking
 =================
 
-As described in `intro_gettingstarted`, host key checking is on by default in Ansible 1.3 and later.  If you understand the
+As described in :doc:`intro_gettingstarted`, host key checking is on by default in Ansible 1.3 and later.  If you understand the
 implications and wish to disable it, you may do so here by setting the value to False::
 
     host_key_checking=True
@@ -208,7 +208,7 @@ different locations::
 
    action_plugins = /usr/share/ansible_plugins/action_plugins
 
-Most users will not need to use this feature.  See `developing_plugins` for more details
+Most users will not need to use this feature.  See :doc:`developing_plugins` for more details
 
 jinja2_extensions
 =================
@@ -259,7 +259,7 @@ different locations::
 
    action_plugins = /usr/share/ansible_plugins/action_plugins
 
-Most users will not need to use this feature.  See `developing_plugins` for more details
+Most users will not need to use this feature.  See :doc:`developing_plugins` for more details
 
 module_name
 ===========
@@ -375,7 +375,7 @@ different locations::
 
    action_plugins = /usr/share/ansible_plugins/action_plugins
 
-Most users will not need to use this feature.  See `developing_plugins` for more details
+Most users will not need to use this feature.  See :doc:`developing_plugins` for more details
 
 
 Paramiko Specific Settings

docsite/latest/rst/intro_dynamic_inventory.rst

@@ -4,7 +4,8 @@ Dynamic Inventory
 =================
 
 Often a user of a configuration management system will want to keep inventory
-in a different system.  
+in a different software system.  Ansible provides a basic system as described in
+`intro_inventory` but what if you want to use something else?
 
 Frequent examples include pulling inventory from a cloud provider, LDAP, `Cobbler <http://cobbler.github.com>`_,
 or a piece of expensive enterprisey CMDB software.