Fix broken link and update the description (#2905)

### Motivation and Context

Fix broken link the ADR README


### Contribution Checklist

- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄

docs/decisions/0001-madr-architecture-decisions.md

@@ -15,7 +15,7 @@ We need a way to keep the implementations aligned with regard to key architectur
 semantic function configuration (config.json) and when this change is agreed it must be reflected in all of the Semantic Kernel implementations.
 
 MADR is a lean template to capture any decisions in a structured way. The template originated from capturing architectural decisions and developed to a template allowing to capture any decisions taken.
-For more information [see](https://adr.github.io/madr/)
+For more information [see](https://adr.github.io/)
 
 <!-- This is an optional element. Feel free to remove. -->
 ## Decision Drivers

docs/decisions/README.md

@@ -1,7 +1,8 @@
-# Markdown Any Decision Records
+# Architectural Decision Records (ADRs)
 
-MADR is a lean template to capture any decisions in a structured way. The template originated from capturing architectural decisions and developed to a template allowing to capture any decisions taken.
-For more information [see](https://adr.github.io/madr/)
+An Architectural Decision (AD) is a justified software design choice that addresses a functional or non-functional requirement that is architecturally significant. An Architectural Decision Record (ADR) captures a single AD and its rationale.
+
+For more information [see](https://adr.github.io/)
 
 ## How are we using ADR's to track technical decisions?