Align docs with TemplateDotNetLibrary pattern for Continuous Compliance

Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>

Author: Copilot

README.md

@@ -22,10 +22,13 @@ This template demonstrates:
 - **Multi-Runtime Support**: Targets .NET 8, 9, and 10
 - **Comprehensive CI/CD**: GitHub Actions workflows with quality checks, builds, and
   integration tests
+- **Linting Enforcement**: markdownlint, cspell, and yamllint enforced on every CI run
+- **Continuous Compliance**: Compliance evidence generated automatically on every CI run, following
+  the [Continuous Compliance][link-continuous-compliance] methodology
+- **SonarCloud Integration**: Quality gate and security analysis on every build
 - **Documentation Generation**: Automated build notes, user guide, code quality reports,
   requirements, justifications, and trace matrix
-- **Continuous Compliance**: Automated, evidence-based quality enforcement following the
-  [DEMA Consulting Continuous Compliance strategy](https://github.com/demaconsulting/ContinuousCompliance)
+- **Requirements Traceability**: Requirements linked to passing tests with auto-generated trace matrix
 
 ## Installation
 
@@ -134,3 +137,4 @@ By contributing to this project, you agree that your contributions will be licen
 [link-security]: https://sonarcloud.io/dashboard?id=demaconsulting_TemplateDotNetTool
 [link-nuget]: https://www.nuget.org/packages/DemaConsulting.TemplateDotNetTool
 [link-guide]: https://github.com/demaconsulting/TemplateDotNetTool/blob/main/docs/guide/guide.md
+[link-continuous-compliance]: https://github.com/demaconsulting/ContinuousCompliance

docs/guide/guide.md

@@ -14,12 +14,19 @@ This user guide covers:
 - Command-line options reference
 - Practical examples for various scenarios
 
-## Continuous Compliance
+# Continuous Compliance
 
-This project follows the [DEMA Consulting Continuous Compliance][continuous-compliance]
-strategy — automated, evidence-based quality enforcement on every CI/CD run. Each build
-automatically lints documentation, verifies all requirements are covered by passing tests,
-runs code quality gates, records tool versions, and generates a complete audit trail.
+This template follows the [Continuous Compliance][continuous-compliance] methodology, which ensures
+compliance evidence is generated automatically on every CI run.
+
+## Key Practices
+
+- **Requirements Traceability**: Every requirement is linked to passing tests, and a trace matrix is
+  auto-generated on each release
+- **Linting Enforcement**: markdownlint, cspell, and yamllint are enforced before any build proceeds
+- **Automated Audit Documentation**: Each release ships with generated requirements, justifications,
+  trace matrix, and quality reports
+- **CodeQL and SonarCloud**: Security and quality analysis runs on every build
 
 # Installation