diff --git a/skills/linear-common/COMMON.md b/skills/linear-common/COMMON.md
index 3b74a05..c4ba47f 100644
--- a/skills/linear-common/COMMON.md
+++ b/skills/linear-common/COMMON.md
@@ -64,7 +64,7 @@ GitHub-issues example (`tracker: github`):
 | Field | Required | Description |
 |---|---|---|
 | `tracker` | no | Where issues live: `linear` (default), `gitea`, or `github`. See **Tracker backend** below. |
-| `linearMcp` | no | MCP server name when `tracker: linear`. Default `linear-server`. Use `linear-acme` for the example workspace. |
+| `linearMcp` | no | MCP server name when `tracker: linear`. Default `linear-server`. Set a per-workspace name (e.g. `linear-acme`) when a project has its own server. |
 | `org` | linear only | Linear organization slug |
 | `team` | linear only | Linear team name (for listing/creating issues) |
 | `project` | no | Linear project name (narrows issue search). Ignored when `tracker: gitea`. |
@@ -84,7 +84,7 @@ GitHub-issues example (`tracker: github`):
 
 `tracker` selects where issues live. Every instruction below that refers to "the issue" applies to the configured backend; where the two differ (selection, status changes, branch naming) the gitea-specific steps are called out explicitly.
 
-- **`linear`** (default): issues live in Linear, accessed via the MCP server named by `linearMcp` (default `linear-server`; an example workspace uses `linear-acme`). Requires `org` + `team`. Tool calls use the `mcp__<linearMcp>__*` prefix.
+- **`linear`** (default): issues live in Linear, accessed via the MCP server named by `linearMcp` (default `linear-server`; a workspace with its own server sets its own name). Requires `org` + `team`. Tool calls use the `mcp__<linearMcp>__*` prefix.
 - **`gitea`**: issues live in the repo's own Gitea issue tracker — **no Linear MCP involved**. The repo (`owner/repo`) is derived from `git remote get-url origin`; the API uses `remoteBaseUrl` + `$GITEA_TOKEN` (load via `source ~/.env.claude` if needed), exactly like the `/work` Gitea PR variant. `org`/`team`/`project` are ignored.
 - **`github`**: issues live in the repo's own GitHub issue tracker — **no Linear MCP involved**. The repo (`owner/repo`) is derived from `git remote get-url origin`; all issue and PR operations use the `gh` CLI (must be authenticated — `gh auth status`). `org`/`team`/`project` are ignored. GitHub has no workflow states, so WIP is signalled by assigning the issue to yourself (like gitea); the PR's `Closes #N` closes the issue on merge.