Because we have a standard of
"For more information, see..."

Because they are on the other pages
as well as the handbook.
Related to: https://gitlab.com/gitlab-org/technical-writing/-/issues/744

Old link was to a hard-coded link that redirected users to a new url.

New link uses relative path that works in compiled documentation.

merge_request_application_and_rate_limit_guidelines.md becomes
rate_limits.md in a subdirectory.

As part of reuniting pages related to merge requests together in a
single subdirectory, let's start by shifting the page and giving it
a MERCIFULLY SHORTER filename.

Bring this statement closer to GitLab tone
and style.

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

- Update templates
- Update occurences of contributing/#breaking-changes

The TW team has to clean up stray whitespace every month,
so we should have a vale rule to gently warn people
when they are introducing EOL whitespace

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Per discussion during CTO office hours on Thursday, May 5 2022, we
want to include observability in our definition of done to increase our
ability to diagnose issues reactively and proactively.

Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

This makes it easier to grok. We are also looking
to rewrite most of this, and doing this in smaller
chunks will make this easier.

The "Accepting merge requests" label is being re-named to "Seeking
merge requests" to improve clarity. This updates all references in
the documentation.

For the sake of productivity metrics, MRs should have the group
label of the group that executed or coached the work, which is not
necessarily the group that owns the feature. Previously that was
not clear in the handbook, so this adds some guidance.

Related to: https://gitlab.com/gitlab-org/technical-writing/-/issues/492