docs: address review feedback (nine small fixes across ten files)

A review pass left 13 comments; nine needed action and each fix is a
word or a line.

- testing.md over-claimed that every example runs "through exactly this
  client". Every example file IS exercised by the suite, but two of the
  42 docs test modules never construct a Client (the OAuth examples
  cannot be driven that way), so it now says "almost all of them".
- oauth-clients.md's "Every other example in these docs you can check
  with an in-memory Client(server)" had the same shape (the identity
  assertion example cannot be either); now "Most examples".
- handling-errors.md's new hand-off promised Troubleshooting covers
  "every error the SDK produces". The Troubleshooting page scopes
  itself the honest way round, so the hand-off now matches it.
- dependencies.md's closing hand-off read "State your server builds
  once at startup ... is the Lifespan", which garden-paths as an
  imperative; it gained its determiner and its head noun.
- asgi.md's tip said "the next section is what host= actually
  controls", but this PR moved that explanation to Deploy & scale; the
  tip now points there.
- media.md gains a relative pronoun: "the TextContent that a plain str
  result becomes".
- README's two get-started links still pointed at the old /v2/tutorial/
  URL, which this PR turns into a redirect stub; both now point at
  /v2/get-started/.
- docs/hooks/llms_txt.py's docstring example path named the removed
  tutorial/ directory; it now names the moved page's real path.
- RELEASE.md's list of version-pin locations gains the new
  docs/get-started/real-host.md (which pins the version seven times),
  and examples/README.md no longer claims the simple-auth pair is
  linked from docs/advanced/ (this PR moved every page that links it).

Two other comments were already addressed by earlier commits on this
branch (the chapter-to-page sweep and the branch-coverage fix), and two
were declined with evidence. The claimed "sentence fragment" in
media.md is a complete sentence (a contact relative clause) read one
wrapped line at a time. And gating the deploy example's refund on
request_state instead of input_responses would not add a
human-confirmation guarantee: input_responses is a wire parameter only
the MCP client can send, and that same client authors the elicitation
answer on the honest second round; the SDK's own Client documents
seeding input_responses on the first call.

Author: maxisbey

README.md

@@ -24,7 +24,7 @@
 
 **The documentation lives at <https://py.sdk.modelcontextprotocol.io/v2/>.**
 
-It has a [Get started guide](https://py.sdk.modelcontextprotocol.io/v2/tutorial/), the [API reference](https://py.sdk.modelcontextprotocol.io/v2/api/mcp/), and the [migration guide](https://py.sdk.modelcontextprotocol.io/v2/migration/).
+It has a [Get started guide](https://py.sdk.modelcontextprotocol.io/v2/get-started/), the [API reference](https://py.sdk.modelcontextprotocol.io/v2/api/mcp/), and the [migration guide](https://py.sdk.modelcontextprotocol.io/v2/migration/).
 
 ## What is MCP?
 
@@ -82,7 +82,7 @@ Call `add` with `a=1`, `b=2` and you get `3` back.
 
 Notice what you did **not** write: no JSON Schema (`a: int, b: int` _is_ the schema), no request parsing, no validation code, no protocol handling. Two type-hinted Python functions and a docstring.
 
-[Get started](https://py.sdk.modelcontextprotocol.io/v2/tutorial/) takes it from here.
+[Get started](https://py.sdk.modelcontextprotocol.io/v2/get-started/) takes it from here.
 
 ## A client in 10 lines
 

RELEASE.md

@@ -35,7 +35,7 @@ the publish job — `skip-existing` makes it skip whatever already landed. The
 
 1. Update the pre-release version examples in `README.md` and the docs
    (grep the outgoing version — the pins live in the README Installation
-   section, `docs/index.md`, and `docs/get-started/installation.md`) so the tagged
+   section, `docs/index.md`, `docs/get-started/installation.md`, and `docs/get-started/real-host.md`) so the tagged
    commit — and therefore the README PyPI publishes — names the version
    being released. When entering a new phase (alpha → beta → rc), update
    the banner wording too.

docs/client/oauth-clients.md

@@ -87,7 +87,7 @@ You wrote none of it. Three keyword arguments remain (`timeout`, `client_metadat
 
 ### Try it
 
-Every other example in these docs you can check with an in-memory `Client(server)`. Not this: the whole point of the flow is an HTTP `401`, and there is no HTTP between an in-memory client and its server.
+Most examples in these docs you can check with an in-memory `Client(server)`. Not this: the whole point of the flow is an HTTP `401`, and there is no HTTP between an in-memory client and its server.
 
 The repository ships the live version. `examples/servers/simple-auth/` runs a standalone authorization server and a protected MCP server; `examples/clients/simple-auth-client/` is this page's client grown into a small CLI. Its README has the two commands: start the servers, run the client against them, and you watch the four steps go by.
 

docs/get-started/testing.md

@@ -99,8 +99,8 @@ Leave it on in tests. It has no meaning in production code.
     failure inside the server task instead of in your test.
 
 That one line is also why these docs can promise you that their examples work: every
-example file is exercised by the SDK's own test suite through exactly this client. You're using the
-same tool the SDK uses on itself.
+example file is exercised by the SDK's own test suite, almost all of them through exactly this
+client. You're using the same tool the SDK uses on itself.
 
 You have a working, tested server. Putting it inside a real application (Claude Desktop, an
 IDE) is **[Connect to a real host](real-host.md)**; every other way to serve it is

docs/handlers/dependencies.md

@@ -142,4 +142,4 @@ That's the right default for a precondition: no answer, no order. When declining
 * Bad graphs fail at registration with `InvalidSignature`, not mid-call.
 * Return `Elicit(message, Model)` to ask the user, only when you have to. Unwrapped annotations abort on decline; `ElicitationResult[T]` lets the tool branch.
 
-State your server builds once at startup, and how a handler reaches it, is the **[Lifespan](lifespan.md)**.
+The state your server builds once at startup, and how a handler reaches it, is the **[Lifespan](lifespan.md)** page.

docs/hooks/llms_txt.py

@@ -5,7 +5,7 @@
 - `llms.txt`: a markdown index of the documentation, one link per page,
   grouped by nav section.
 - a `.md` rendition of every prose page next to its HTML (e.g.
-  `tutorial/tools/index.md`), which is what the llms.txt links point at.
+  `servers/tools/index.md`), which is what the llms.txt links point at.
 - `llms-full.txt`: every prose page concatenated for single-fetch consumption.
 
 Page markdown is the source markdown with `--8<--` snippet includes resolved

docs/run/asgi.md

@@ -30,8 +30,8 @@ Run the app on its own (`uvicorn server:app`) and you never think about either.
 !!! tip
     `streamable_http_app()` takes the same keyword arguments as `mcp.run("streamable-http", ...)`,
     minus `port`: the port belongs to whatever serves the app. `host` is still accepted but binds
-    nothing here; the next section is what it actually controls. **[Running your server](index.md)** covers the
-    options themselves.
+    nothing here; **[Deploy & scale](deploy.md)** explains what it actually controls.
+    **[Running your server](index.md)** covers the options themselves.
 
 `mcp.sse_app()` does the same for the superseded SSE transport.
 

docs/servers/handling-errors.md

@@ -131,4 +131,4 @@ It means a whole class of `raise` statements you don't write: don't re-validate
 
 Errors handled. That is everything a server *exposes*. What every handler can read, and do back to the client while it runs, is the next section: **[Inside your handler](../handlers/index.md)**.
 
-The exact text of every error the SDK produces, what it means, and the one-move fix for each is **[Troubleshooting](../troubleshooting.md)**.
+The exact text of the SDK errors you are most likely to meet, what each means, and the one-move fix for each is **[Troubleshooting](../troubleshooting.md)**.

docs/servers/media.md

@@ -30,7 +30,7 @@ Two things to notice:
 
 !!! info
     `ImageContent` and `AudioContent` live in `mcp_types`, right next to the `TextContent`
-    a plain `str` result becomes (**[Tools](tools.md)**). A tool result is a list of content blocks; `Image` and `Audio` are
+    that a plain `str` result becomes (**[Tools](tools.md)**). A tool result is a list of content blocks; `Image` and `Audio` are
     the shortest way to produce the two binary kinds.
 
 ### Try it

examples/README.md

@@ -16,7 +16,7 @@
 - [`clients/`](clients/) and the remaining [`servers/`](servers/) directories
   (`simple-*`, `sse-polling-demo`, `structured-output-lowlevel`) — standalone
   v1-era projects retained pending consolidation into `stories/` (the
-  `simple-auth` pair is still linked from `docs/advanced/`).
+  `simple-auth` pair is still linked from `docs/run/authorization.md` and `docs/client/oauth-clients.md`).
 
 For real-world servers see the
 [servers repository](https://github.com/modelcontextprotocol/servers).