From 77a4dcca8537fc97334ba8f9e84134b938c694ef Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Sun, 21 Jul 2013 11:18:07 -0400 Subject: [PATCH] Sphinx/docs syntax fixes --- docsite/latest/rst/glossary.rst | 5 ++--- docsite/latest/rst/playbooks.rst | 6 +++--- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/docsite/latest/rst/glossary.rst b/docsite/latest/rst/glossary.rst index d650ba76e5..ea0d7b1d2b 100644 --- a/docsite/latest/rst/glossary.rst +++ b/docsite/latest/rst/glossary.rst @@ -10,8 +10,7 @@ when a term comes up on the mailing list. Action ++++++ -An action is a part of a task that specifies which one of the :ref:`modules` will run, and the arguments to pass to that module. Each task can -have only one action, but it may also have other parameters. +An action is a part of a task that specifies which of the modules to run and the arguments to pass to that module. Each task can have only one action, but it may also have other parameters. Ad Hoc ++++++ @@ -159,7 +158,7 @@ them in the inventory file. The Host Vars file can also be used to define compl inventory file. Lazy Evaluation -++++++++++++++ ++++++++++++++++ In general, Ansible evaluates any variables in playbook content at the last possible second, which means that if you define a data structure that data structure itself can define variable values within it, and everything "just works" as you would expect. This also means variable diff --git a/docsite/latest/rst/playbooks.rst b/docsite/latest/rst/playbooks.rst index 535d28ef01..18637a1cf6 100644 --- a/docsite/latest/rst/playbooks.rst +++ b/docsite/latest/rst/playbooks.rst @@ -541,9 +541,9 @@ If you want to define certain tasks to happen before AND after roles are applied - shell: echo 'goodbye' .. note:: -If you are using tags with tasks (described later as a means of only running part of a playbook) -be sure you also tag your pre_tasks and post_tasks and pass those along as well, especially if the pre -and post tasks are used for monitoring outage window control or load balancing. + If using tags with tasks (described later as a means of only running part of a playbook), + be sure to also tag your pre_tasks and post_tasks and pass those along as well, especially if the pre + and post tasks are used for monitoring outage window control or load balancing. Executing A Playbook ````````````````````