@@ -187,7 +187,7 @@ The version of an event is included in its type. This allows for easy filtering
187187of events of a specific version, by looking at a single field in the context.
188188Examples of full event versions are:
189189
190- - ` dev.cdevents.build.queued.0.1.0 `
190+ - ` dev.cdevents.build.queued.0.1.0-draft `
191191- ` dev.cdevents.environment.deleted.0.1.0 `
192192
193193### Versioning of the CDEvents specification
@@ -207,7 +207,7 @@ format `vMajor.Minor.Patch`.
207207 identified by a change in the major version, for instance 0.1.2 -> 2.0.0
208208
209209While a version of the specification is work in progress, its version is tagged
210- with an extra ` -draft ` at the end, for instance 0.1.0.
210+ with an extra ` -draft ` at the end, for instance 0.1.0-draft .
211211
212212### Development of a new version
213213
@@ -408,11 +408,11 @@ There are two root use cases that we are considering:
408408
409409The [ CDF Interoperability Special Interest Group] [ sig-interop ] has produced a
410410[ table of the terms] [ tool-terms ] used by different CI/CD tools and how they
411- related to each other. The SIG is also working on distilling a recommended
412- [ shared terminology] [ shared-terms ] . CDEvents strives to adopt to the shared
413- terminology and collaborate with the SIG Interoperability.
411+ relate to each other. The SIG Interoperability is also working on distilling a
412+ recommended [ shared terminology] [ shared-terms ] . CDEvents strives to adopt to the
413+ shared terminology and collaborate with the SIG Interoperability.
414414
415- Work to align terms to those identified by the SIG will continue in upcoming
415+ Work to align terms to those identified by the SIG Interoperability will continue in upcoming
416416CDEvents releases.
417417
418418## Design Decisions
0 commit comments