From a5b02d6c7c9252fdda5a33ac96f9438a4a2e17a6 Mon Sep 17 00:00:00 2001 From: Greg Chavez Date: Wed, 29 Aug 2018 10:14:09 -0400 Subject: [PATCH] "encountered" is an adj. here, need vb. "are" (#44833) +label: docsite_pr --- docs/docsite/rst/user_guide/playbooks_reuse_includes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/user_guide/playbooks_reuse_includes.rst b/docs/docsite/rst/user_guide/playbooks_reuse_includes.rst index c50fdc99a2..e0d8910a28 100644 --- a/docs/docsite/rst/user_guide/playbooks_reuse_includes.rst +++ b/docs/docsite/rst/user_guide/playbooks_reuse_includes.rst @@ -9,7 +9,7 @@ Includes vs. Imports As noted in :doc:`playbooks_reuse`, include and import statements are very similar, however the Ansible executor engine treats them very differently. - All ``import*`` statements are pre-processed at the time playbooks are parsed. -- All ``include*`` statements are processed as they encountered during the execution of the playbook. +- All ``include*`` statements are processed as they are encountered during the execution of the playbook. Please refer to :doc:`playbooks_reuse` for documentation concerning the trade-offs one may encounter when using each type.