From 14098d9b045f4048e540560d3bee808cbb87e2fa Mon Sep 17 00:00:00 2001
From: Tommaso Macchioni <51484458+tmacchioni@users.noreply.github.com>
Date: Tue, 22 Mar 2022 16:25:46 +0100
Subject: [PATCH] typo variable reference (#77327)

---
 docs/docsite/rst/user_guide/playbooks_environment.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docsite/rst/user_guide/playbooks_environment.rst b/docs/docsite/rst/user_guide/playbooks_environment.rst
index 4b58658181b..d347812b9c2 100644
--- a/docs/docsite/rst/user_guide/playbooks_environment.rst
+++ b/docs/docsite/rst/user_guide/playbooks_environment.rst
@@ -121,7 +121,7 @@ Some language-specific version managers (such as rbenv and nvm) require you to s
         when: packagejson.stat.exists
 
 .. note::
-   The example above uses ``ansible_env`` as part of the PATH. Basing variables on ``ansible_env`` is risky. Ansible populates ``ansible_env`` values by gathering facts, so the value of the variables depends on the remote_user or become_user Ansible used when gathering those facts. If you change remote_user/become_user the values in ``ansible-env`` may not be the ones you expect.
+   The example above uses ``ansible_env`` as part of the PATH. Basing variables on ``ansible_env`` is risky. Ansible populates ``ansible_env`` values by gathering facts, so the value of the variables depends on the remote_user or become_user Ansible used when gathering those facts. If you change remote_user/become_user the values in ``ansible_env`` may not be the ones you expect.
 
 .. warning::
     Environment variables are normally passed in clear text (shell plugin dependent) so they are not a recommended way of passing secrets to the module being executed.