From 8582df36c5931a488d36bc2efaf8fa5324668538 Mon Sep 17 00:00:00 2001
From: Matt Martz <matt@sivel.net>
Date: Tue, 8 Feb 2022 09:26:37 -0600
Subject: [PATCH] Remove misleading note in template doc fragment. Fixes #61233
 (#76955)

---
 lib/ansible/plugins/doc_fragments/template_common.py | 2 --
 1 file changed, 2 deletions(-)

diff --git a/lib/ansible/plugins/doc_fragments/template_common.py b/lib/ansible/plugins/doc_fragments/template_common.py
index cb7ca6ff1f5..6276e84a62f 100644
--- a/lib/ansible/plugins/doc_fragments/template_common.py
+++ b/lib/ansible/plugins/doc_fragments/template_common.py
@@ -116,8 +116,6 @@ notes:
   i.e. C(#jinja2:variable_start_string:'[%', variable_end_string:'%]', trim_blocks: False)
   which changes the variable interpolation markers to C([% var %]) instead of C({{ var }}).
   This is the best way to prevent evaluation of things that look like, but should not be Jinja2.
-- Using raw/endraw in Jinja2 will not work as you expect because templates in Ansible are recursively
-  evaluated.
 - To find Byte Order Marks in files, use C(Format-Hex <file> -Count 16) on Windows, and use C(od -a -t x1 -N 16 <file>)
   on Linux.
 '''