diff --git a/.github/ISSUE_TEMPLATE/clarification.yml b/.github/ISSUE_TEMPLATE/clarification.yml
index 905059e..d07e567 100644
--- a/.github/ISSUE_TEMPLATE/clarification.yml
+++ b/.github/ISSUE_TEMPLATE/clarification.yml
@@ -26,8 +26,7 @@ body:
       label: Specification Section
       description: Which section(s) are you asking about?
       placeholder: |
-        E.g., Section 9.3, "Arrays of Objects — Tabular Form"
-        Or: SPEC.md:383-408
+        E.g., Section 9.3, "Arrays of Objects – Tabular Form"
     validations:
       required: true
 
diff --git a/README.md b/README.md
index ca3e1d1..21f28a2 100644
--- a/README.md
+++ b/README.md
@@ -75,6 +75,7 @@ The TOON specification uses MAJOR.MINOR versioning. See [VERSIONING.md](./VERSIO
 - **Test Fixtures:** [tests/fixtures/](./tests/fixtures/) – Reference test fixtures
 - **Changelog:** [CHANGELOG.md](./CHANGELOG.md) – Version history and changes
 - **Reference Implementation:** [github.com/toon-format/toon](https://github.com/toon-format/toon) – TypeScript/JavaScript implementation
+- **Implementations:** [toonformat.dev/ecosystem/implementations](https://toonformat.dev/ecosystem/implementations) – Official and community ports
 - **Benchmarks:** [Reference repo benchmarks/](https://github.com/toon-format/toon/tree/main/benchmarks) – Token efficiency measurements and accuracy retrieval tests
 
 ## License
diff --git a/VERSIONING.md b/VERSIONING.md
index c49f264..a379cf5 100644
--- a/VERSIONING.md
+++ b/VERSIONING.md
@@ -97,7 +97,7 @@ If we need to make a breaking change (MAJOR version bump):
 
 When in doubt, we err on the side of caution and treat potentially breaking changes as MAJOR version bumps.
 
-Implementations should document the supported spec version (e.g. `"toon-spec": "3.2"`) and may support multiple versions concurrently: default to the latest, let users target a specific version, and document version-specific behavior. A new MINOR version keeps existing conformant implementations conformant. A new MAJOR version may require updates; previous-version implementations remain valid, and its CHANGELOG.md entry carries the migration guidance. A MINOR version that renames or retires a public concept handle (for example an option name) carries a migration note in CHANGELOG.md naming the old and new spelling.
+Implementations should document the supported spec version (e.g., `toon-spec: 4.1`, as in SPEC.md §13) and may support multiple versions concurrently: default to the latest, let users target a specific version, and document version-specific behavior. A new MINOR version keeps existing conformant implementations conformant. A new MAJOR version may require updates; previous-version implementations remain valid, and its CHANGELOG.md entry carries the migration guidance. A MINOR version that renames or retires a public concept handle (for example an option name) carries a migration note in CHANGELOG.md naming the old and new spelling.
 
 ## Version History