Link to issue number:

None.

Summary of the issue:

While working on #14810, I found several places where comments about the core extensionPoints could be made clearer, or had typos/capitalization errors/questionable grammar.

Description of user facing changes

None.

Description of development approach

I fixed them as I went along, and scooped them all into their own branch. Here is the result.

I changed no code in this, and nothing structural has been altered. That is, where #: style comments were used in some places, and docstring style comments in others, I left them that way. I'm not actually sure what we prefer now. I wasn't trying to lint anything, just fix language.

Testing strategy:

Letting Appveyor build this branch in the PR, and see if any lint errors pop out. That's about all I would expect to find.

Known issues with pull request:

None, unless the mixed comment style is an issue. But I didn't do that.

Change log entries:

None needed.

Code Review Checklist:

• Pull Request description:
  • description is up to date
  • change log entries
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• API is compatible with existing add-ons.
• Documentation:
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• Security precautions taken.