diff --git a/issues/json-ld11-api-wrongcaseenumvalue.md b/issues/json-ld11-api-wrongcaseenumvalue.md
index 8cb6126d..c7ad304a 100644
--- a/issues/json-ld11-api-wrongcaseenumvalue.md
+++ b/issues/json-ld11-api-wrongcaseenumvalue.md
@@ -1,12 +1,12 @@
 ---
 Title: >-
-  Enum values that ignore naming conventions in JSON-LD 1.1 Processing
+  Enum values that ignore naming conventions in JSON-LD 1.2 Processing
   Algorithms and API
 Tracked: Long deployed
 Repo: 'https://github.com/w3c/json-ld-api'
 ---
 
-While crawling [JSON-LD 1.1 Processing Algorithms and API](https://w3c.github.io/json-ld-api/), the following enum values were found to ignore naming conventions (lower case, hyphen separated words):
+While crawling [JSON-LD 1.2 Processing Algorithms and API](https://w3c.github.io/json-ld-api/), the following enum values were found to ignore naming conventions (lower case, hyphen separated words):
 * [ ] The value `"colliding keywords"` of the enum `JsonLdErrorCode` does not match the expected conventions (lower case, hyphen separated words)
 * [ ] The value `"conflicting indexes"` of the enum `JsonLdErrorCode` does not match the expected conventions (lower case, hyphen separated words)
 * [ ] The value `"context overflow"` of the enum `JsonLdErrorCode` does not match the expected conventions (lower case, hyphen separated words)
@@ -59,6 +59,6 @@ While crawling [JSON-LD 1.1 Processing Algorithms and API](https://w3c.github.io
 
 See [Use casing rules consistent with existing APIs](https://w3ctag.github.io/design-principles/#casing-rules) in Web Platform Design Principles document for guidance.
 
-<sub>Cc @dontcallmedom @tidoust</sub>
+<sub>Cc @tidoust</sub>
 
 <sub>This issue was detected and reported semi-automatically by [Strudy](https://github.com/w3c/strudy/) based on data collected in [webref](https://github.com/w3c/webref/).</sub>