Round 10: fix Docker docs links in gitlab repo
What does this MR do?
In gitlab-org/charts/gitlab!3654 (merged) I learned that the Docker Registry docs had been moved to https://distribution.github.io/distribution/, and I worked on fixing the docs in the charts
repo. (A subject matter expert on Docker would have known, but I am not an SME in this area.)
This merge requests fixes links from the gitlab
repository to those same docs. It takes a little untangling to figure out the new destinations, and it made sense to do the rest of the fixes while they were fresh in my mind.
I want a subject matter expert to look over my work, so I'll give this MR to @eread and @axil for review. Whoever gets to it first, claim your glory and fame!
Related issues
- Related to Round 9: fix links (and table) in Charts repo (gitlab-org/charts/gitlab!3654 - merged) where I was given fixes for these links
- Related to Docs project maintenance tasks, March 2024 (technical-writing#1006 - closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product tier badge under the H1 topic title. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.