From 2d7e019dd2d647f494ac03b4b0f6089626a3a484 Mon Sep 17 00:00:00 2001
From: Steven Robertson <srtrumpetaggie@gmail.com>
Date: Tue, 17 Mar 2020 21:09:13 -0700
Subject: [PATCH] Update docs/ansible_detailed.rst

Co-Authored-By: Jacob Floyd <cognifloyd@gmail.com>
---
 docs/ansible_detailed.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/ansible_detailed.rst b/docs/ansible_detailed.rst
index 07acb0a3..27798faa 100644
--- a/docs/ansible_detailed.rst
+++ b/docs/ansible_detailed.rst
@@ -243,7 +243,9 @@ Noteworthy Differences
 ..
     * The ``ansible_python_interpreter`` variable is parsed using a restrictive
       :mod:`shell-like <shlex>` syntax, permitting values such as ``/usr/bin/env
-      FOO=bar python`` or ``source /opt/rh/rh-python36/enable && python``, which occur in practice. Jinja2 templating is also supported for complex task-level interpreter settings. Ansible `documents this
+      FOO=bar python`` or ``source /opt/rh/rh-python36/enable && python``, which
+      occur in practice. Jinja2 templating is also supported for complex task-level
+      interpreter settings. Ansible `documents this
       <https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html#ansible-python-interpreter>`_
       as an absolute path, however the implementation passes it unquoted through
       the shell, permitting arbitrary code to be injected.