Skip to content

Fix wrong example in api/users documentation

What does this MR do?

Just a small typo fix in API docs. While greping for this typo I also found couple more places with same mistake and included them in the MR too.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Because current example in events API documentation is broken :)

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Merge request reports

Loading