SSoT audit fixes for some topics in GitLab U section
Related issues
As part of &1280 (closed), audit some topics in docs/university
for adherence to SSoT guidelines.
Includes fixes where necessary. Also includes some other improvements to markdown and grammar.
Some topics not part of phase 1 are included with some fixes, because it makes markdownlint
run cleaning and potential pays forward to running markdownlint
or similar in a pipeline.
Related issues
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61513.
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the ~Documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.