docs: keep inline code spans on one line

The changeset's `tapErrCases` bullet had an unindented continuation line,
which markdown renders as a new paragraph, breaking the list.

Cause: the inline code span `[the branch's cause, the observed error]`
wrapped across lines, and oxfmt strips the continuation indent there —
leading whitespace is significant inside a code span, so reflowing it
would alter the span's text. The indent was correct as written and the
formatter removed it.

Reworded so the span no longer wraps; re-running oxfmt now leaves the
indentation alone.

Swept the rest of the docs for the same shape and found two more
(upgrade-to-v8.md, why-temporal-contract.md). Neither sat in a list, so
both rendered fine, but they carried the same latent hazard — reworded
too. A backtick-parity scan over all authored markdown is now clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: 2 people

.changeset/bump-unthrown-beta-7.md

@@ -13,8 +13,8 @@ Two changes come with it, neither requiring code changes here:
   the branch returns. Available on all five `*ErrCases` combinators, `match`'s
   `errCases` handler, and standalone `match(value)`.
 - **`tapErrCases` no longer silently drops a `defect(…)` branch.** Such a branch
-  now produces a `Defect` carrying an `AggregateError` of `[the branch's cause,
-the observed error]`, matching what a `throw` in the same position already
-  did. Only a breaking change for code that relied on the value being discarded
-  — this package's single `tapErrCases` call site logs and does not use the
-  `defect` marker.
+  now produces a `Defect` whose cause is an `AggregateError` of the branch's
+  cause and the observed error, matching what a `throw` in the same position
+  already did. Only a breaking change for code that relied on the value being
+  discarded — this package's single `tapErrCases` call site logs and does not
+  use the `defect` marker.

docs/explanation/why-temporal-contract.md

@@ -112,8 +112,8 @@ or charges wrongly, and leaves a failed execution to explain.
 ## Failures as values
 
 Temporal's failure model is strings: an `ApplicationFailure` with a `type` that
-retry policies match on. Effective for retries, weak for branching. `if
-(error.type === "CARD_DECLINED")` is a stringly-typed conditional with a typo
+retry policies match on. Effective for retries, weak for branching. A check like
+`error.type === "CARD_DECLINED"` is a stringly-typed conditional with a typo
 waiting to happen, and no payload beyond a message.
 
 A contract can declare its failures:

docs/how-to/upgrade-to-v8.md

@@ -10,8 +10,9 @@ Version 8 has two breaking changes:
 Both are mechanical. Budget an afternoon for a medium codebase.
 
 ::: warning 8.0 is currently a prerelease
-The 8.0 line is published under the `beta` tag. `npm install
-@temporal-contract/contract` still resolves 7.x. Install explicitly:
+The 8.0 line is published under the `beta` tag, so a plain
+`npm install @temporal-contract/contract` still resolves 7.x. Install
+explicitly:
 
 ```bash
 pnpm add @temporal-contract/contract@beta @temporal-contract/worker@beta \