summaryrefslogtreecommitdiff
path: root/docsite
diff options
context:
space:
mode:
authorkustodian <kustodian@gmail.com>2014-07-18 20:29:25 +0200
committerkustodian <kustodian@gmail.com>2014-07-18 20:29:25 +0200
commitdea19070e2de98aaf39df086bc2f1274ad0b5388 (patch)
tree8c31360d4c4cd0fa292b94810e245e288ccd345d /docsite
parentcc6ad40534cdddcbf9e439ac2d18a8cc3251019e (diff)
downloadansible-dea19070e2de98aaf39df086bc2f1274ad0b5388.tar.gz
Fixed documentation in playbooks_variables.rst
Diffstat (limited to 'docsite')
-rw-r--r--docsite/rst/playbooks_variables.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst
index f277b1b2a0..f072c09896 100644
--- a/docsite/rst/playbooks_variables.rst
+++ b/docsite/rst/playbooks_variables.rst
@@ -1029,7 +1029,7 @@ can set variables in there and make use of them in other roles and elsewhere in
- { role: something_else }
.. note:: There are some protections in place to avoid the need to namespace variables.
- In the above, variables defined in common_settings are most definitely available to 'app_user' and 'something_else' tasks, but if
+ In the above, variables defined in common_settings are most definitely available to 'something' and 'something_else' tasks, but if
"something's" guaranteed to have foo set at 12, even if somewhere deep in common settings it set foo to 20.
So, that's precedence, explained in a more direct way. Don't worry about precedence, just think about if your role is defining a