summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPierre Templier <pierre.templier@gmail.com>2018-04-06 07:20:51 +0200
committerscottb <dharmabumstead@users.noreply.github.com>2018-04-05 22:20:51 -0700
commit2340ca7701d50e250c6b797e40bd83da33280199 (patch)
treea46c69586cbbf017d022f9858299c9b472a533af
parent1bf29651af557c875bbae9050724f2e82c65cab1 (diff)
downloadansible-2340ca7701d50e250c6b797e40bd83da33280199.tar.gz
Small typos in docs (#38370)
* Small typos in docs * Fixed wording
-rw-r--r--docs/docsite/rst/porting_guides/porting_guide_2.5.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docsite/rst/porting_guides/porting_guide_2.5.rst b/docs/docsite/rst/porting_guides/porting_guide_2.5.rst
index bc546d0a97..1c7c26fd2d 100644
--- a/docs/docsite/rst/porting_guides/porting_guide_2.5.rst
+++ b/docs/docsite/rst/porting_guides/porting_guide_2.5.rst
@@ -83,7 +83,7 @@ Jinja tests used as filters
Using Ansible-provided jinja tests as filters will be removed in Ansible 2.9.
-Prior to Ansible 2.5, jinja tests included within Ansible were most often used as filters. The large difference in use is that filters are referenced as ``variable | filter_name`` where as jinja tests are refereced as ``variable is test_name``.
+Prior to Ansible 2.5, jinja tests included within Ansible were most often used as filters. The large difference in use is that filters are referenced as ``variable | filter_name`` while jinja tests are referenced as ``variable is test_name``.
Jinja tests are used for comparisons, while filters are used for data manipulation and have different applications in jinja. This change is to help differentiate the concepts for a better understanding of jinja, and where each can be appropriately used.