diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0ff2174..c8ee1e7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,6 +11,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
- Put the content of `status:` in quotes to tell YAML it's a string. [#91](https://github.com/adr/madr/issues/91)
- Renamed "Validation" to "Confirmation" and put it as sub element of "Decision Outcome". [#87](https://github.com/adr/madr/pull/87)
+- Rename template name "Markdown Any Decision Record" back to "Markdown Architectural Decision Record"
+- Rename `0000-use-markdown-any-decision-records.md` to `0000-use-madr.md`.
## [3.0.0] – 2022-10-09
diff --git a/README.md b/README.md
index d27c68d..87db15f 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
-# Markdown Any Decision Records
+# Markdown Architectural Decision Records
-> "Markdown Any Decision Records" (MADR) `[ˈmæɾɚ]` – decisions that [matter `[ˈmæɾɚ]`](https://en.wiktionary.org/wiki/matter#Pronunciation).
+> "Markdown Architectural Decision Records" (MADR) `[ˈmæɾɚ]` – decisions that [matter `[ˈmæɾɚ]`](https://en.wiktionary.org/wiki/matter#Pronunciation).
For user documentation, please head to .
@@ -62,8 +62,8 @@ In case you get errors regarding `Gemfile.lock`, just delete `Gemfile.lock` and
5. Update `CHANGELOG.md`.
6. Check that the YAML front matter in `docs/decisions/adr-template.md` is kept.
7. Copy `.markdownlint.yml` to `template/.markdownlint.yml`
-8. Adapt the version reference in `template/0000-use-markdown-any-decision-records.md`.
-9. Copy `template/0000-use-markdown-any-decision-records.md` to `docs/decisions/0000-use-markdown-any-decision-records.md`.
+8. Adapt the version reference in `template/0000-use-madr.md`.
+9. Copy `template/0000-use-madr.md` to `docs/decisions/0000-use-madr.md`.
10. Update `package.json`
11. Publish to [npmjs](https://www.npmjs.com/package/madr) using [release-it](https://www.npmjs.com/package/release-it) (do not create a release on GitHub). This also does a commit.
12. Create GitHub release using [github-release-from-changelog](https://www.npmjs.com/package/github-release-from-changelog).
diff --git a/docs/_config.yml b/docs/_config.yml
index 994bf77..8abbdd4 100644
--- a/docs/_config.yml
+++ b/docs/_config.yml
@@ -1,5 +1,5 @@
title: "MADR"
-desription: Markdown Any Decisions Records
+desription: Markdown Architectural Decisions Records
repository: adr/madr
theme: just-the-docs
color_scheme: light
diff --git a/docs/decisions/0000-use-markdown-any-decision-records.md b/docs/decisions/0000-use-madr.md
similarity index 77%
rename from docs/decisions/0000-use-markdown-any-decision-records.md
rename to docs/decisions/0000-use-madr.md
index df5c4f9..106f93b 100644
--- a/docs/decisions/0000-use-markdown-any-decision-records.md
+++ b/docs/decisions/0000-use-madr.md
@@ -2,16 +2,16 @@
parent: Decisions
nav_order: 0
---
-# Use Markdown Any Decision Records
+# Use Markdown Architectural Decision Records
## Context and Problem Statement
-We want to record any decisions made in this project independent whether decisions concern the architecture ("architectural decision record"), the code, or other fields.
+We want to record architectural decisions made in this project independent whether decisions concern the architecture ("architectural decision record"), the code, or other fields.
Which format and structure should these records follow?
## Considered Options
-* [MADR](https://adr.github.io/madr/) 3.0.0 – The Markdown Any Decision Records
+* [MADR](https://adr.github.io/madr/) 4.0.0 – The Markdown Architectural Decision Records
* [Michael Nygard's template](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions) – The first incarnation of the term "ADR"
* [Sustainable Architectural Decisions](https://www.infoq.com/articles/sustainable-architectural-design-decisions) – The Y-Statements
* Other templates listed at
diff --git a/package.json b/package.json
index 0ff48aa..1d005c7 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "madr",
- "description": "Markdown Any Decision Records",
+ "description": "Markdown Architectural Decision Records",
"keywords": [
"adr",
"decision record",
diff --git a/template/0000-use-markdown-any-decision-records.md b/template/0000-use-markdown-any-decision-records.md
index 0edc15d..914b1e9 100644
--- a/template/0000-use-markdown-any-decision-records.md
+++ b/template/0000-use-markdown-any-decision-records.md
@@ -1,13 +1,13 @@
-# Use Markdown Any Decision Records
+# Use Markdown Architectural Decision Records
## Context and Problem Statement
-We want to record any decisions made in this project independent whether decisions concern the architecture ("architectural decision record"), the code, or other fields.
+We want to record architectural decisions made in this project independent whether decisions concern the architecture ("architectural decision record"), the code, or other fields.
Which format and structure should these records follow?
## Considered Options
-* [MADR](https://adr.github.io/madr/) 3.0.0 – The Markdown Any Decision Records
+* [MADR](https://adr.github.io/madr/) 4.0.0 – The Markdown Architectural Decision Records
* [Michael Nygard's template](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions) – The first incarnation of the term "ADR"
* [Sustainable Architectural Decisions](https://www.infoq.com/articles/sustainable-architectural-design-decisions) – The Y-Statements
* Other templates listed at
@@ -15,7 +15,7 @@ Which format and structure should these records follow?
## Decision Outcome
-Chosen option: "MADR 3.0.0", because
+Chosen option: "MADR 4.0.0", because
* Implicit assumptions should be made explicit.
Design documentation is important to enable people understanding the decisions later on.