Update documentation of user creation by replacing the 'confirm' param with 'skip_confirmation'
What does this MR do?
It updates the API documentation for POST /users to match API v4.
Are there points in the code the reviewer needs to double check?
Just make sure I didn't do anything dumb.
Why was this MR needed?
So people aren't confused when reading documentation.
Screenshots (if relevant)
N/A
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
- Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together