Typo fix/rebuild

bestpractices.html

@@ -286,7 +286,7 @@ for heterogeneous distributions.  While lots of software packages
 claim to make this easy on you, the configuration files are often
 quite different, to the point where it would be easier to treat them
 as different playbooks.  This is why, for example, Ansible has a
-separate <a class="reference internal" href="modules.html#yum"><em>yum</em></a> and <a class="reference internal" href="modules.html#apt"><em>apt</em></a> module.  Yum and apt have different
+separate &#8216;yum&#8217; and &#8216;apt&#8217; module.  Yum and apt have different
 capabilities, and we don&#8217;t want to code for the least common
 denominator.</p>
 <p>Use variables for user tunable settings versus having constants in the

examples.html

@@ -247,7 +247,7 @@ required.</p>
 <p>Ok, so those are basics.  If you didn&#8217;t read about patterns and groups yet, go back and read <a class="reference internal" href="patterns.html"><em>Inventory &amp; Patterns</em></a>.</p>
 <p>The <tt class="docutils literal"><span class="pre">-f</span> <span class="pre">10</span></tt> in the above specifies the usage of 10 simultaneous
 processes.  Normally commands also take a <tt class="docutils literal"><span class="pre">-m</span></tt> for module name, but
-the default module name is <a class="reference internal" href="modules.html#command"><em>command</em></a>, so we didn&#8217;t need to
+the default module name is &#8216;command&#8217;, so we didn&#8217;t need to
 specify that all of the time.  We&#8217;ll use <tt class="docutils literal"><span class="pre">-m</span></tt> in later examples to
 run some other <a class="reference internal" href="modules.html"><em>Ansible Modules</em></a>.</p>
 <div class="admonition note">
@@ -299,7 +299,7 @@ same options can be passed directly to the <tt class="docutils literal"><span cl
 <div class="section" id="managing-packages">
 <h2><a class="toc-backref" href="#contents">Managing Packages</a><a class="headerlink" href="#managing-packages" title="Permalink to this headline">¶</a></h2>
 <p>There are modules available for yum and apt.  Here are some examples
-with <a class="reference internal" href="modules.html#yum"><em>yum</em></a>.</p>
+with yum.</p>
 <p>Ensure a package is installed, but don&#8217;t update it:</p>
 <div class="highlight-bash"><div class="highlight"><pre><span class="nv">$ </span>ansible webservers -m yum -a <span class="s2">&quot;pkg=acme state=installed&quot;</span>
 </pre></div>
@@ -322,7 +322,7 @@ for other package managers.  Stop by the mailing list for info/details.</p>
 </div>
 <div class="section" id="users-and-groups">
 <h2><a class="toc-backref" href="#contents">Users and Groups</a><a class="headerlink" href="#users-and-groups" title="Permalink to this headline">¶</a></h2>
-<p>The <a class="reference internal" href="modules.html#user"><em>user</em></a> module allows easy creation and manipulation of
+<p>The &#8216;user&#8217; module allows easy creation and manipulation of
 existing user accounts, as well as removal of user accounts that may
 exist:</p>
 <div class="highlight-bash"><div class="highlight"><pre><span class="nv">$ </span>ansible all -m user -a <span class="s2">&quot;name=foo password=&lt;crypted password here&gt;&quot;</span>

moduledev.html

@@ -409,7 +409,7 @@ for you, and allows you to check inputs.</p>
 </pre></div>
 </div>
 <p>And failures are just as simple (where &#8216;msg&#8217; is a required parameter to explain the error):</p>
-<div class="highlight-python"><div class="highlight"><pre><span class="n">module</span><span class="o">.</span><span class="n">exit_json</span><span class="p">(</span><span class="n">msg</span><span class="o">=</span><span class="s">&quot;Something fatal happened&quot;</span><span class="p">)</span>
+<div class="highlight-python"><div class="highlight"><pre><span class="n">module</span><span class="o">.</span><span class="n">fail_json</span><span class="p">(</span><span class="n">msg</span><span class="o">=</span><span class="s">&quot;Something fatal happened&quot;</span><span class="p">)</span>
 </pre></div>
 </div>
 <p>There are also other useful functions in the module class, such as module.md5(path).  See

playbooks.html

@@ -321,7 +321,7 @@ who which to use more advanced templating.  This is optional and the $varname fo
 files.</p>
 <p>If there are discovered variables about the system, called &#8216;facts&#8217;, these variables bubble up back into the
 playbook, and can be used on each system just like explicitly set variables.  Ansible provides several
-of these, prefixed with &#8216;ansible&#8217;, and are documented under <a class="reference internal" href="modules.html#setup"><em>setup</em></a> in the module documentation.  Additionally,
+of these, prefixed with &#8216;ansible&#8217;, and are documented under &#8216;setup&#8217; in the module documentation.  Additionally,
 facts can be gathered by ohai and facter if they are installed.  Facter variables are prefixed with <tt class="docutils literal"><span class="pre">facter_</span></tt> and Ohai
 variables are prefixed with <tt class="docutils literal"><span class="pre">ohai_</span></tt>.</p>
 <p>So for instance, if I wanted

rst/bestpractices.rst

@@ -111,7 +111,7 @@ for heterogeneous distributions.  While lots of software packages
 claim to make this easy on you, the configuration files are often
 quite different, to the point where it would be easier to treat them
 as different playbooks.  This is why, for example, Ansible has a
-separate :ref:`yum` and :ref:`apt` module.  Yum and apt have different
+separate 'yum' and 'apt' module.  Yum and apt have different
 capabilities, and we don't want to code for the least common
 denominator.
 

rst/examples.rst

@@ -59,7 +59,7 @@ Ok, so those are basics.  If you didn't read about patterns and groups yet, go b
 
 The ``-f 10`` in the above specifies the usage of 10 simultaneous
 processes.  Normally commands also take a ``-m`` for module name, but
-the default module name is :ref:`command`, so we didn't need to
+the default module name is 'command', so we didn't need to
 specify that all of the time.  We'll use ``-m`` in later examples to
 run some other :doc:`modules`.
 
@@ -117,7 +117,7 @@ Managing Packages
 `````````````````
 
 There are modules available for yum and apt.  Here are some examples
-with :ref:`yum`.
+with yum.
 
 Ensure a package is installed, but don't update it::
 
@@ -142,7 +142,7 @@ for other package managers.  Stop by the mailing list for info/details.
 Users and Groups
 ````````````````
 
-The :ref:`user` module allows easy creation and manipulation of
+The 'user' module allows easy creation and manipulation of
 existing user accounts, as well as removal of user accounts that may
 exist::
 

rst/modules/_list.rst

@@ -1,39 +1,43 @@
-.. include:: apt_repository.rst
-.. include:: apt.rst
-.. include:: assemble.rst
-.. include:: authorized_key.rst
-.. include:: command.rst
-.. include:: copy.rst
-.. include:: easy_install.rst
-.. include:: facter.rst
-.. include:: fetch.rst
-.. include:: file.rst
-.. include:: fireball.rst
-.. include:: get_url.rst
-.. include:: git.rst
-.. include:: group.rst
-.. include:: ini_file.rst
-.. include:: lineinfile.rst
-.. include:: mount.rst
-.. include:: mysql_db.rst
-.. include:: mysql_user.rst
-.. include:: nagios.rst
-.. include:: ohai.rst
-.. include:: ping.rst
-.. include:: pip.rst
-.. include:: postgresql_db.rst
-.. include:: postgresql_user.rst
-.. include:: raw.rst
-.. include:: service.rst
-.. include:: seboolean.rst
-.. include:: selinux.rst
-.. include:: setup.rst
-.. include:: shell.rst
-.. include:: slurp.rst
-.. include:: subversion.rst
-.. include:: supervisorctl.rst
-.. include:: template.rst
-.. include:: user.rst
-.. include:: wait_for.rst
-.. include:: virt.rst
-.. include:: yum.rst
+.. Generated by module_formatter
+.. include:: modules/subversion.rst
+.. include:: modules/git.rst
+.. include:: modules/get_url.rst
+.. include:: modules/shell.rst
+.. include:: modules/raw.rst
+.. include:: modules/pause.rst
+.. include:: modules/postgresql_db.rst
+.. include:: modules/easy_install.rst
+.. include:: modules/user.rst
+.. include:: modules/seboolean.rst
+.. include:: modules/selinux.rst
+.. include:: modules/nagios.rst
+.. include:: modules/command.rst
+.. include:: modules/fail.rst
+.. include:: modules/assemble.rst
+.. include:: modules/fetch.rst
+.. include:: modules/apt.rst
+.. include:: modules/ohai.rst
+.. include:: modules/ping.rst
+.. include:: modules/postgresql_user.rst
+.. include:: modules/service.rst
+.. include:: modules/ini_file.rst
+.. include:: modules/template.rst
+.. include:: modules/mysql_user.rst
+.. include:: modules/apt_repository.rst
+.. include:: modules/setup.rst
+.. include:: modules/fireball.rst
+.. include:: modules/mysql_db.rst
+.. include:: modules/yum.rst
+.. include:: modules/async_status.rst
+.. include:: modules/virt.rst
+.. include:: modules/file.rst
+.. include:: modules/copy.rst
+.. include:: modules/supervisorctl.rst
+.. include:: modules/slurp.rst
+.. include:: modules/authorized_key.rst
+.. include:: modules/lineinfile.rst
+.. include:: modules/wait_for.rst
+.. include:: modules/facter.rst
+.. include:: modules/group.rst
+.. include:: modules/pip.rst
+.. include:: modules/mount.rst

rst/playbooks.rst

@@ -144,7 +144,7 @@ files.
 
 If there are discovered variables about the system, called 'facts', these variables bubble up back into the
 playbook, and can be used on each system just like explicitly set variables.  Ansible provides several
-of these, prefixed with 'ansible', and are documented under :ref:`setup` in the module documentation.  Additionally,
+of these, prefixed with 'ansible', and are documented under 'setup' in the module documentation.  Additionally,
 facts can be gathered by ohai and facter if they are installed.  Facter variables are prefixed with ``facter_`` and Ohai
 variables are prefixed with ``ohai_``.