From e35c4be1c1a5e40d1b5e2b33ac04e83e4a5fc4e7 Mon Sep 17 00:00:00 2001
From: FloMiau <37121807+FloMiau@users.noreply.github.com>
Date: Wed, 12 Sep 2018 21:52:22 +0200
Subject: [PATCH] Change "Defaulting Undefined Variables" (#41379)

Rewording the text for the second parameter of default because the original text was misunderstandable. +label: docsite_pr
---
 docs/docsite/rst/user_guide/playbooks_filters.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docsite/rst/user_guide/playbooks_filters.rst b/docs/docsite/rst/user_guide/playbooks_filters.rst
index d8cbebcc422..7eab897cc0d 100644
--- a/docs/docsite/rst/user_guide/playbooks_filters.rst
+++ b/docs/docsite/rst/user_guide/playbooks_filters.rst
@@ -89,8 +89,8 @@ Jinja2 provides a useful 'default' filter that is often a better approach to fai
 In the above example, if the variable 'some_variable' is not defined, the value used will be 5, rather than an error
 being raised.
 
-If the variable evaluates to an empty string, the second parameter of the filter should be set to
-`true`::
+If you want to use the default value when variables evaluate to false or an empty string you have to set the second parameter to
+``true``::
 
     {{ lookup('env', 'MY_USER') | default('admin', true) }}