From e307bf8aff26cbc2fb263f91bccf89de3493776a Mon Sep 17 00:00:00 2001
From: Olaf Zimmermann <olaf.zimmermann@ost.ch>
Date: Wed, 30 Oct 2024 07:35:50 +0100
Subject: [PATCH] Fixed heading level, made Y template consistent

---
 _posts/2024-10-25-adr-templates.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/_posts/2024-10-25-adr-templates.md b/_posts/2024-10-25-adr-templates.md
index ffdf447..5d523b7 100644
--- a/_posts/2024-10-25-adr-templates.md
+++ b/_posts/2024-10-25-adr-templates.md
@@ -26,7 +26,7 @@ MADR is about architectural decisions that *matter* ([`[ˈmæɾɚ]`](https://en.
 
 We think that the *considered options* with their pros and cons are crucial to understand the reasons for choosing a particular design. Therefore, the [Markdown Architectural Decision Records (MADR)](https://adr.github.io/madr/) project in this organization includes such tradeoff analysis information. It also suggests metadata such as decision makers and confirmation in addition to decision status.
 
-## Nygard ADR
+### Nygard ADR
 
 An ADR consists of title, status, context, decision, and consequences according to "Documenting Architecture Decisions" by [@mtnygard](https://github.com/mtnygard). <!-- From the Nygard post: "Context This section describes the forces at play, including technological, political, social, and project local." and "We should use a lightweight text formatting language like Markdown or Textile." --> 
 
@@ -40,9 +40,9 @@ In short, the Y-statement is as follows:
 
 The long form of it is as follows (extra section "because"):
 
-> In the context of `<use case/user story u>`,
-> facing `<concern c>`
-> we decided for `<option o>`
+> In the context of `<use case/user story>`,
+> facing `<concern>`,
+> we decided for `<option>`
 > and neglected `<other options>`,
 > to achieve `<system qualities/desired consequences>`,
 > accepting `<downside/undesired consequences>`,