diff --git a/api-guidelines/async/semantics/event-structure/rules/should-send-durable-event-ids.md b/api-guidelines/async/semantics/event-structure/rules/should-send-durable-event-ids.md
index 5a231d67..85c7d6d1 100644
--- a/api-guidelines/async/semantics/event-structure/rules/should-send-durable-event-ids.md
+++ b/api-guidelines/async/semantics/event-structure/rules/should-send-durable-event-ids.md
@@ -1,5 +1,5 @@
 ---
-id: R000058
+id: R000082
 ---
 
 # SHOULD send durable event IDs 
diff --git a/api-guidelines/rest/http/headers/rules/must-forward-test-header.md b/api-guidelines/rest/http/headers/rules/must-forward-test-header.md
index 369ec8b5..27c6a6f0 100644
--- a/api-guidelines/rest/http/headers/rules/must-forward-test-header.md
+++ b/api-guidelines/rest/http/headers/rules/must-forward-test-header.md
@@ -4,6 +4,6 @@ id: R000081
 
 # MUST forward `Test` header
 
-An API provider or consumer must include the [`Test` header](./may-use-header.md) from the initial interaction in all subsequent requests and asynchronous events if the original API request or response is marked with a Test header.
+An API provider or consumer must include the [`Test` header](./may-use-test-header.md) from the initial interaction in all subsequent requests and asynchronous events if the original API request or response is marked with a Test header.
 
 This behavior enables downstream API providers and consumers to choose whether they would like to participate in the test.
diff --git a/changes/changelog.md b/changes/changelog.md
index acc8c2a3..af961901 100644
--- a/changes/changelog.md
+++ b/changes/changelog.md
@@ -2,40 +2,40 @@
 
 <!--CHANGELOG-MARKER-->
 ## 2024-10-07
-### New
-
-- SHOULD send durable event IDs [R000058](https://api.otto.de/portal/guidelines/r000058)
+### New
+
+- SHOULD send durable event IDs [R000082](https://api.otto.de/portal/guidelines/r000082)
 
 ## 2024-09-18
-### New
-
-- MAY use Test header [R000080](api-guidelines/rest/http/headers/rules/may-use-test-header.md)
-- MUST forward Test header [R000081](api-guidelines/rest/http/headers/rules/must-forward-test-header.md)
+### New
+
+- MAY use `Test` header [R000080](https://api.otto.de/portal/guidelines/r000080)
+- MUST forward `Test` header [R000081](https://api.otto.de/portal/guidelines/r000081)
 
 ## 2024-03-06
-### Update
-
+### Update
+
 - Fixed the link to the date rule in "MUST use common data formats" [R100071](https://api.otto.de/portal/guidelines/r100071).
 
 ## 2024-02-05
-### Removal
-
-The following rules have been removed as they contained consumer-facing content. This content has been included in the API Portal in the REST API sections "Status codes", "Headers" "Preview", and "Deprecation" respectively.
-
-- MUST NOT rely on API components marked as preview
-- MUST NOT not start using deprecated APIs
-- MUST accept undocumented status codes
-- MUST follow redirection
+### Removal
+
+The following rules have been removed as they contained consumer-facing content. This content has been included in the API Portal in the REST API sections "Status codes", "Headers" "Preview", and "Deprecation" respectively.
+
+- MUST NOT rely on API components marked as preview
+- MUST NOT not start using deprecated APIs
+- MUST accept undocumented status codes
+- MUST follow redirection
 - SHOULD honor available ETag header on subsequent modifications
 
 ## 2024-01-31
-### Update
-
+### Update
+
 - Replaced the dead link to `serialized.io/ddd/domain-event` with its internet archive counterpart.
 
 ## 2023-09-18
-### Update
-
+### Update
+
 - Added uri-list format to rule "MUST use common data formats [R100071](https://api.otto.de/portal/guidelines/r100071)".
 
 ## 2023-08-29