Docs: fix two broken links

[chenxsan]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

I just noticed another two links are broken on this page.

Before:

1. https://eslint.org/docs/developer-guide/working-with-rules#messageIds
2. https://eslint.org/docs/developer-guide/nodejs-api#Linter

After:

1. https://eslint.org/docs/developer-guide/working-with-rules#messageids
2. https://eslint.org/docs/developer-guide/nodejs-api#linter

It seems that the markdown-it-anchor plugin eslint website is using would transform all characters in header into lower case, see https://github.com/valeriangalliat/markdown-it-anchor/blob/master/index.js#L3. Which means every URI fragment used on eslint website has to be in lower case, otherwise links generated will be broken just like the aforementioned ones.

Is there anything you'd like reviewers to focus on?

Nothing.

[eslint-github-bot]

Hi @chenxsan!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

• The first letter of the tag should be in uppercase

Read more about contributing to ESLint here

[snitin315]

LGTM. Thanks!

[aladdin-add]

LGTM, thanks!