docs: unify casing and replace path-as-text links across recent doc surfaces

Sweep recent (last ~5h) doc edits for two readability/uniformity issues:

- Replace 42 path-as-text links of the form '[/foo/bar](/foo/bar)' with
  descriptive labels derived from each target page's frontmatter title
  (e.g. '[Anthropic]', '[Token use and costs]', '[OpenAI-compatible
  endpoints]'). Affected files include gateway/troubleshooting,
  concepts/oauth, reference/session-management-compaction, and
  reference/transcript-hygiene.
- Sentence-case Title-Cased headings and link text in Related sections
  across codex-harness, model-providers, tools/plugin, sdk-runtime,
  sdk-setup, prompt-caching, ci, cli/config, google-meet, browser,
  rich-output-protocol, subagents, web/control-ui, while preserving
  brand and proper-noun capitalization (OpenAI, Codex, Chrome, Parallels,
  Z.AI, etc.).
This commit is contained in:
Vincent Koc
2026-04-24 22:18:09 -07:00
parent 88ca1859ed
commit c948c63bbd
17 changed files with 80 additions and 80 deletions

View File

@@ -693,11 +693,11 @@ turn for that agent must be a Codex-supported OpenAI model.
## Related
- [Agent Harness Plugins](/plugins/sdk-agent-harness)
- [Agent harness plugins](/plugins/sdk-agent-harness)
- [Agent runtimes](/concepts/agent-runtimes)
- [Model Providers](/concepts/model-providers)
- [Model providers](/concepts/model-providers)
- [OpenAI provider](/providers/openai)
- [Status](/cli/status)
- [Plugin hooks](/plugins/hooks)
- [Configuration Reference](/gateway/configuration-reference)
- [Configuration reference](/gateway/configuration-reference)
- [Testing](/help/testing-live#live-codex-app-server-harness-smoke)

View File

@@ -158,7 +158,7 @@ the microphone/speaker path used by OpenClaw. For clean duplex audio, use
separate virtual devices or a Loopback-style graph; a single BlackHole device is
enough for a first smoke test but can echo.
### Local Gateway + Parallels Chrome
### Local gateway + Parallels Chrome
You do **not** need a full OpenClaw Gateway or model API key inside a macOS VM
just to make the VM own Chrome. Run the Gateway and agent locally, then run a

View File

@@ -462,6 +462,6 @@ Beyond `api.runtime`, the API object also provides:
## Related
- [SDK Overview](/plugins/sdk-overview) -- subpath reference
- [SDK Entry Points](/plugins/sdk-entrypoints) -- `definePluginEntry` options
- [Plugin Internals](/plugins/architecture) -- capability model and registry
- [SDK overview](/plugins/sdk-overview) subpath reference
- [SDK entry points](/plugins/sdk-entrypoints) `definePluginEntry` options
- [Plugin internals](/plugins/architecture) capability model and registry

View File

@@ -566,6 +566,6 @@ startup installs; keep using the explicit plugin installer.
## Related
- [SDK Entry Points](/plugins/sdk-entrypoints) -- `definePluginEntry` and `defineChannelPluginEntry`
- [Plugin Manifest](/plugins/manifest) -- full manifest schema reference
- [Building Plugins](/plugins/building-plugins) -- step-by-step getting started guide
- [SDK entry points](/plugins/sdk-entrypoints) `definePluginEntry` and `defineChannelPluginEntry`
- [Plugin manifest](/plugins/manifest) full manifest schema reference
- [Building plugins](/plugins/building-plugins) step-by-step getting started guide