From 41a10ff78439dde26733ad27166cb604692bd0ea Mon Sep 17 00:00:00 2001 From: "patchback[bot]" <45432694+patchback[bot]@users.noreply.github.com> Date: Wed, 25 Mar 2026 08:17:28 +0000 Subject: [PATCH] Improve inclusivity of "Christmas vacation" (#3521) (#3551) * Improve inclusivity of "Christmas vacation" This PR updates wording in the "Why use ad hoc commands?" section. The phrase "Christmas vacation" was replaced with "holiday vacation" to make the example more globally inclusive, since Ansible is used by people from many cultures. No functional changes. Documentation only. * Apply suggestion from @oraNod --------- (cherry picked from commit 9ba07abe00d4915bd50da26e51674c8b9b4d9e7a) Co-authored-by: ashokraoc Co-authored-by: Don Naro --- docs/docsite/rst/command_guide/intro_adhoc.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/command_guide/intro_adhoc.rst b/docs/docsite/rst/command_guide/intro_adhoc.rst index 91b2bc286e..524867b9ff 100644 --- a/docs/docsite/rst/command_guide/intro_adhoc.rst +++ b/docs/docsite/rst/command_guide/intro_adhoc.rst @@ -17,7 +17,7 @@ Before reading and executing these examples, please read :ref:`intro_inventory`. Why use ad hoc commands? ======================== -ad hoc commands are great for tasks you repeat rarely. For example, if you want to power off all the machines in your lab for Christmas vacation, you could execute a quick one-liner in Ansible without writing a playbook. An ad hoc command looks like this: +ad hoc commands are great for tasks you repeat rarely. For example, if you want to power off all the machines in your lab when you go on vacation, you could execute a quick one-liner in Ansible without writing a playbook. An ad hoc command looks like this: .. code-block:: bash