<!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->

##### SUMMARY

Templates do not appear to be evaluated recursively anymore (see #4638).  I don't know when it changed.  I am using Ansible -devel or 2.8.  If it helps, here is the reproducer from issue #4638:

> [playbook.yml]
> 
> ```
> ---
> - name: "test raw template output"
>   hosts: localhost
> 
>   vars:
>     myvar: "foo"
> 
>   tasks:
>     - local_action: template src="mytemplate.j2" dest="/tmp/myoutput.txt"
> 
> ```
>
> [mytemplate.j2]
>
> ```
> Test: Preserve curly braces, and NOT perform variable substitution:
> 
> First Attempt:
> {% raw %}
>   - { include: "{{ myvar }}" }
> {% endraw %}
> ```
>
> [/tmp/myoutput.txt]
>
> ```
> Test: Preserve curly braces, and NOT perform variable substitution:
> 
> 
> First Attempt:
> 
>   - { include: "foo" }
> ```
> 
> NOTE: template output performs variable substitution even inside the {% raw %} block.

and here is the output *I* got:

```
Test: Preserve curly braces, and NOT perform variable substitution:

First Attempt:

  - { include: "{{ myvar }}" }
```

At least, I really hope this is a documentation bug. I think the old behaviour was a bad idea.  I would not like Ansible to go back to it.

##### ISSUE TYPE
- Documentation Report

##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
template

##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```
ansible 2.9.0.dev0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/alan-sysop/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /home/alan-sysop/src/ansible/lib/ansible
  executable location = /home/alan-sysop/src/ansible/bin/ansible
  python version = 2.7.16 (default, Apr 30 2019, 15:54:43) [GCC 9.0.1 20190312 (Red Hat 9.0.1-0.10)]
```

##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->

`ansible-config dump --only-changed` shows no output at all.

##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->

Fedora Workstation 30

##### ADDITIONAL INFORMATION

I'm hoping this is all ancient history now. If so, we can simply remove the sentence in question:

> * Using raw/endraw in Jinja2 will not work as you expect because templates in Ansible are recursively evaluated.

https://docs.ansible.com/ansible/latest/modules/template_module.html#notes
version_added: '2.6'
  force:
    description:
    - Determine when the file is being transferred if the destination already exists.
    - When set to C(yes), replace the remote file when contents are different than the source.
    - When set to C(no), the file will only be transferred if the destination does not exist.
    type: bool
    default: yes
  output_encoding:
    description:
    - Overrides the encoding used to write the template file defined by C(dest).
    - It defaults to C(utf-8), but any encoding supported by python can be used.
    - The source template file must always be encoded using C(utf-8), for homogeneity.
    type: str
    default: utf-8
    version_added: '2.7'
notes:
- Including a string that uses a date in the template will result in the template being marked 'changed' each time.
- Since Ansible 0.9, templates are loaded with C(trim_blocks=True).
- >
  Also, you can override jinja2 settings by adding a special header to template file.
  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.
'''