Remove invalid markup
What does this MR do?
This fixes the kramdown warnings in this file due to the use of invalid tags:
kramdown warning(s) for <Nanoc::Core::CompilationItemRepView item.identifier=/ee/architecture/blueprints/gitlab_ml_experiments/index.md name=default>
Found block HTML tag 'ol' in span-level text on line 133
Found block HTML tag 'li' in span-level text on line 133
Found invalidly used HTML closing tag for 'li' on line 133
Found block HTML tag 'li' in span-level text on line 133
Found invalidly used HTML closing tag for 'li' on line 133
Found block HTML tag 'li' in span-level text on line 133
Found invalidly used HTML closing tag for 'li' on line 133
Found invalidly used HTML closing tag for 'ol' on line 133
Found block HTML tag 'ol' in span-level text on line 137
Found block HTML tag 'li' in span-level text on line 137
Found invalidly used HTML closing tag for 'li' on line 137
Found block HTML tag 'li' in span-level text on line 137
Found invalidly used HTML closing tag for 'li' on line 137
Found block HTML tag 'li' in span-level text on line 137
Found invalidly used HTML closing tag for 'li' on line 137
Found invalidly used HTML closing tag for 'ol' on line 137
Found block HTML tag 'ol' in span-level text on line 139
Found block HTML tag 'li' in span-level text on line 139
Found invalidly used HTML closing tag for 'li' on line 139
Found block HTML tag 'li' in span-level text on line 139
Found invalidly used HTML closing tag for 'li' on line 139
Found invalidly used HTML closing tag for 'ol' on line 139
Found block HTML tag 'ol' in span-level text on line 151
Found block HTML tag 'li' in span-level text on line 151
Found invalidly used HTML closing tag for 'li' on line 151
Found block HTML tag 'li' in span-level text on line 151
Found invalidly used HTML closing tag for 'li' on line 151
Found block HTML tag 'li' in span-level text on line 151
Found invalidly used HTML closing tag for 'li' on line 151
Found invalidly used HTML closing tag for 'ul' on line 151
Found block HTML tag 'ol' in span-level text on line 158
Found block HTML tag 'li' in span-level text on line 158
Found invalidly used HTML closing tag for 'li' on line 158
Found invalidly used HTML closing tag for 'ol' on line 158
Found block HTML tag 'ol' in span-level text on line 159
Found block HTML tag 'li' in span-level text on line 159
Found invalidly used HTML closing tag for 'li' on line 159
Found invalidly used HTML closing tag for 'ol' on line 159
Found block HTML tag 'ol' in span-level text on line 161
Found block HTML tag 'li' in span-level text on line 161
Found invalidly used HTML closing tag for 'li' on line 161
Found invalidly used HTML closing tag for 'ol' on line 161
Found block HTML tag 'ol' in span-level text on line 164
Found block HTML tag 'li' in span-level text on line 164
Found invalidly used HTML closing tag for 'li' on line 164
Found invalidly used HTML closing tag for 'ol' on line 164
Related issues
Related to !135741 (merged)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
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.
Edited by Marcel Amirault