Description:
- follow-up to my previous PR #6060
(chore: MarkDown Note marker compatibility spacing)
Main directory: /browsers/
This is a follow-up attempt to standardize the MarkDown Note bubbles
by adding the recommended single space after the quote marker.
MarkDown codestyle & whitespace usage consistency is the main goal here.
Additional proposed changes:
- Remove redundant end-of-line (EOL) whitespace
- Simplify blank space usage in bullet point lists/numbered lists to 1
- Replace some tab characters with 4 blank spaces (GitHub compatibility)
- Reduce redundant blank line whitespace usage:
- remove excessive blank lines between sections
- remove surplus blank lines in minimal bullet point lists
File-specific improvement change:
browsers/edge/microsoft-edge-kiosk-mode-deploy.md
- Add back missing table readability spacing and cell dividers.
Ticket reference or closure:
None that I know of (at least not yet).
Additional notes:
- I have split this modification chore into sub-folder sections
to keep the number of files within a reasonably manageable amount.
- Some of the whitespace changes could not be applied due to layout.
Description:
This PR is a standalone attempt to standardize the MarkDown Note
bubbles by adding the recommended single space after the quote marker.
MarkDown codestyle consistency is the main goal here.
Changes proposed:
- Add single space between the quote marker and the text [!NOTE]
- Add the same spacing to the connected text line in the same bubble
- Apply the same standard to other nearby notes, e.g. [!IMPORTANT]
- Standardize on uppercase [!NOTE] instead of mixed casing ( [!Note] )
- Remove some of the obvious redundant spacing at end-of-file
Ticket reference or closure:
None that I know of (at least not yet).
Additional notes:
I have split this modification chore into sub-folder sections to keep
the number of files within a reasonably manageable amount.
Description:
The 4 images in the subsection "Supported configuration types" are
supposed to be linked to their image files, but the relative links have
been broken by not containing the needed parent directory dots.
Proposed change:
Add the required parent directory dots to enable the links to point to
the files as intended (even if not strictly needed to begin with).
Closes#4275
