Unnecessarily confusing documentation with /post

[danskal]

This documentation:
https://redux-toolkit.js.org/rtk-query/usage-with-typescript
contains examples with endpoints called /post, and has Post scattered everywhere in the code. Any reader wanting to use HTTP POST ends up totally confused, and there's no need for it. It would be much better with /foo or /message or /wombat or anything that makes it clear that this is my part of the code, rather than something that RTK needs to be a certain way.

Following this principle (ie. make it very clear what is custom code and what is boilerplate) would ease adoption markedly, as noobs like myself find it really hard to tell what is boilerplate and what is custom code.