docs: replace em dashes with plain punctuation

Author: Amir-hkr

AGENTS.md

@@ -7,7 +7,7 @@ If a `placeholder/` directory still exists in this repo, the template has not be
 1. Run `bin/customize.sh <package-name>` with appropriate `--author`, `--email`, `--description`, and `--repository-url` flags (see `### Setup Your Plugin` in [README.md](README.md) for details). This handles the directory rename, `pyproject.toml`/`.releaserc.yaml` edits, and `from placeholder.` import rewrites in one shot.
 2. Verify with `uv venv && source .venv/bin/activate && uv sync --all-extras && tox`.
 3. Remove the template-only files: `rm CONTRIBUTING.md bin/customize.sh`.
-4. **Delete this `## First-time setup` section from both `CLAUDE.md` and `AGENTS.md`** — it only applies to fresh-template repos and would be misleading once the placeholder is gone.
+4. 4. **Delete this `## First-time setup` section from both `CLAUDE.md` and `AGENTS.md`**. It only applies to fresh-template repos and would be misleading once the placeholder is gone. gone.
 
 Must read [README.md](README.md) first.
 

CLAUDE.md

@@ -7,7 +7,7 @@ If a `placeholder/` directory still exists in this repo, the template has not be
 1. Run `bin/customize.sh <package-name>` with appropriate `--author`, `--email`, `--description`, and `--repository-url` flags (see `### Setup Your Plugin` in [README.md](README.md) for details). This handles the directory rename, `pyproject.toml`/`.releaserc.yaml` edits, and `from placeholder.` import rewrites in one shot.
 2. Verify with `uv venv && source .venv/bin/activate && uv sync --all-extras && tox`.
 3. Remove the template-only files: `rm CONTRIBUTING.md bin/customize.sh`.
-4. **Delete this `## First-time setup` section from both `CLAUDE.md` and `AGENTS.md`** — it only applies to fresh-template repos and would be misleading once the placeholder is gone.
+4. **Delete this `## First-time setup` section from both `CLAUDE.md` and `AGENTS.md`**. It only applies to fresh-template repos and would be misleading once the placeholder is gone.
 
 Must read [README.md](README.md) first.
 

README.md

@@ -102,28 +102,28 @@ rm CONTRIBUTING.md bin/customize.sh
 
 `CONTRIBUTING.md` describes how to contribute to the template repo; `bin/customize.sh` is a one-shot scaffold script that has nothing left to do.
 
-Also delete the `## First-time setup` section from `CLAUDE.md` and `AGENTS.md` — those instructions only apply to fresh-template repos.
+Also delete the `## First-time setup` section from `CLAUDE.md` and `AGENTS.md`. Those instructions only apply to fresh-template repos.
 
 The remaining baseline files apply to your plugin out of the box and can be edited to match your conventions:
 
-- `AGENTS.md` and `CLAUDE.md` — toolchain and project practices for the same `tox`/ruff/mypy/bandit pipeline you inherit. Tune the bullets if you change the toolchain.
-- `CODE_OF_CONDUCT.md` — short, plain-English baseline. Update the contact (`conduct@mloda.ai` → your address) if you want enforcement to come to you.
-- `.github/ISSUE_TEMPLATE/issue.yml` — unified issue form. Update the placeholder file paths to point at your renamed package.
+- `AGENTS.md` and `CLAUDE.md`: toolchain and project practices for the same `tox`/ruff/mypy/bandit pipeline you inherit. Tune the bullets if you change the toolchain.
+- `CODE_OF_CONDUCT.md`: short, plain-English baseline. Update the contact (`conduct@mloda.ai` → your address) if you want enforcement to come to you.
+- `.github/ISSUE_TEMPLATE/issue.yml`: unified issue form. Update the placeholder file paths to point at your renamed package.
 
 You may also want to replace this `README.md` with one that describes your plugin.
 
 ### Where to next
 
-- **[mloda-registry/docs/guides/](https://github.com/mloda-ai/mloda-registry/tree/main/docs/guides/)** — full plugin development walkthrough (FeatureGroups, ComputeFrameworks, Extenders, packaging, publishing).
-- **[mloda](https://github.com/mloda-ai/mloda)** — core framework reference.
-- **[Claude Code skills](https://github.com/mloda-ai/mloda-registry/tree/main/.claude/skills/)** — pattern guidance and best practices for AI-assisted plugin development.
-- **[docs/github-workflows.md](docs/github-workflows.md)** — CI/CD setup and required secrets for the included workflows.
-- **[docs/github-repository-settings.md](docs/github-repository-settings.md)** — repository-side settings (secrets, branch protection, required checks, dependabot reviewer) you should configure after scaffolding.
+- **[mloda-registry/docs/guides/](https://github.com/mloda-ai/mloda-registry/tree/main/docs/guides/)**: full plugin development walkthrough (FeatureGroups, ComputeFrameworks, Extenders, packaging, publishing).
+- **[mloda](https://github.com/mloda-ai/mloda)**: core framework reference.
+- **[Claude Code skills](https://github.com/mloda-ai/mloda-registry/tree/main/.claude/skills/)**: pattern guidance and best practices for AI-assisted plugin development.
+- **[docs/github-workflows.md](docs/github-workflows.md)**: CI/CD setup and required secrets for the included workflows.
+- **[docs/github-repository-settings.md](docs/github-repository-settings.md)**: repository-side settings (secrets, branch protection, required checks, dependabot reviewer) you should configure after scaffolding.
 
 ## Contribute to this template
 
 This section is for people improving the scaffold itself (CI workflows, dev tooling, docs, examples). See [CONTRIBUTING.md](CONTRIBUTING.md) for the full contributor guide. Quick pointers:
 
 - [Code of Conduct](CODE_OF_CONDUCT.md)
-- [AGENTS.md](AGENTS.md) — agent guidance, project practices, issue creation
+- [AGENTS.md](AGENTS.md): agent guidance, project practices, issue creation
 - [Issue template](.github/ISSUE_TEMPLATE/issue.yml)

SECURITY.md

@@ -7,7 +7,7 @@
 ## Supported Versions
 
 Security fixes are applied to the latest released version and the `main`
-branch. We do not backport fixes to older releases — please upgrade to the
+branch. We do not backport fixes to older releases. Please upgrade to the
 latest version before reporting.
 
 | Version        | Supported          |
@@ -23,10 +23,10 @@ prepared.
 
 Instead, use one of these private channels:
 
-1. **GitHub Private Vulnerability Reporting** (preferred) — open the **Security**
+1. **GitHub Private Vulnerability Reporting** (preferred): open the **Security**
    tab of this repository and click **Report a vulnerability**. This keeps the
    report, discussion, and coordinated disclosure in one place.
-2. **Email** — for plugins in the mloda organization, write to
+2. **Email**: for plugins in the mloda organization, write to
    **security@mloda.ai**. If you forked this template, use your own address.
 
 Please include as much of the following as you can:

docs/getting-started.md

@@ -49,7 +49,7 @@ Regardless of which option you chose, follow the setup steps in the [README](../
 4. Update `.releaserc.yaml` (change `mloda-plugin-template` to your package name and update `repositoryUrl`)
 5. Update Python imports
 6. Verify with `tox`
-7. Remove `CONTRIBUTING.md` — it describes contributing to the template repo, not your plugin
+7. Remove `CONTRIBUTING.md`. it describes contributing to the template repo, not your plugin
 8. Keep `CODE_OF_CONDUCT.md`, `AGENTS.md`, `CLAUDE.md`, and `.github/ISSUE_TEMPLATE/` as inherited baselines; tune them later (contact email, placeholder paths, toolchain bullets) if you want
 9. Configure repository settings on GitHub: see [github-repository-settings.md](github-repository-settings.md) for the secrets, branch protection, required checks, and dependabot reviewer that the inherited workflows expect