<!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->

##### SUMMARY
When I read the `copy` documentation, I couldn't work out what it meant.  Unfortunately, this meant it sounded like it might be a weird sex joke.

It doesn't sound like a big problem, but in an ideal world, I think we should prefer to avoid weird sex jokes in an alias for a parameter called `force`.

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME
copy

##### ADDITIONAL INFORMATION
Issue search tells me "thirsty" was added as an option to the `get_url` module.  In that context, it is appropriate.  But in the context of the `copy` module, it does not make sense, because `copy` only works in the upload direction.

The first three pages of Google Search results (Ansible thirsty) show people using "thirsty" for downloads only, not uploads.  Similarly for GitHub code search (copy thirsty language:YAML).
- This flag indicates that filesystem links in the destination, if they exist, should be followed.
    type: bool
    default: no
    version_added: '1.8'
  local_follow:
    description:
    - This flag indicates that filesystem links in the source tree, if they exist, should be followed.
    type: bool
    default: yes
    version_added: '2.4'
  checksum:
    description:
    - SHA1 checksum of the file being transferred.
    - Used to validate that the copy of the file was successful.
    - If this is not provided, ansible will use the local calculated checksum of the src file.
    type: str
    version_added: '2.5'
extends_documentation_fragment:
- decrypt
- files
- validate
notes:
- The M(copy) module recursively copy facility does not scale to lots (>hundreds) of files.
seealso:
- module: assemble
- module: fetch
- module: file
- module: synchronize
- module: template
- module: win_copy