Docs: Enforce consistent prefix for bullet lists
What does this MR do?
Enforced Markdown rule MD004 for the MarkDownLint: https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md#md004---unordered-list-style, which aligns with our Styleguide for bullet lists: https://docs.gitlab.com/ee/development/documentation/styleguide.html#list-items.
asterisks replaced with hyphens as necessary.
Related issues
Related to https://gitlab.com/gitlab-com/gitlab-docs/issues/287
Related to https://gitlab.com/gitlab-com/gitlab-docs/issues/397
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.
Edited by Marcel Amirault