Bogus comments INCORRECT_TERM_SPELLING and INVALID_REQLEVEL_KEYWORD

[tomaszmrugalski]

I got this comment when using 3.0.0-alpha.36 on rfc8415bis:

 4  Comment
 └- Code - INCORRECT_TERM_SPELLING
 └- Desc - "e mail" should be spelled as email (no hyphen).
 └- Ref  - https://www.rfc-editor.org/materials/terms-online.txt
 └- Line - Ln 5771 Col 42

What the actual I-D text had: More than 500 users subscribed to the mailing list. Seems like the mailing triggers a regexp for e mail.

You can generate the txt from repo linked above or let me know and I'll provide a txt that triggers this bug. Didn't want to litter a simple ticket with 150kb+ file.

BTW Thanks for this tool. It's been invaluable over the years. This new iteration feels even better.

[tomaszmrugalski]

And another one:

3  Comment
 └- Code - INVALID_REQLEVEL_KEYWORD
 └- Desc - MAY not is not a valid RFC2119 Requirement Level keyword.
 └- Ref  - https://datatracker.ietf.org/doc/html/rfc2119
 └- Line - Ln 1 Col 52

The actual texts says and MAY notify these programs.