Updates based on Acrolinx score reports

Author: ChrisHowd

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/10-knowledge-check.yml

@@ -72,7 +72,7 @@ quiz:
     - content: "TDD operates at the unit test level, while SDD works at a higher requirements level to describe complete features."
       isCorrect: true
       explanation: "Correct. TDD drives design through unit tests for individual functions, while SDD uses specifications that describe complete features to drive design and code generation."
-    - content: "TDD and SDD are mutually exclusive approaches that cannot be used together."
+    - content: "TDD and SDD are mutually exclusive approaches that can't be used together."
       isCorrect: false
       explanation: "Incorrect. TDD and SDD can complement each other. You can use SDD for overall direction and still apply TDD within implementation."
     - content: "SDD produces automated tests while TDD produces specifications."
@@ -157,7 +157,7 @@ quiz:
       explanation: "Incorrect. Tasks are stored in tasks.md, not constitution.md. The constitution contains guiding principles, not task lists."
   - content: "What is the recommended sequence for using GitHub Spec Kit commands in a greenfield project?"
     choices:
-    - content: "Run commands in any order since they are independent of each other."
+    - content: "Run commands in any order since they're independent of each other."
       isCorrect: false
       explanation: "Incorrect. The commands follow a specific sequence where each builds on the outputs of the previous one."
     - content: "specify init, then /speckit.constitution, /speckit.specify, /speckit.plan, /speckit.tasks, and finally /speckit.implement."

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/2-what-spec-driven-development.md

@@ -1,20 +1,3 @@
-<!--
-=============================================================================
-CONTENT SOURCE TRACKING
-=============================================================================
-This unit was constructed using content from the following sources:
-
-Source File: includes/2-review-spec-driven-development-approach.md
-  - Section: "The shift to spec-driven development" (paragraphs 1-4)
-  - Section: "Why spec-driven development matters now" (all bullet points)
-  - Section: "The core principles of spec-driven development" (adapted for key features)
-  - Opening paragraph (traditional development context)
-
-Source File: includes/3-examine-github-spec-kit.md
-  - Opening paragraph (context about AI-assisted development challenges)
-=============================================================================
--->
-
 In traditional software development, we often treat code as the ultimate source of truth. Specifications serve code - they're the scaffolding we build and then discard once the "real work" of coding begins. We write Product Requirements Documents (PRDs) to guide development, create design docs to inform implementation, and draw diagrams to visualize architecture. But these documents are always subordinate to the code itself. As code moves forward, specs rarely keep pace.
 
 With the rise of powerful AI coding assistants like GitHub Copilot, this code-first approach evolved into what we now call "vibe coding." Unfortunately, the vibe coding approach often involves submitting a high-level prompt that returns a chunk of code that "looks right" but might miss the intent or have errors. It can be fast, but sometimes it's misaligned. Each chat session operates in isolation, lacking awareness of previous decisions or overall project requirements.

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/3-examine-spec-driven-development-principles-processes.md

@@ -1,25 +1,3 @@
-<!--
-## Content Sources
-
-This unit was built from the following source content:
-
-**Primary Sources:**
-- includes/2-review-spec-driven-development-approach.md
-  - "The shift to spec-driven development" section
-  - "The spec-driven development workflow in practice" section
-  - "The core principles of spec-driven development" section
-  - "Why spec-driven development matters now" section
-
-**Supporting Sources:**
-- includes/5-write-effective-spec-file.md
-  - "The spec as the single source of truth" section (Specify phase details)
-- includes/6-create-technical-plan-file.md
-  - "Understand the purpose of a technical plan" section (Plan phase details)
-- includes/7-generate-implementation-tasks-file.md
-  - "Benefits of task breakdown" section (Tasks phase details)
-  - "Phase-based organization" section
--->
-
 The spec-driven development (SDD) methodology provides a phased approach to software development that emphasizes clarity, structure, and adaptability. By breaking down the development process into four distinct phases—Specify, Plan, Tasks, and Implement—SDD ensures that each step is well-defined and builds upon the previous one. This structured workflow not only enhances communication among stakeholders but also allows for continuous refinement and adaptation of the software being developed.
 
 ## SDD workflow overview

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/4-compare-spec-driven-development-other-methodologies.md

@@ -1,25 +1,3 @@
-<!--
-## Content Sources
-
-This unit was built from the following source content:
-
-**Primary Sources:**
-- includes/2-review-spec-driven-development-approach.md
-  - "The shift to spec-driven development" section (SDD core characteristics)
-  - "Why spec-driven development matters now" section (drivers and benefits)
-  - "The core principles of spec-driven development" section
-
-**Supporting Sources:**
-- includes/5-write-effective-spec-file.md
-  - "For enterprise developers accustomed to agile workflows..." (Agile comparison context)
-- includes/7-generate-implementation-tasks-file.md
-  - Task granularity and verification concepts (for TDD comparison)
-- Module Outline
-  - Unit 4 outline requirements (comparison framework and methodology positioning)
-
-**Note:** The source module doesn't contain direct methodology comparisons. Content was derived from SDD principles in source materials and structured according to the module outline's comparison framework.
--->
-
 Understanding how spec-driven development (SDD) relates to other software development methodologies helps you see where it fits in your existing practices. Rather than replacing what you already know, SDD can complement and enhance established approaches, especially when you're using AI-assisted development tools.
 
 ## Methodology comparison overview

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/5-examine-spec-driven-development-workflow-phases.md

@@ -1,26 +1,3 @@
-<!--
-## Content Sources
-
-This unit was built from the following source content:
-
-**Primary Sources:**
-- includes/5-write-effective-spec-file.md
-  - "The spec as the single source of truth" section
-  - "Specification structure" section (Summary, User Stories, Acceptance Criteria, Functional Requirements, Nonfunctional Requirements, Edge Cases)
-  
-- includes/6-create-technical-plan-file.md
-  - "Understand the purpose of a technical plan" section
-  - "Examine plan structure and content" section (Architecture overview, Technology stack, Implementation sequence, Constitution verification, Assumptions)
-  
-- includes/7-generate-implementation-tasks-file.md
-  - "Benefits of task breakdown" section
-  - "Examine task structure and organization" section (Phase-based organization, Task granularity, Dependencies)
-  
-**Supporting Sources:**
-- includes/2-review-spec-driven-development-approach.md
-  - "The spec-driven development workflow in practice" section (workflow flow narrative)
--->
-
 Each phase of the Spec-Driven Development (SDD) workflow plays a crucial role in transforming ideas into working software. Developers who understand the purpose, content, and output of each phase can apply SDD effectively to their own projects.
 
 > [!NOTE]

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/6-introduction-github-spec-kit.md

@@ -1,20 +1,3 @@
-<!--
-## Content Sources
-
-This unit was built from the following source content:
-
-**Primary Sources:**
-- includes/3-examine-github-spec-kit.md
-  - "What is GitHub Spec Kit?" section
-  - "Key components of GitHub Spec Kit" section (Specify CLI, Markdown artifact files, Slash commands)
-  - "GitHub Spec Kit's AI agent support" section (Multi-agent compatibility)
-  - "Integrate GitHub Spec Kit with Git workflows" section (Project structure conventions)
-
-**Supporting Sources:**
-- includes/4-establish-project-principles-constitution-file.md
-  - Constitution concept and purpose (for explaining project constitution)
--->
-
 GitHub Spec Kit is an open-source toolkit that operationalizes spec-driven development (SDD) by providing a structured workflow, persistent artifacts, and AI integration. It guides you through the SDD phases of Specify, Plan, Tasks, and Implement using commands and templates, enabling efficient, consistent, and high-quality software development.
 
 ## What is GitHub Spec Kit?

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/7-examine-github-spec-kit-environment-installation.md

@@ -1,25 +1,3 @@
-<!--
-## Content Sources
-
-This unit was built from the following source content:
-
-**Primary Sources:**
-- includes/3-examine-github-spec-kit.md
-  - "Key components of GitHub Spec Kit" → "Specify CLI tool" section (installation commands)
-  - "GitHub Spec Kit's AI agent support" → "Multi-agent compatibility" section (supported agents list)
-
-**Supporting Sources:**
-- Module Outline (Unit 7)
-  - Prerequisites and system requirements
-  - Installation methods (global and one-time)
-  - Visual Studio Code setup specifics
-  - Troubleshooting guidance
-
-**External References:**
-- GitHub Spec Kit README (installation instructions, uv tool usage)
-- blog.ovilgroup.com (installation walkthrough, prerequisites)
--->
-
 Before you can use GitHub Spec Kit to practice spec-driven development, you need to set up your environment. This unit covers the prerequisites, installation process, and configuration steps to get GitHub Spec Kit running in your development environment.
 
 ## Prerequisites and system requirements
@@ -89,9 +67,9 @@ uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
 
 Global installation provides these benefits:
 
-- Available in any project directory
-- Easy to update using `uv tool upgrade specify-cli`
-- No need to rerun installation commands each time
+- Available in any project directory.
+- Easy to update using `uv tool upgrade specify-cli`.
+- No need to rerun installation commands each time.
 
 ### Method 2: One-time usage
 
@@ -118,8 +96,8 @@ specify check
 
 This command checks for required tools and confirms that installation succeeded. It reports:
 
-- Whether Git is found and configured.
-- Whether your AI coding assistant is detected.
+- Whether or not Git is found and configured.
+- Whether or not your AI coding assistant is detected.
 - Any missing dependencies or configuration issues.
 
 If `specify check` reports issues, address them before proceeding.

learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/8-examine-github-spec-kit-commands-results.md

@@ -1,25 +1,3 @@
-<!--
-## Content Sources
-
-This unit was built from the following source content:
-
-**Primary Sources:**
-- includes/3-examine-github-spec-kit.md
-  - "Key components of GitHub Spec Kit" → "Slash commands" section
-  - "Leverage GitHub Spec Kit's optional enhancement commands" section (/speckit.clarify, /speckit.analyze, /speckit.checklist)
-  - "Continuous workflow support" section (command chaining)
-
-**Supporting Sources:**
-- includes/4-establish-project-principles-constitution-file.md
-  - Constitution purpose and structure (for /speckit.constitution context)
-- includes/5-write-effective-spec-file.md
-  - Spec structure and sections (for spec.md output context)
-- includes/6-create-technical-plan-file.md
-  - Plan structure and content (for plan.md output context)
-- includes/7-generate-implementation-tasks-file.md
-  - Task structure and organization (for tasks.md output context)
--->
-
 With GitHub Spec Kit installed, you're ready to use its commands to practice spec-driven development. This unit walks through each command in the workflow, explaining what it does, what output it produces, and how to work with the results. Understanding this process prepares you for the hands-on lab exercise.
 
 ## Command overview