<!--- 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
from __future__ import (absolute_import, division, print_function)
__metaclass__ = type
class ModuleDocFragment(object):
    
    DOCUMENTATION = r'''
description:
- Templates are processed by the L(Jinja2 templating language,http://jinja.pocoo.org/docs/).
- Documentation on the template formatting can be found in the
  L(Template Designer Documentation,http://jinja.pocoo.org/docs/templates/).
- Additional variables listed below can be used in templates.
- C(ansible_managed) (configurable via the C(defaults) section of C(ansible.cfg)) contains a string which can be used to
  describe the template name, host, modification time of the template file and the owner uid.
- C(template_host) contains the node name of the template's machine.
- C(template_uid) is the numeric user id of the owner.
- C(template_path) is the path of the template.
- C(template_fullpath) is the absolute path of the template.
- C(template_destpath) is the path of the template on the remote system (added in 2.8).
- C(template_run_date) is the date that the template was rendered.
options:
  src:
    description:
    - Path of a Jinja2 formatted template on the Ansible controller.
    - This can be a relative or an absolute path.
    - The file must be encoded with C(utf-8) but I(output_encoding) can be used to control the encoding of the output
      template.
    type: path