From 544ddcb76f33328224d32982af89d1be4aba2d27 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A5rten=20Angner?= Date: Sun, 1 Mar 2026 15:24:23 +0100 Subject: [PATCH] Fix markdownlint errors in learn section - Deduplicate heading in lesson-02 (specifications) - Disable MD024 for lesson-03 (repeated component spec structure) - Fix bare URL in tutorial-11 Co-Authored-By: Claude Opus 4.6 --- .../lesson-02-why-specifications-matter.md | 2 +- .../lesson-03-element-state-specifications.md | 1 + docs/learn/module-11-conceptual-specifications/tutorial-11.md | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md b/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md index 0b1f8f0ff..3e363b0f1 100644 --- a/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md +++ b/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md @@ -754,7 +754,7 @@ Many methodologies exist. What makes WDS different? --- -## Your App Exists in Specifications +## Remember: Your App Exists in Specifications **Let this sink in:** diff --git a/docs/learn/module-11-conceptual-specifications/lesson-03-element-state-specifications.md b/docs/learn/module-11-conceptual-specifications/lesson-03-element-state-specifications.md index d0b18a884..0f07137d1 100644 --- a/docs/learn/module-11-conceptual-specifications/lesson-03-element-state-specifications.md +++ b/docs/learn/module-11-conceptual-specifications/lesson-03-element-state-specifications.md @@ -1,3 +1,4 @@ + # Module 11: Conceptual Specifications ## Lesson 3: Element & State Specifications diff --git a/docs/learn/module-11-conceptual-specifications/tutorial-11.md b/docs/learn/module-11-conceptual-specifications/tutorial-11.md index ac4987d39..b808e2159 100644 --- a/docs/learn/module-11-conceptual-specifications/tutorial-11.md +++ b/docs/learn/module-11-conceptual-specifications/tutorial-11.md @@ -116,7 +116,7 @@ Transform curious visitors into registered users. > "Let's specify each element. Starting with the email field — what are the details?" **You respond:** -> "Text input, label says 'Email', placeholder 'you@example.com', validates email format, error message 'Please enter a valid email'." +> "Text input, label says 'Email', placeholder '`you@example.com`', validates email format, error message 'Please enter a valid email'." **Freya documents:** ```markdown