### Summary

From a mastodon user - the password parameter could make it clearer that is a password hash.

Ideally, the key would be called password_hash instead of password. 

If that is not possible, it would be nice to add a disclaimer that this doesn't encrypt the password for you. You could also extend the examples of the user module to show how to set the user password by calculating the hash with the jinja2 filter.


### Issue Type

Documentation Report

### Component Name

user

### Ansible Version

```console
$ ansible --version
2.15
```


### Configuration

```console
# if using a version older than ansible-core 2.12 you should omit the '-t all'
$ ansible-config dump --only-changed -t all
none
```


### OS / Environment

none

### Additional Information

none

### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
description: Whether or not to create the home directory.
  returned: When user does not exist and not check mode
  type: bool
  sample: True
force:
  description: Whether or not a user account was forcibly deleted.
  returned: When I(state) is C(absent) and user exists
  type: bool
  sample: False
group:
  description: Primary user group ID
  returned: When user exists
  type: int
  sample: 1001
groups:
  description: List of groups of which the user is a member.
  returned: When I(groups) is not empty and I(state) is C(present)
  type: str
  sample: 'chrony,apache'
home:
  description: "Path to user's home directory."
  returned: When I(state) is C(present)
  type: str
  sample: '/home/asmith'
move_home:
  description: Whether or not to move an existing home directory.
  returned: When I(state) is C(present) and user exists
  type: bool
  sample: False
name: