diff --git a/docs-developers/meta/data-model.md b/docs-developers/meta/data-model.md
index 73f121b..20844ad 100644
--- a/docs-developers/meta/data-model.md
+++ b/docs-developers/meta/data-model.md
@@ -113,7 +113,7 @@ Two **per-work sidecars** carry the community-authored, spoiler-tagged content:
 the `characters` and `recaps` members of a work's entry in the separate
 `data/works-community/` family, keyed by the **work's** slug. They are
 structurally separated from the core: their `license` field accepts only
-`CC-BY-SA-3.0` (`$defs/license_content`), and the family boundary makes the
+`CC-BY-SA-4.0` (`$defs/license_content`), and the family boundary makes the
 licensing split visible in the directory tree. Authoring them is documented in
 the repo's `AUTHORING.md` (see [contributing data](contributing-data.md)).
 
diff --git a/docs-developers/meta/overview.md b/docs-developers/meta/overview.md
index 346d842..2127210 100644
--- a/docs-developers/meta/overview.md
+++ b/docs-developers/meta/overview.md
@@ -35,13 +35,13 @@ data is split across two licence layers (below).
 
 Data lives in two layers, and the boundary is **enforced structurally by the JSON
 Schema**, not by convention (see `LICENSING.md` in the repo): the `license` field
-of a core record accepts only `CC0-1.0`, and a sidecar's only `CC-BY-SA-3.0`
+of a core record accepts only `CC0-1.0`, and a sidecar's only `CC-BY-SA-4.0`
 (`common.schema.json` `$defs/license` vs `$defs/license_content`).
 
 | Layer | Entities | Licence |
 |---|---|---|
 | **Factual core** | works, recordings, people, series | **CC0-1.0** public-domain dedication |
-| **Expressive layer** | per-work characters + recaps sidecars | **CC BY-SA 3.0** |
+| **Expressive layer** | per-work characters + recaps sidecars | **CC BY-SA 4.0** |
 
 Publisher blurbs and cover art are referenced, never copied: descriptions are
 community-written and covers are URLs. Every entity also carries a `sources[]`