From dea19070e2de98aaf39df086bc2f1274ad0b5388 Mon Sep 17 00:00:00 2001 From: kustodian Date: Fri, 18 Jul 2014 20:29:25 +0200 Subject: [PATCH] Fixed documentation in playbooks_variables.rst --- docsite/rst/playbooks_variables.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index f277b1b2a09..f072c098969 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