Additional formatting updates based on reviewer feedback

Author: ChrisHowd

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

@@ -1,9 +1,9 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.spec-driven-development-github-spec-kit-greenfield-intro.introduction-github-spec-kit
-title: "Introduce GitHub Spec Kit for spec-driven development"
+title: "What is GitHub Spec Kit?"
 metadata:
-  title: "Introduce GitHub Spec Kit for Spec-Driven Development"
-  description: "Introduce GitHub Spec Kit for spec-driven development."
+  title: "What is GitHub Spec Kit?"
+  description: "What is GitHub Spec Kit?"
   ms.date: 01/26/2026
   author: chrishowd
   ms.author: cahowd

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

@@ -6,15 +6,15 @@ The topics covered in this module include:
 
 - Understanding what spec-driven development is and why it matters now.
 - Exploring the principles and phases of the SDD workflow.
-- Comparing spec-driven development to other methodologies like Waterfall, Agile, and test-driven development (TDD).
+- Comparing spec-driven development to other methodologies like Waterfall, Agile, and test-driven development.
 - Examining the SDD workflow phases in detail: Specify, Plan, Tasks, and Implement.
 - Introducing GitHub Spec Kit as a toolkit for practicing SDD.
 - Configuring your environment and installing GitHub Spec Kit.
 - Using GitHub Spec Kit commands to generate the constitution, spec, plan, and tasks files.
 
 After completing this module, you'll be able to:
 
-- Describe the principles and phases of the spec-driven development (SDD) methodology.
+- Describe the principles and phases of the spec-driven development methodology.
 - Use GitHub Spec Kit commands to create the constitution.md, spec.md, plan.md, and tasks.md files.
 - Implement a greenfield application from start to finish using GitHub Spec Kit's AI-assisted workflows.
 

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

@@ -7,7 +7,7 @@ Each phase of the Spec-Driven Development (SDD) workflow plays a crucial role in
 
 Imagine you're building a new application: an RSS Feed Reader that lets users subscribe to feeds, see new articles, and track what they've read. How do you go from this idea to working code using SDD? The answer is a systematic progression through four phases, each producing artifacts that feed into the next.
 
-## Phase 1: Specify (define the "what" and the "why")
+## Phase 1: Specify
 
 The specification defines exactly what the software should do. Every implementation decision traces back to it. If functionality doesn't appear in the spec, it doesn't appear in the final product unless you update the spec.
 
@@ -45,7 +45,7 @@ A well-structured specification includes several key sections:
 
 Writing the spec is as important as writing code. The spec isn't a formality to satisfy project management - it's the artifact that drives AI-assisted code generation. Invest the same care in crafting specs as you would in implementing features manually.
 
-## Phase 2: Plan (define the "how")
+## Phase 2: Plan
 
 A specification defines what you need to build. A technical plan defines *how* you build it. The plan transforms requirements into architecture decisions, ensuring your implementation aligns with both the specification and your project's governing principles.
 
@@ -76,7 +76,7 @@ A plan should include the following elements:
 
 If you later switch technologies - say, moving from SQLite to a different database - you update the plan while the specification remains largely unchanged. The feature requirements don't change; only the implementation approach changes.
 
-## Phase 3: Tasks (break it down)
+## Phase 3: Tasks
 
 Technical plans provide architectural direction, but implementation requires concrete, actionable steps. The tasks phase converts high-level decisions into specific work items.
 
@@ -114,7 +114,7 @@ Before moving to implementation, review tasks against the plan and spec. For exa
 - If a requirement isn't covered by a task, add a corresponding task.
 - If a task isn't associated with the plan or spec, evaluate whether the task is needed.
 
-## Phase 4: Implement (code the solution)
+## Phase 4: Implement
 
 If phases 1-3 are done well, implementation should be straightforward. You can execute tasks one by one with clear guidance.
 

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

@@ -1,7 +1,3 @@
-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?
-
 GitHub Spec Kit is an open-source toolkit developed by GitHub to facilitate spec-driven development. It's designed to integrate with AI coding assistants like GitHub Copilot and orchestrate the SDD workflow through structured commands, templates, and persistent artifacts.
 
 Think of GitHub Spec Kit as a copilot for your copilot - it guides the AI through a structured process, ensuring consistent, high-quality output at each phase of development.

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

@@ -264,6 +264,8 @@ Generates quality verification checklists for your specification. Use this comma
 
 ## Best practices
 
+There are several best practices to follow when using GitHub Spec Kit:
+
 - **Always review AI outputs:** Don't blindly accept generated content. The AI assists, but you're the domain expert.
 
 - **Communicate clearly in prompts:** The quality of output depends on the quality of input. Include all important requirements and constraints.