Fixing links like zelda

Author: D-K-P

docs/guides/example-projects/batch-llm-evaluator.mdx

@@ -39,7 +39,7 @@ This demo is a full stack example that uses the following:
 - View the Trigger.dev task code in the [src/trigger/batch.ts](https://github.com/triggerdotdev/examples/blob/main/batch-llm-evaluator/src/trigger/batch.ts) file.
 - The `evaluateModels` task uses the `batch.triggerByTaskAndWait` method to distribute the task to the different LLM models.
 - It then passes the results through to a `summarizeEvals` task that calculates some dummy "tags" for each LLM response.
-- We use a [useRealtimeRunsWithTag](/realtime/react-hooks/realtime#userealtimerunswithtag) hook to subscribe to the different evaluation tasks runs in the [src/components/llm-evaluator.tsx](https://github.com/triggerdotdev/examples/blob/main/batch-llm-evaluator/src/components/llm-evaluator.tsx) file.
+- We use a [useRealtimeRunsWithTag](/realtime/react-hooks/subscribe#userealtimerunswithtag) hook to subscribe to the different evaluation tasks runs in the [src/components/llm-evaluator.tsx](https://github.com/triggerdotdev/examples/blob/main/batch-llm-evaluator/src/components/llm-evaluator.tsx) file.
 - We then pass the relevant run down into three different components for the different models:
   - The `AnthropicEval` component: [src/components/evals/Anthropic.tsx](https://github.com/triggerdotdev/examples/blob/main/batch-llm-evaluator/src/components/evals/Anthropic.tsx)
   - The `XAIEval` component: [src/components/evals/XAI.tsx](https://github.com/triggerdotdev/examples/blob/main/batch-llm-evaluator/src/components/evals/XAI.tsx)

docs/guides/example-projects/vercel-ai-sdk-image-generator.mdx

@@ -11,7 +11,7 @@ import RealtimeLearnMore from "/snippets/realtime-learn-more.mdx";
 This demo is a full stack example that uses the following:
 
 - A [Next.js](https://nextjs.org/) app using [shadcn](https://ui.shadcn.com/) for the UI
-- Our 'useRealtimeRun' [React hook](/realtime/react-hooks/realtime) to subscribe to the run and show updates on the frontend
+- Our 'useRealtimeRun' [React hook](/realtime/react-hooks/subscribe#userealtimerun) to subscribe to the run and show updates on the frontend
 - The [Vercel AI SDK](https://sdk.vercel.ai/docs/introduction) to [generate images](https://sdk.vercel.ai/docs/ai-sdk-core/image-generation) using OpenAI's DALL-E models
 
 ## GitHub repo
@@ -36,6 +36,6 @@ This demo is a full stack example that uses the following:
 ## Relevant code
 
 - View the Trigger.dev task code which generates the image using the Vercel AI SDK in [src/trigger/realtime-generate-image.ts](https://github.com/triggerdotdev/examples/tree/main/vercel-ai-sdk-image-generator/src/trigger/realtime-generate-image.ts).
-- We use a [useRealtimeRun](/realtime/react-hooks/realtime#userealtimerun) hook to subscribe to the run in [src/app/processing/[id]/ProcessingContent.tsx](https://github.com/triggerdotdev/examples/tree/main/vercel-ai-sdk-image-generator/src/app/processing/[id]/ProcessingContent.tsx).
+- We use a [useRealtimeRun](/realtime/react-hooks/subscribe#userealtimerun) hook to subscribe to the run in [src/app/processing/[id]/ProcessingContent.tsx](https://github.com/triggerdotdev/examples/tree/main/vercel-ai-sdk-image-generator/src/app/processing/[id]/ProcessingContent.tsx).
 
 <RealtimeLearnMore />

docs/realtime/backend/streams.mdx

@@ -4,8 +4,6 @@ sidebarTitle: Streams
 description: Emit and consume real-time streaming data from your tasks
 ---
 
-import RealtimeExamplesCards from "/snippets/realtime-examples-cards.mdx";
-
 The Streams API allows you to stream data from your tasks to the outside world in realtime using the [metadata](/runs/metadata) system. This is particularly useful for streaming LLM outputs or any other real-time data.
 
 <Note>
@@ -351,5 +349,3 @@ export const aiStreamingWithTools = schemaTask({
   },
 });
 ```
-
-<RealtimeExamplesCards />{" "}

docs/realtime/backend/subscribe.mdx

@@ -109,8 +109,8 @@ The metadata API allows you to update custom metadata on runs and receive real-t
 
 <Note>
   For frontend applications using React, see our [React hooks metadata
-  documentation](/realtime/react-hooks/realtime#using-metadata) for consuming metadata updates in
-  your UI.
+  documentation](/realtime/react-hooks/subscribe#using-metadata-to-show-progress-in-your-ui) for
+  consuming metadata updates in your UI.
 </Note>
 
 When you update metadata from within a task using `metadata.set()`, `metadata.append()`, or other metadata methods, all subscribers to that run will automatically receive the updated run object containing the new metadata.

docs/realtime/react-hooks/overview.mdx

@@ -58,7 +58,7 @@ Learn more about [generating and managing tokens in our authentication guide](/r
 We provide several categories of hooks:
 
 - **[Triggering hooks](/realtime/react-hooks/triggering)** - Trigger tasks from your frontend application
-- **[Subscribe hooks](/realtime/react-hooks/realtime)** - Subscribe to runs, batches, metadata, and more
+- **[Subscribe hooks](/realtime/react-hooks/subscribe)** - Subscribe to runs, batches, metadata, and more
 - **[Streams hooks](/realtime/react-hooks/streams)** - Subscribe to real-time streams from your tasks
 - **[SWR hooks](/realtime/react-hooks/swr)** - Fetch data once and cache it using SWR
 

docs/realtime/react-hooks/streams.mdx

@@ -218,4 +218,4 @@ export function MyComponent({
 }
 ```
 
-All other options (accessToken, baseURL, enabled, id) work the same as the other realtime hooks. See our [realtime hooks documentation](/realtime/react-hooks/realtime#common-options) for more details.
+All other options (accessToken, baseURL, enabled, id) work the same as the other realtime hooks.

docs/realtime/react-hooks/swr.mdx

@@ -7,9 +7,9 @@ description: Fetch and cache data using SWR-based hooks
 SWR hooks use the [swr](https://swr.vercel.app/) library to fetch data once and cache it. These hooks are useful when you need to fetch data without real-time updates.
 
 <Note>
-  While SWR can be configured to poll for updates, we recommend using the [Realtime
-  hooks](/realtime/react-hooks/realtime) for most use-cases due to rate-limits and the way the
-  Trigger.dev API works.
+  While SWR can be configured to poll for updates, we recommend using our other [Realtime
+  hooks](/realtime/react-hooks/) for most use-cases due to rate-limits and the way the Trigger.dev
+  API works.
 </Note>
 
 ## useRun