Update JSON RPC API doc

Author: geo2a

docs/2022-07-18-JSON-RPC-Server-API.md

@@ -1,15 +1,15 @@
 JSON RPC Server API
 ===================
 
-This document details the API and working of the `kore-rpc` executable. This binary has a similar CLI interface to `kore-exec` and running
+This document details the API and working of the `kore-rpc`, `kore-rpc-booster` and `booster-dev` executables. Running
 
 ```bash
 kore-rpc <DEFINITION>.kore --module <MODULE> --server-port <PORT>
 ```
 
 will parse the `<DEFINITION>.kore` file with `<MODULE>` as the main module and then launch a JSON RPC server on port `<PORT>`.
 
-The server runs over sockets and can be interacted with by sending JSON RPC messages. Note that the server listens over raw sockets and doesn't use a high(er)-level protocol like HTTP. The server sends responses as single line strings, with `\n` used as the message delimiter. The server allows for bidirectional communication and once opened, a socket connection can be maintained throughout the session. However, this is not strictly necessary as all the API functions (except for `cancel`) are pure. Also note that the server uses the `id` of the request message as the `id` of the response, which allows the client to link responses back to their requests. It is therefore important to always send a unique `id` with each request witin the current socket session.
+The server runs over sockets and can be interacted with by sending JSON RPC messages. Note that the server listens over raw sockets and doesn't use a high(er)-level protocol like HTTP. The server sends responses as single line strings, with `\n` used as the message delimiter. The server allows for bidirectional communication and once opened, a socket connection can be maintained throughout the session. However, this is not strictly necessary as all the API functions (except for `cancel` and `add-module`) are pure. Also note that the server uses the `id` of the request message as the `id` of the response, which allows the client to link responses back to their requests. It is therefore important to always send a unique `id` with each request witin the current socket session.
 
 # API