Update IssueTriage.md

Co-authored-by: Anssi Kostiainen <[email protected]>

Author: inexorabletash

IssueTriage.md

@@ -37,13 +37,11 @@ Every issue should have one of these issue types, and only rarely more than one.
 
 These broad categories describe the projected impact on the specification and implementation of an issue.
 
-- **Editorial** - spec text could be improved, but does not imply normative behavior changes to the proposed API
-- **Normative** - _PROPOSED_ - resolving the issue would require behavior changes, likely affecting implementations and tests
+- **editorial** - spec text could be improved, but does not imply normative behavior changes to the proposed API
+- **normative** - _PROPOSED_ - resolving the issue would require behavior changes, likely affecting implementations and tests
 
 TODO: I'm not convinced of the utility of these; maybe drop them?
 
-TODO: Make these lowercase for consistency?
-
 ## Issue Scope
 
 Every issue should have at least one of these issue types, but occasionally multiple.