These are all over the place, but several are of interest to the
Chief of Staff team.

Because any maintainer can merge
Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/397788

Fix spelling. Wrap code items in backticks.

Because the information on the top-level
page was random and could go elsewhere

The docs-lint markdown job is sneaky, and runs an additional check
that we don't talk much about.

Also:

- Remove some white space from end of line
- Document using markdownlint-cli2

Also remove references to Atom packages

Because we were mixing up title
versus heading.
Related to:https://gitlab.com/gitlab-org/gitlab/-/issues/361700

Related epic: https://gitlab.com/groups/gitlab-com/-/epics/1940

A very quick, dirty, MVC documentation of the internal_anchors and
internal_links tests. If we document how to fix the problem, we can
add a line to the output linking to the explanation. Self-solving FTW.

While we're here, correct a British spelling.

- Link to issue with external config instructions

Based on many discussions we've had,
we should fail the pipeline
only for very important reasons.
We want to make it easy for contributors
to contribute, and for all of us to quickly
iterate on our documentation