Remove unnecessary sentences for return codes in the API documentation
What does this MR do?
Remove unnecessary sentences for return codes in the API documentation
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
To get consistency and avoid confusion as the real return code when succeed for POST is 201 and not 200 as the actual documentation indicates .
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
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