diff --git a/errata.html b/errata.html
index 945cdc09e..fbf7c225d 100644
--- a/errata.html
+++ b/errata.html
@@ -6,7 +6,7 @@
-->
- Open Errata for the Verifiable Credentials Working Group
+ Open Errata for the Verifiable Credentials Data Model v2.0
@@ -24,7 +24,7 @@
-
Open Errata for the Verifiable Credentials Working Group
+
Open Errata for the Verifiable Credentials Data Model v2.0
Latest errata update:
@@ -38,15 +38,15 @@
Open Errata for the Verifiable Credentials Working Group
An issue is raised for a possible erratum. The label of the issue SHOULD be set to “ErratumRaised”. It is o.k. for an erratum to have several labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a reference to a document.
-
Issues labeled as “Editorial” are displayed separately, to make it easier to differentiate editorial errata from substantive ones.
-
The community discusses the issue. If it is accepted as a genuine erratum, the label “Errata” is added to the entry and the “ErratumRaised” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion).
-
If the community rejects the issue as an erratum, the issue should be closed.
-
Each errata may be labelled as “Editorial”; editorial errata are listed separately from the substantive ones.
-
ALL substantive errata are generally expected to have corresponding test(s) (such as a pull request in web-platform-tests), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.
-
+
An issue is raised for a possible erratum. The label of the issue SHOULD be set to “PossibleErratum”. One erratum might have several labels.
+
The community discusses the issue. If it is accepted as a genuine erratum, the label “Errata” is added to the entry and the “PossibleErratum” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion).
+
Issues labeled as “Errata” are displayed below.
+
If the community rejects the issue as an erratum, the issue should be closed (but they will not be removed from the listing below, to ensure a historical record).
+
Each errata may also be labelled as “Editorial”; editorial errata are listed separately from the substantive ones.
+
ALL substantive errata are generally expected to have corresponding test(s), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.
+
-
This report contains a reference to all open issues with the label Errata, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.
+
This report contains a reference to all open issues with the label Errata.
If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group, ivan.
@@ -57,15 +57,15 @@
How to Submit an Erratum?
-
Open Errata on the “Verifiable Credentials Data Model 1.0” Recommendation
+
Open Errata on the “Verifiable Credentials Data Model v2.0”