Improved backend docs

Author: D-K-P

docs/realtime/backend/metadata.mdx

@@ -219,8 +219,4 @@ async function monitorTypedProgress(runId: string) {
 }
 ```
 
-## Authentication
-
-Backend metadata subscriptions support both server-side and client-side authentication. For server-side authentication, use your API key. For client-side authentication, you must generate a public access token with read access to the specific run, task, or tag. See our [authentication guide](/realtime/auth) for details.
-
 <RealtimeExamplesCards />{" "}

docs/realtime/backend/overview.mdx

@@ -16,6 +16,15 @@ The backend API provides three main categories of functionality:
 - **[Metadata](/realtime/backend/metadata)** - Update and subscribe to run metadata in real-time
 - **[Streams](/realtime/backend/streams)** - Emit and consume real-time streaming data from your tasks
 
+## Authentication
+
+All backend functions support both server-side and client-side authentication:
+
+- **Server-side**: Use your API key (automatically handled in tasks)
+- **Client-side**: Generate a Public Access Token with appropriate scopes
+
+See our [authentication guide](/realtime/auth) for detailed information on creating and using tokens.
+
 ## Quick example
 
 Subscribe to a run:
@@ -51,13 +60,4 @@ export const myTask = task({
 });
 ```
 
-## Authentication
-
-All backend functions support both server-side and client-side authentication:
-
-- **Server-side**: Use your API key (automatically handled in tasks)
-- **Client-side**: Generate a Public Access Token with appropriate scopes
-
-See our [authentication guide](/realtime/auth) for detailed information on creating and using tokens.
-
 <RealtimeExamplesCards />{" "}

docs/realtime/backend/subscribe.mdx

@@ -10,8 +10,6 @@ These functions allow you to subscribe to run updates from your backend code. Ea
 
 Subscribes to all changes to a specific run.
 
-<RequestExample>
-
 ```ts Example
 import { runs } from "@trigger.dev/sdk/v3";
 
@@ -20,8 +18,6 @@ for await (const run of runs.subscribeToRun("run_1234")) {
 }
 ```
 
-</RequestExample>
-
 This function subscribes to all changes to a run. It returns an async iterator that yields the run object whenever the run is updated. The iterator will complete when the run is finished.
 
 **Authentication**: This function supports both server-side and client-side authentication. For server-side authentication, use your API key. For client-side authentication, you must generate a public access token with read access to the specific run. See our [authentication guide](/realtime/auth) for details.
@@ -32,8 +28,6 @@ This function subscribes to all changes to a run. It returns an async iterator t
 
 Subscribes to all changes to runs with a specific tag.
 
-<RequestExample>
-
 ```ts Example
 import { runs } from "@trigger.dev/sdk/v3";
 
@@ -42,8 +36,6 @@ for await (const run of runs.subscribeToRunsWithTag("user:1234")) {
 }
 ```
 
-</RequestExample>
-
 This function subscribes to all changes to runs with a specific tag. It returns an async iterator that yields the run object whenever a run with the specified tag is updated. This iterator will never complete, so you must manually break out of the loop when you no longer want to receive updates.
 
 **Authentication**: This function supports both server-side and client-side authentication. For server-side authentication, use your API key. For client-side authentication, you must generate a public access token with read access to the specific tag. See our [authentication guide](/realtime/auth) for details.
@@ -54,8 +46,6 @@ This function subscribes to all changes to runs with a specific tag. It returns
 
 Subscribes to all changes for runs in a batch.
 
-<RequestExample>
-
 ```ts Example
 import { runs } from "@trigger.dev/sdk/v3";
 
@@ -64,8 +54,6 @@ for await (const run of runs.subscribeToBatch("batch_1234")) {
 }
 ```
 
-</RequestExample>
-
 This function subscribes to all changes for runs in a batch. It returns an async iterator that yields a run object whenever a run in the batch is updated. The iterator does not complete on its own, you must manually `break` the loop when you want to stop listening for updates.
 
 **Authentication**: This function supports both server-side and client-side authentication. For server-side authentication, use your API key. For client-side authentication, you must generate a public access token with read access to the specific batch. See our [authentication guide](/realtime/auth) for details.