fix setCustomConsole and event callback functions

Author: AtibQur

sites/cheerpx/src/content/docs/12-reference/CheerpX.Linux/04-setCustomConsole.md

@@ -7,23 +7,23 @@ description: Configure custom console behavior for handling keyboard input and o
 namespace CheerpX {
 	class Linux {
 		setCustomConsole(
-			writeFunc: (buf: Buffer) => void,
+			writeFunc: (buf: Uint8Array, vt: number) => void,
 			cols: number,
 			rows: number
-		): (keyCode: number) => void;
+		): client.EventListener;
 	}
 }
 ```
 
 ## Parameters
 
-- **writeFunc (`(buf: Buffer) => void`)** - Function to handle the output sent to the console.
+- **writeFunc (`(buf: Uint8Array, vt: number) => void`)** - Function to handle the output sent to the console.
 - **cols (`number`)** - Number of columns for the console.
 - **rows (`number`)** - Number of rows for the console.
 
 ## Returns
 
-`setCustomConsole` returns a function of type `(keyCode: number) => void`. This function should be called to simulate user input by sending key codes to the console.
+`setCustomConsole` returns an event listener function of type `client.EventListener`. This function simulates user input by sending key codes to the console when triggered.
 
 ## Examples
 

sites/cheerpx/src/content/docs/12-reference/CheerpX.Linux/06-event callbacks.md

@@ -8,30 +8,30 @@ The `CheerpX.Linux` instance returned by `create` provides methods to register a
 ### `registerCallback`
 
 ```ts
-registerCallback(eventName: string, callback: (state: string | number) => void): void
+registerCallback(eventName: string, callback: EventListener): void
 ```
 
 Registers a callback function for a specific event type.
 
 **Parameters**
 
 - **eventName (`string`)** - A string specifying the event type. Can be `"cpuActivity"`, `"diskActivity"`, or `"diskLatency"`.
-- **callback (`(state: string | number) => void`)** - A function that will be called when the event occurs. It receives a parameter which varies based on the event type:
-  - For `"cpuActivity"` and `"diskActivity"`: `state` can be either "ready" (idle, no activity at this time) or "wait" (active, currently in use).
+- **callback (`EventListener`)** - A function that will be called when the event occurs. It receives a parameter, `state`, which varies based on the event type:
+  - For `"cpuActivity"` and `"diskActivity"`: `state` can be either `"ready"` (idle, no activity at this time) or `"wait"` (active, currently in use).
   - For `"diskLatency"`: `state` is a number representing the time in milliseconds between requesting and receiving the last disk block from the backend.
 
 ### `unregisterCallback`
 
 ```ts
-unregisterCallback(eventName: string, callback: (state: string | number) => void): void
+unregisterCallback(eventName: string, callback: EventListener): void
 ```
 
 Unregisters a previously registered callback function for a specific event type.
 
 **Parameters**
 
 - **eventName (`string`)** - A string specifying the event type. See the `registerCallback` reference above for the supported event types.
-- **callback (`(state: string | number) => void`)** - The function to be unregistered.
+- **callback (`EventListener`)** - The callback function to unregister, which must be the same function that was previously registered with `registerCallback`.
 
 Example usage: