Reword new doc passages to avoid dash asides

Author: maxisbey

docs/advanced/multi-round-trip.md

@@ -19,7 +19,7 @@ That's the whole protocol. Every leg is an ordinary request from the client to t
 
 ## The server side
 
-On `@mcp.tool()` you rarely build this by hand: declare a dependency that asks the user and the SDK returns the `InputRequiredResult` for you - that form is the **[Dependencies](../tutorial/dependencies.md)** tutorial. The two forms don't mix: a call has one `input_responses`/`request_state` channel, so a tool that uses `Resolve(...)` parameters cannot also return `InputRequiredResult` from its body - a declared `InputRequiredResult` return is rejected at registration (`InvalidSignature`), and an undeclared one fails the call at runtime. The manual form is the **low-level** `Server`, whose `on_call_tool` handler is allowed to return either result type:
+On `@mcp.tool()` you rarely build this by hand: declare a dependency that asks the user and the SDK returns the `InputRequiredResult` for you - that form is the **[Dependencies](../tutorial/dependencies.md)** tutorial. The two forms don't mix: a call has one `input_responses`/`request_state` channel, so a tool that uses `Resolve(...)` parameters cannot also return `InputRequiredResult` from its body. A declared `InputRequiredResult` return is rejected at registration (`InvalidSignature`), and an undeclared one fails the call at runtime. The manual form is the **low-level** `Server`, whose `on_call_tool` handler is allowed to return either result type:
 
 ```python title="server.py" hl_lines="44-47"
 --8<-- "docs_src/mrtr/tutorial001.py"

docs/tutorial/dependencies.md

@@ -126,10 +126,10 @@ That's the right default for a precondition: no answer, no order. When declining
     multi-round-trip form any resolver may run again whenever the call resumes after a question,
     so code before a `return Elicit(...)` runs on each of those rounds; the recorded answer then
     satisfies the repeated question without prompting the user again. A recorded answer is only
-    ever consulted when the resolver asks - a resolver that answers *without* asking, like
+    ever consulted when the resolver asks; a resolver that answers *without* asking, like
     `check_stock`, always supplies its own computed value. Because each answer is matched back to
     its question, an eliciting resolver must derive its question deterministically from the
-    tool's arguments and earlier answers - a per-call generated value (a `default_factory` id, a
+    tool's arguments and earlier answers. A per-call generated value (a `default_factory` id, a
     timestamp) is re-derived on each round and must not appear in a question the answer is meant
     to bind to.
 

examples/stories/refund_desk/README.md

@@ -62,9 +62,9 @@ uv run python -m stories.refund_desk.client --http
   within a round each resolver runs at most once, keyed by function identity.
   Across 2026 rounds only *elicited* outcomes persist (in `requestState`); any
   resolver's body may run again on each round the call passes through. A
-  recorded answer is consulted only when the resolver asks its question again —
-  it satisfies the question without re-prompting the user, and never stands in
-  for a value the resolver computes itself.
+  recorded answer is consulted only when the resolver asks its question again:
+  it satisfies the question without re-prompting the user, and it never stands
+  in for a value the resolver computes itself.
   An answer is matched back to its question when the call resumes, so an
   eliciting resolver must derive its question deterministically from the
   tool's arguments and earlier answers; a per-call generated value (a