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.
* fixed issue with h1s from hotlinked note-articles rendering as duplicate h1s
* testing path is correct
* find & replace old path > new path
attempting to fix issue with note-articles not being in seperate /includes dir
* fixed link on note page
* Adding a sentence to dynamic lock
* Add titleSuffix for mdop
* Add titleSuffix for smb
* Add titleSuffix for surface-hub
* Add titleSuffix for Edge
* Add titleSufix for client-management
* Correct metadata attribute
* Add titleSuffix for application-management
* Add titleSuffix for surface
* Add titleSuffix for hub
* pencil edit
line 27
* Add titleSuffix for deployment
* pencil edit
line 27
* pencil edit
line 27
* pencil edit
line 27
* Add titleSuffix for internet-explorer
* Add titleSuffix for privacy
Also added one tab spacing for lines 43-47 for beautification
* Add titleSuffix for whats-new
* Add titleSuffix for security
* Add titleSuffix for configuration
* CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20191210080851 (#1678)
Correcting the sample xml so that the comments don't break parsing rules. Also, updating the "Default" and "None" captialization to be consistent with our other documentation and tools.
Updating the "Deprecated attributes" section to be more accurate about elements and attributes. Also corrected samples.
This change fixes 2 issues in the "Schema Attributes" section.
1. This section uses < and > around the attribute names, which is confusing, because that is notation reserved for elements.
2. The description of exclude is a little vague and somewhat misleading.
The sample xml has a couple of problems that are fixed here.
1. Comments use -- not --- to begin and end. 3 hyphens will cause a parse error.
2. The default values for <compat-mode> (Default) and <open-in> (None) are not capitalized, which doesn't fit with other documentation and tools.
As previously discussed in this PR, I have converted the
**Important** section headings by using their MarkDown equivalent
> [!IMPORTANT] (as well as adding the blockquote for its text content).
