📖 [Docs]: Specification requirement anchors render correctly

[Marius Storhaug (MariusStorhaug)]

The Process-PSModule specification now uses markdownlint-compatible explicit anchors for every functional and non-functional requirement, so direct links to FR1-FR6 and NFR1-NFR5 remain reliable.

Changed: Requirement anchors render reliably

All 11 requirement headings now use the canonical {#id} syntax. Requirement identifiers, heading text, link targets, and documented behavior are unchanged.

---

Technical details

• Normalized the 11 explicit anchors in docs/content/Modules/Process-PSModule/specification/spec.md from { #id } to {#id}.
• Backward compatibility: all existing anchor identifiers are preserved.
• Standards and framework alignment:

Changed surface	Standards checked	Framework docs checked	Result
docs/content/Modules/Process-PSModule/specification/spec.md	Markdownlint MD051 anchor syntax	Process-PSModule documentation structure	Aligned

• Issue convergence sweep: this focused documentation-only diff fully carries forward the still-applicable Process documentation portion of 📖 [Docs]: Specifications written from the template now pass the Markdown linter MSXOrg/docs#144; no additional issues are satisfied.

Relevant issues (or links)

• 📖 [Docs]: Specifications written from the template now pass the Markdown linter MSXOrg/docs#144

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
HTML	Pass ✅
JAVASCRIPT_ES	Pass ✅
JAVASCRIPT_PRETTIER	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter