docs: use plain hyphens instead of em dashes in prose

Author: cvetty

README.md

@@ -2,7 +2,7 @@
 
 Rationale layer over [CodeGraph](https://github.com/colbymchenry/codegraph): explains *why* code exists, not just what it does.
 
-For each chunk of code, WhyGraph collects evidence from git history and GitHub — commits, blame, PRs, the issues those PRs closed — then serves it to AI editors over MCP, plus an on-demand rationale card (purpose, why, constraints, tradeoffs, risks) with a persistent cache.
+For each chunk of code, WhyGraph collects evidence from git history and GitHub - commits, blame, PRs, the issues those PRs closed - then serves it to AI editors over MCP, plus an on-demand rationale card (purpose, why, constraints, tradeoffs, risks) with a persistent cache.
 
 > **📖 Full documentation → <https://mtrdesign.github.io/whygraph/>**
 >

docs/deploy/docker.md

@@ -21,10 +21,10 @@ image against the current directory:
 docker run --rm -v "$PWD:/workspace" -w /workspace ghcr.io/mtrdesign/whygraph whygraph "$@"
 ```
 
-The container is **ephemeral per command** — no compose, no `docker exec`, nothing to start or stop.
+The container is **ephemeral per command** - no compose, no `docker exec`, nothing to start or stop.
 Each invocation is a fresh process against the repo you're standing in.
 
-- **Everything's in the image** — Python and WhyGraph, `git`, the GitHub CLI, and Node with the
+- **Everything's in the image** - Python and WhyGraph, `git`, the GitHub CLI, and Node with the
   CodeGraph CLI. CodeGraph indexes from the in-image binary, so there's no docker-in-docker.
 - **Per-project config just works.** Each command reads the current repo's own `whygraph.toml`,
   `.whygraph/`, and `.codegraph/`.
@@ -52,12 +52,12 @@ whygraph init --agent claude     # writes .mcp.json (also: --agent cursor / vsco
 
 The generated config launches `whygraph-mcp` by bare command name. Your editor resolves it to the
 shim, which starts a per-session container speaking MCP over stdio. It reads the repo's `.whygraph/`
-and `.codegraph/` over the same `/workspace` mount the scan writes to — so the editor and the scan
+and `.codegraph/` over the same `/workspace` mount the scan writes to - so the editor and the scan
 share one source of truth on disk.
 
 ## Build the image yourself
 
-Building locally instead of pulling — say, while developing:
+Building locally instead of pulling - say, while developing:
 
 ```bash
 docker build -f docker/whygraph/Dockerfile -t whygraph:latest .

docs/deploy/index.md

@@ -9,7 +9,7 @@ they differ in who's driving.
 
     ---
 
-    Install the Docker shim, then `init` and `scan` your repos and wire your editor — no Python or
+    Install the Docker shim, then `init` and `scan` your repos and wire your editor - no Python or
     Node on the host. This is the default install.
 
     [:octicons-arrow-right-24: Run with Docker](docker.md)
@@ -18,13 +18,13 @@ they differ in who's driving.
 
     ---
 
-    A containerized `whygraph-mcp` endpoint that real applications — not just editors — connect to
+    A containerized `whygraph-mcp` endpoint that real applications - not just editors - connect to
     for git-based analysis of a target repo.
 
     [:octicons-arrow-right-24: WhyGraph as a service](service.md)
 
 </div>
 
 Most people start with the local tool. Reach for the service model when you're building an
-application that needs the *why* behind code — a review bot, an onboarding assistant, an internal
+application that needs the *why* behind code - a review bot, an onboarding assistant, an internal
 portal.

docs/deploy/service.md

@@ -3,7 +3,7 @@
 Editors aren't the only thing that can talk to WhyGraph. The MCP server is a plain stdio program, so
 any application that speaks MCP can connect to it for git-based analysis of a target repo. Think of a
 review bot, an onboarding assistant, or an internal dev portal that needs the *why* behind a chunk of
-code — not just the code.
+code - not just the code.
 
 This page covers that model: a containerized `whygraph-mcp` endpoint a third-party app drives over
 MCP, reading the same on-disk data your scan produces.
@@ -27,17 +27,17 @@ flowchart LR
 
 The consuming app gets the full read surface over MCP:
 
-- **Evidence** — `whygraph_evidence_for` and `whygraph_area_history` for the commits, PRs, and issues
+- **Evidence** - `whygraph_evidence_for` and `whygraph_area_history` for the commits, PRs, and issues
   behind a path or symbol.
-- **Rationale** — `whygraph_rationale_brief` for a structured why-this-exists card.
-- **Resources** — `whygraph://commit/{sha}`, `whygraph://pr/{number}`, `whygraph://issue/{number}`,
+- **Rationale** - `whygraph_rationale_brief` for a structured why-this-exists card.
+- **Resources** - `whygraph://commit/{sha}`, `whygraph://pr/{number}`, `whygraph://issue/{number}`,
   and `whygraph://repo/overview`.
 
 See the [MCP surface reference](../reference/mcp.md) for exact signatures.
 
 ## Scan first
 
-The server reads cached data — it doesn't crawl on demand. So the target repo must be scanned before
+The server reads cached data - it doesn't crawl on demand. So the target repo must be scanned before
 an app connects, or the tools have nothing to return.
 
 ```bash
@@ -76,14 +76,14 @@ What the app needs depends on what it asks for:
   `[llm.*]` table.
 
 !!! info "Tokens never live in the image"
-    Pass credentials at run time via env or the gitignored `whygraph.toml` — never bake them into a
+    Pass credentials at run time via env or the gitignored `whygraph.toml` - never bake them into a
     built image. This matches WhyGraph's own invariant for the Docker shim.
 
 ## Current scope
 
 Today the server speaks MCP over **stdio, one session per process**. There's no long-running HTTP
-endpoint yet — each connection is its own `docker run`. A persistent server mode with an HTTP MCP
+endpoint yet - each connection is its own `docker run`. A persistent server mode with an HTTP MCP
 transport is on the [roadmap](../roadmap.md), not built.
 
-For now, model your integration as "spawn a session, run the tools you need, let it exit" — the same
+For now, model your integration as "spawn a session, run the tools you need, let it exit" - the same
 lifecycle an editor uses, driven by your app instead.

docs/getting-started/index.md

@@ -1,11 +1,11 @@
 # Getting Started
 
 WhyGraph is a rationale layer over [CodeGraph](https://github.com/colbymchenry/codegraph). CodeGraph
-maps what your code *is* — symbols, callers, callees. WhyGraph adds *why* it exists, drawn from the
+maps what your code *is* - symbols, callers, callees. WhyGraph adds *why* it exists, drawn from the
 history around it.
 
-For each chunk of code, it collects evidence from git and GitHub — commits, blame, pull requests, the
-issues those PRs closed — and links it together. Then it exposes that evidence to your AI editor over
+For each chunk of code, it collects evidence from git and GitHub - commits, blame, pull requests, the
+issues those PRs closed - and links it together. Then it exposes that evidence to your AI editor over
 MCP, plus an on-demand rationale card (purpose, why, constraints, tradeoffs, risks) that it caches.
 
 You install WhyGraph once, then wire it into each repo you want it to analyze. It speaks MCP, so any
@@ -25,17 +25,17 @@ its own history on top.
 
 ## Prerequisites
 
-You don't need all of these — most are optional, and the phases that depend on them skip cleanly when
+You don't need all of these - most are optional, and the phases that depend on them skip cleanly when
 they're missing.
 
-- **[uv](https://docs.astral.sh/uv/)** *or* **Docker** — uv for a native install, or Docker alone for
+- **[uv](https://docs.astral.sh/uv/)** *or* **Docker** - uv for a native install, or Docker alone for
   the [container install](installation.md). With Docker, you need nothing else on your host.
-- **git** — your repo history is the primary evidence source.
-- **Docker** *(native installs only)* — when no `codegraph` binary is on `PATH`, `whygraph scan` runs
+- **git** - your repo history is the primary evidence source.
+- **Docker** *(native installs only)* - when no `codegraph` binary is on `PATH`, `whygraph scan` runs
   CodeGraph inside the WhyGraph image to index the repo.
-- **[`gh` CLI](https://cli.github.com/)**, authenticated — only for GitHub repos, and only if you
+- **[`gh` CLI](https://cli.github.com/)**, authenticated - only for GitHub repos, and only if you
   enable the remote crawl. Without it, the GitHub phase is skipped.
-- **`claude` CLI** *or* an LLM API key — for per-commit descriptions and rationale cards. Both phases
+- **`claude` CLI** *or* an LLM API key - for per-commit descriptions and rationale cards. Both phases
   skip cleanly if neither is available.
 
 Ready to install?
@@ -46,15 +46,15 @@ Ready to install?
 
     ---
 
-    Docker, PyPI, GitHub, or a local checkout — pick the path that fits.
+    Docker, PyPI, GitHub, or a local checkout - pick the path that fits.
 
     [:octicons-arrow-right-24: Install WhyGraph](installation.md)
 
 -   :material-rocket-launch:{ .lg .middle } __Quickstart__
 
     ---
 
-    Init, scan, wire an editor — the happy path in four commands.
+    Init, scan, wire an editor - the happy path in four commands.
 
     [:octicons-arrow-right-24: Quickstart](quickstart.md)
 

docs/getting-started/installation.md

@@ -1,14 +1,14 @@
 # Installation
 
-WhyGraph follows a one-global-install, use-anywhere model — like `npx`, but for Python. You install
+WhyGraph follows a one-global-install, use-anywhere model - like `npx`, but for Python. You install
 the package once; that puts `whygraph` and `whygraph-mcp` on your `PATH`. Then
 `whygraph init --agent <name>` wires each project so its editor can launch the MCP server.
 
 Pick the path that fits where you are.
 
 === "Docker (recommended)"
 
-    The host needs **only Docker** — no Python, Node, `gh`, or CodeGraph. A tiny shim runs everything
+    The host needs **only Docker** - no Python, Node, `gh`, or CodeGraph. A tiny shim runs everything
     inside one published image.
 
     ```bash
@@ -30,7 +30,7 @@ Pick the path that fits where you are.
 
 === "GitHub"
 
-    Install straight from the repo — latest `main`, a feature branch, or a tag:
+    Install straight from the repo - latest `main`, a feature branch, or a tag:
 
     ```bash
     # Latest from main:

docs/getting-started/quickstart.md

@@ -12,7 +12,7 @@ whygraph init
 ```
 
 This creates `.whygraph/whygraph.db`, writes a commented `whygraph.example.toml`, and adds the right
-`.gitignore` entries. It's idempotent — run it again any time. It does *not* index CodeGraph yet;
+`.gitignore` entries. It's idempotent - run it again any time. It does *not* index CodeGraph yet;
 that's the next step.
 
 ## 2. Scan
@@ -29,7 +29,7 @@ evidence WhyGraph serves.
     A fresh scan stays git-only and needs no token, because `[scan].provider` defaults to `"off"`. To
     pull PRs and issues, set `provider = "github"` (or `"auto"`) in `whygraph.toml`.
 
-For a fast, offline pass — no remote calls, no LLM — skip both phases:
+For a fast, offline pass - no remote calls, no LLM - skip both phases:
 
 ```bash
 whygraph scan --no-remote --no-llm-descriptions
@@ -47,7 +47,7 @@ whygraph init --agent claude
 ```
 
 That writes `.mcp.json` at the repo root and copies the bundled assets into `.claude/`. Other agents
-work the same way — `--agent cursor`, `--agent vscode`, `--agent codex`. See
+work the same way - `--agent cursor`, `--agent vscode`, `--agent codex`. See
 [Wiring your editor](../guide/editors.md) for each one's config path.
 
 ## 4. Sanity-check the server
@@ -56,7 +56,7 @@ work the same way — `--agent cursor`, `--agent vscode`, `--agent codex`. See
 whygraph-mcp   # Ctrl-C to exit
 ```
 
-If it launches without error, your editor can launch it too. That's it — ask your assistant why a
+If it launches without error, your editor can launch it too. That's it - ask your assistant why a
 function exists, and WhyGraph answers from history.
 
 ## Where to next

docs/guide/concepts.md

@@ -12,11 +12,11 @@ the pull requests that merged it, and the issues those PRs closed. WhyGraph coll
 
 You reach evidence two ways, because there are two questions to ask:
 
-- **`whygraph_evidence_for`** — "which commits authored *these specific lines*?" Line-blame-driven and
+- **`whygraph_evidence_for`** - "which commits authored *these specific lines*?" Line-blame-driven and
   anchored to HEAD. Best when you have a precise range or a symbol.
-- **`whygraph_area_history`** — "which commits ever touched *this file*, or anything that became this
+- **`whygraph_area_history`** - "which commits ever touched *this file*, or anything that became this
   file?" It walks the rename chain, so it reaches code that's since been deleted, moved, or fully
-  rewritten — commits that blame physically can't surface.
+  rewritten - commits that blame physically can't surface.
 
 The two reinforce each other. Evidence keeps line-level precision; area history reaches further back.
 
@@ -25,22 +25,22 @@ The two reinforce each other. Evidence keeps line-level precision; area history
 A rationale card is WhyGraph's answer to "why does this exist?" It takes the evidence bundle, hands it
 to the configured LLM, and gets back a structured card with exactly five fields:
 
-- **purpose** — what this code is for.
-- **why** — why it was written this way.
-- **constraints** — what it must preserve.
-- **tradeoffs** — what was given up, and for what.
-- **risks** — what could break if you change it.
+- **purpose** - what this code is for.
+- **why** - why it was written this way.
+- **constraints** - what it must preserve.
+- **tradeoffs** - what was given up, and for what.
+- **risks** - what could break if you change it.
 
-The card comes back with provenance too — `model`, `provider`, `cached_at` — and an `evidence_count`
+The card comes back with provenance too - `model`, `provider`, `cached_at` - and an `evidence_count`
 summarizing how many commits, PRs, and issues fed it.
 
 !!! note "Five fields, nothing more"
-    A card carries those five narrative fields and nothing else — no extra score or rating. The
+    A card carries those five narrative fields and nothing else - no extra score or rating. The
     rationale is the evidence-grounded explanation, full stop.
 
 ### Caching
 
-Cards are **persistently cached**, keyed by content — the target, the evidence bundle, the provider,
+Cards are **persistently cached**, keyed by content - the target, the evidence bundle, the provider,
 and the model. Generate a card once and the next identical lookup is a sub-second database read. Change
 the underlying code (so the evidence shifts) and the next call regenerates. You pay the LLM cost only
 when something actually changed.
@@ -51,9 +51,9 @@ WhyGraph sits on top of CodeGraph and stays out of its lane:
 
 | Layer | Owns |
 |---|---|
-| **CodeGraph** | "what's connected to what" — callers, callees, `find_symbols`, type hierarchy |
-| **WhyGraph** | "why it exists and when it changed" — evidence, rationale, area history |
+| **CodeGraph** | "what's connected to what" - callers, callees, `find_symbols`, type hierarchy |
+| **WhyGraph** | "why it exists and when it changed" - evidence, rationale, area history |
 
 When you target a symbol by `qualified_name`, WhyGraph asks CodeGraph to resolve it to a file and line
-range, then layers its own history on top. It exposes no graph-traversal tools of its own — for that,
+range, then layers its own history on top. It exposes no graph-traversal tools of its own - for that,
 call CodeGraph directly.

docs/guide/editors.md

@@ -11,7 +11,7 @@ whygraph init --agent claude
 
 ## Supported agents
 
-Four agents are supported. **All of them are project-scoped** — the config file is written or merged
+Four agents are supported. **All of them are project-scoped** - the config file is written or merged
 inside the repo, so you can commit it and every teammate's editor picks it up.
 
 | `--agent` | Editor | Config file |
@@ -24,7 +24,7 @@ inside the repo, so you can commit it and every teammate's editor picks it up.
 Run `whygraph init --list-agents` to print these paths for your own checkout.
 
 The generated config launches `whygraph-mcp` by bare command name, so the same checked-in file works
-for everyone who has WhyGraph installed — no absolute paths to scrub.
+for everyone who has WhyGraph installed - no absolute paths to scrub.
 
 ## Claude Code assets
 

docs/guide/index.md

@@ -1,6 +1,6 @@
 # User Guide
 
-You've scanned a repo and wired an editor. This guide explains how the pieces fit together — and how
+You've scanned a repo and wired an editor. This guide explains how the pieces fit together - and how
 to get the most out of each.
 
 The flow is simple. You **scan** a repo to build the evidence database and refresh the CodeGraph