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

The destinations of these links have moved. Update them accordingly.

Unfortunately, /help does not render inline Vale exclusions
properly, so we need to move them all to block-level exclusions.

Update tree, blob, issue links to gitlab-org/gitlab with a new format
that includes /-/ scope.

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

In https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27239 the
default branch of GitLab Runner is going to change to `main` which
already exists and being kept in sync with `master` until the full
migration is done.

In some cases I've added `/-/` path seperator to use the new URL
structure in GitLab.

reference https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27239

We recently renamed `master` -> `main`. Some doc links were not updated.

Updates all redirecting and 404'ing links in
the /doc/development directory

Handle another round of spelling issues in whatever ways seem best.

- Change "within" to "in" where appropriate
- Make extension lists and link similar

Continuing to clean up spelling issues from our docsets!

This will ease the integration of Lefthook with GitPod.

Signed-off-by: Rémy Coutable <remy@rymai.me>

These words were referenced in rules but we didn't have them
clearly stated in the usage guide.

Explain the three types of results from Vale, what they mean, and
whether or not they appear in / break CI.