##### SUMMARY
The warning that `become` show, point to a non-existing page.

The reference: https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user
Should be: https://docs.ansible.com/ansible/user_guide/become.html#risks-of-becoming-an-unprivileged-user

```
  msg: |-
    Failed to set permissions on the temporary files Ansible needs to create when becoming an unprivileged user (rc: 1, err: chown: changing ownership of '/var/tmp/ansible-tmp-1587201990.1515293-106086999273646/': Operation not permitted
    chown: changing ownership of '/var/tmp/ansible-tmp-1587201990.1515293-106086999273646/AnsiballZ_postgresql_db.py': Operation not permitted
    }). For information on working around this, see https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user
```

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
become

##### ANSIBLE VERSION
```
ansible 2.9.6
  config file = None
  configured module search path = ['/home/robertdb/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.7.6 (default, Jan 30 2020, 09:44:41) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
```

##### CONFIGURATION
```
# empty.
```

##### OS / ENVIRONMENT
Controller: Fedora 31
Managed node: Ubuntu 19

##### STEPS TO REPRODUCE
I use [this](https://github.com/robertdebock/ansible-role-postgres/blob/master/tasks/main.yml#L70) role on Ubuntu 19. (Using [this](https://github.com/robertdebock/ansible-tester) code.

##### EXPECTED RESULTS
The chapter is found immediately.

##### ACTUAL RESULTS
The documentation page loads (good), but does not jump to the right chapter.
"""
        We need the files we upload to be readable (and sometimes executable)
        by the user being sudo'd to but we want to limit other people's access
        (because the files could contain passwords or other private
        information.  We achieve this in one of these ways:
        * If no sudo is performed or the remote_user is sudo'ing to
          themselves, we don't have to change permissions.
        * If the remote_user sudo's to a privileged user (for instance, root),
          we don't have to change permissions
        * If the remote_user sudo's to an unprivileged user then we attempt to
          grant the unprivileged user access via file system acls.
        * If granting file system acls fails we try to change the owner of the
          file with chown which only works in case the remote_user is
          privileged or the remote systems allows chown calls by unprivileged
          users (e.g. HP-UX)
        * If the chown fails we can set the file to be world readable so that
          the second unprivileged user can read the file.
          Since this could allow other users to get access to private