Improve markdown and changelog instructions for clarity and consistency

Author: johlju

.github/instructions/dsc-community-style-guidelines-changelog.instructions.md

@@ -7,7 +7,7 @@ applyTo: "CHANGELOG.md"
 
 - Always update the Unreleased section in CHANGELOG.md
 - Use Keep a Changelog format
-- Describe main changes as concise release notes
-- Reference issues using format #<issue_number>
+- Describe notable changes briefly, ≤2 items per change type
+- Reference issues using format [#<issue_number>](https://github.com/<owner>/<repo>/issues/<issue_number>)
 - No empty lines between list items in same section
 - Do not add item if there are already an existing item for the same change

.github/instructions/dsc-community-style-guidelines-markdown.instructions.md

@@ -10,3 +10,14 @@ applyTo: "**/*.md"
 - Use '1.' for all items in ordered lists (1/1/1 numbering style)
 - Surround fenced code blocks with blank lines
 - Disable `MD013` rule by adding a comment for tables/code blocks exceeding 80 characters
+- Ensure empty line before and after headings
+- Escape backslashes in file paths only (not in code blocks)
+- Ensure empty line before and after code blocks
+- Code blocks must specify language identifiers
+
+## Text Formatting
+
+- Parameters: **bold**
+- Values/literals: `inline code`
+- Resource/module/product names: _italic_
+- Commands/files/paths: `inline code`

CHANGELOG.md

@@ -88,6 +88,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Improved documentation with optimized analysis workflow description.
 - DSC community style guidelines
   - Added requirement to follow guidelines over existing code patterns.
+- Improved markdown and changelog instructions.
 
 ## [17.1.0] - 2025-05-22