@@ -363,5 +363,5 @@ Remove the call and assert after the action's promise resolves.
 - [Forms](/guides/forms): the same actions behind a `<form>`, with progressive enhancement, validation, and errors returned from the server.
 - [Mutations and responses](/building-apps/server-functions/mutations-and-responses): writing `api.add` as a `"use server"` function and returning redirects, statuses, and safe errors.
 - [Boundaries](/concepts/boundaries): where `Errored` catches the errors an action does not, and how an errored region recovers.
-- [Data loading and mutations](/routing/solid-router/data): Solid Router's `formAction` and `query` add submissions, caching, and revalidation on top of these primitives.
+- [Data loading and mutations](/routing/solid-router/data): with Solid Router mounted, the same actions call server functions and the router applies their revalidation and redirects; `query` adds caching and `formAction` adds forms.
 - [State management](/guides/state-management): where the cart, the user, and the filter live, and why `createCart()` runs inside a provider.
@@ -223,7 +223,7 @@ Render `<form method="post" action={addToCartAction}>` and the form posts to the
 The router marks the form `aria-busy` while it runs and, once it settles, records a submission whose `error` is the thrown envelope's value, which the [Forms guide](/guides/forms) reads to show messages next to the fields.
 
 Keep the server function a named export and wrap it separately, as above, so a test or an API route can call `addToCart` without the form.
-When the function exists only for the form, write the body inline, `formAction(async (form: FormData) => { "use server"; ... })`; the [Data loading and mutations](/routing/solid-router/data#mutate-with-form-actions) page uses that shape throughout, and the two behave the same.
+When the function exists only for the form, write the body inline, `formAction(async (form: FormData) => { "use server"; ... })`; the two behave the same, and [Data loading and mutations](/routing/solid-router/data#add-a-form-with-formaction) shows both.
 
 :::note[Which action]
 `formAction` is from `@solidjs/router`.
 
@@ -143,7 +143,7 @@ export const stopReply = formAction(async (replyId: string) => {
 `sendMessage` stores the shopper's message and an empty reply with status `generating`, starts the job, and returns.
 The response closes while the job is still writing; the server-function runtime does not dispose work a function started, so the job runs to its end whether or not anyone is watching.
 `threads.append` is the thread half of the store, which keeps the message list and the history the model reads; the `chat` example's `db.send` is one.
-`stopReply` is a Solid Router [form action](/routing/solid-router/data#mutate-with-form-actions), so the Stop button works as a form before JavaScript has loaded.
+`stopReply` is a Solid Router [form action](/routing/solid-router/data#add-a-form-with-formaction), so the Stop button works as a form before JavaScript has loaded.
 `sendMessage` is a plain server function the composer calls from code; the mounted router applies its response, revalidation included, the same way it does for a form.
 
 :::caution[An orphan is a fact, not a hang]
 
@@ -235,5 +235,5 @@ Read these in order if you are new to Solid Router, or jump to the one you need:
 2. [Route definitions](/routing/solid-router/route-definitions): path patterns, parameter filters, route metadata, lazy subtrees, and the file-system manifest.
 3. [Nested routes and layouts](/routing/solid-router/nested-routes): an account section with its own frame that stays mounted while its pages change.
 4. [Navigation and typed paths](/routing/solid-router/navigation): `paths`, `useNavigate`, search parameters with a schema, active and pending links, and leave guards.
-5. [Data loading and mutations](/routing/solid-router/data): `preload`, `query`, `formAction`, optimistic updates, and what revalidates after a mutation.
+5. [Data loading and mutations](/routing/solid-router/data): `preload`, `query`, mutations through server functions and actions, forms with `formAction`, optimistic updates, and what revalidates.
 6. [Server rendering and hydration](/routing/solid-router/server-rendering): what the server adds when the app renders there, and how a mutation returns fresh data in one round trip.