Apply copilot suggestions

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: mwillbanks

versioned_docs/version-3.x/reference/server-adapters/custom.mdx

@@ -40,9 +40,7 @@ import type { RequestContext } from '@zenstackhq/server/types';
 
 interface NodeAdapterOptions<Schema extends SchemaDef> extends CommonAdapterOptions<Schema> {
     prefix?: string;
-    getClient(request: IncomingMessage, response: ServerResponse):
-        | ClientContract<Schema>
-        | Promise<ClientContract<Schema>>;
+    getClient(request: IncomingMessage, response: ServerResponse): ClientContract<Schema> | Promise<ClientContract<Schema>>;
 }
 
 export function createNodeAdapter<Schema extends SchemaDef>(
@@ -125,7 +123,7 @@ createServer(
     createNodeAdapter({
         prefix: '/api',
         apiHandler: handler,
-        getClient: () => /* return a tenant-aware ZenStack client */,
+        getClient: (req, res) => /* return a tenant-aware ZenStack client based on req */,
     }),
 ).listen(3000);
 ```

versioned_docs/version-3.x/service/api-handler/custom.md

@@ -9,11 +9,11 @@ description: Extend or implement ZenStack API handlers to match your backend con
 
 ## Overview
 
-ZenStack ships ready-to-use REST and RPC handlers, but you can tailor their behavior or author brand new handlers without leaving TypeScript. The server package exposes the handler contracts through `@zenstackhq/server/types`, utility helpers from `@zenstackhq/server/api`, all built-in handlers expose their methods as `protected` to allow for extension points. You can:
+ZenStack ships ready-to-use REST and RPC handlers, but you can tailor their behavior or author brand new handlers without leaving TypeScript. The server package exposes the handler contracts through `@zenstackhq/server/types` and utility helpers from `@zenstackhq/server/api`. All built-in handlers expose their methods as `protected` to allow for extension points. You can:
 
-- override parts of the REST or RPC pipeline (filtering, serialization, validation, error handling, and more);
-- wrap the default handlers with extra behavior (multi-tenancy, telemetry, custom logging);
-- implement a handler from scratch while still benefiting from ZenStack's schema and serialization helpers.
+- override parts of the REST or RPC pipeline (filtering, serialization, validation, error handling, and more)
+- wrap the default handlers with extra behavior (multi-tenancy, telemetry, custom logging)
+- implement a handler from scratch while still benefiting from ZenStack's schema and serialization helpers
 
 ## Core building blocks