Skip to content

Commit 02c16b2

Browse files
authored
Fix typo in Interop 2023 README
1 parent b4daffe commit 02c16b2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

2023/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ If you've had problems using a feature on the web because of differences between
1818
Before making a proposal, here's what to expect:
1919

2020
- There are two kinds of proposals:
21-
- **Focus Area**: Most proposals should fall into the category, where the goal is for browsers to pass a set of tests for a feature. Only features which have high quality specifications and tests are in scope.
21+
- **Focus Area**: Most proposals should fall into this category, where the goal is for browsers to pass a set of tests for a feature. Only features which have high quality specifications and tests are in scope.
2222
- **Investigation Effort**: If a feature is widely implemented, but lacks a high quality specification or tests, an investigation effort may be appropriate. An investigation efforts consists of a set of tasks that will bring the feature up to the bar required for a Focus Area in the future. If this involves any standards work, that work must be done in the appropriate standards group, and those doing the work need to join those groups.
2323
- Interop 2023 is not a venue for specifying new features; that work happens in working groups within organizations such as W3C and WHATWG.
2424
- Interop 2023 is not a process for making browser vendors work on things they're opposed to. Decisions are made by consensus, so highly contentious features are unlikely to be accepted.

0 commit comments

Comments
 (0)