Skip to content

Commit 02137b2

Browse files
domenicannevk
authored andcommitted
Fix typos in Stages
1 parent 31d1502 commit 02137b2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Stages.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ These checkpoints are modeled loosely on the [TC39 process](https://tc39.es/proc
1212

1313
* <dfn>Stage</dfn>: each successive stage is closer to an integrated [Contribution](./IPR%20Policy.md#21-contribution) and interoperable implementation. These stages are tracked on the issues in the relevant WHATWG GitHub repository, using labels ("stage 0", "stage 1", etc.). The stages are described in the Stages overview below.
1414
* <dfn>Browser engine</dfn>: an independent implementation of the web platform (i.e., Chromium, Gecko, and WebKit at present).
15-
* <dfn>Implementation interest</dfn>: a direct signal from a browser engine that a feature is on the roadmap to implement, as defined in the [Working Mode](./Working%20Mode.md#additions)].
15+
* <dfn>Implementation interest</dfn>: a direct signal from a browser engine that a feature is on the roadmap to implement, as defined in the [Working Mode](./Working%20Mode.md#additions).
1616
* <dfn>Browser engine representatives</dfn>: persons delegated by a browser engine to indicate implementer interest.
1717

1818
## Process
@@ -24,7 +24,7 @@ These checkpoints are modeled loosely on the [TC39 process](https://tc39.es/proc
2424
* Stage labels (other than stage 0) should only be added by browser engine representatives, or by Editors of the relevant standard, once necessary support for a level has been demonstrated.
2525
* This process is subject to and governed by [WHATWG Policies](./Policies.md), including the [Intellectual Property Rights Policy](./IPR%20Policy.md).
2626
* **Advancing stages**
27-
* The [Contributor](./IPR%20Policy.md#contributor) should bring the [Contribution](./IPR%20Policy.md#21-contribution) to the WHATWG to advance to the next stage by setting an “Agenda+” label on the tracking issue, and showing up to (or ensuring someone will show up to) the next triage meeting to discuss. Advancing to a new stage requires support for the decision by at least two implementers (via their browser engine representatives), and there should not be any strong implementer objections ([per the working mode](./Working%20Mode.md#additions). This support can also be gathered in any public manner, e.g., GitHub issue comments, triage meetings, etc.
27+
* The [Contributor](./IPR%20Policy.md#contributor) should bring the [Contribution](./IPR%20Policy.md#21-contribution) to the WHATWG to advance to the next stage by setting an “Agenda+” label on the tracking issue, and showing up to (or ensuring someone will show up to) the next triage meeting to discuss. Advancing to a new stage requires support for the decision by at least two implementers (via their browser engine representatives), and there should not be any strong implementer objections ([per the working mode](./Working%20Mode.md#additions)). This support can also be gathered in any public manner, e.g., GitHub issue comments, triage meetings, etc.
2828
* Positive support to advance a stage does **not** imply:
2929
* Commitment to eventually support a subsequent stage.
3030
* That the particular solution approach at the time of the signal or support will be the one eventually standardized (unless the advancement is to the Standardized stage).

0 commit comments

Comments
 (0)