Following up on #14
Add a note to the README about how next-rpc relates to Next.js api routes. Explain it's not intended as a full replacement and more as a complement to. Some use cases (e.g. want to leverage browser caching) are better solved by API routes and that's ok.