From 281490804ec386d6d239c38372581cbc12af9948 Mon Sep 17 00:00:00 2001 From: Morgan Roderick Date: Fri, 3 Apr 2026 23:41:35 +0200 Subject: [PATCH 1/2] fix(specs): explain interpretation nature, fix broken prev link --- docs/learn/spec.md | 2 +- docs/specs/index.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/learn/spec.md b/docs/learn/spec.md index 100fe99..c2a1681 100644 --- a/docs/learn/spec.md +++ b/docs/learn/spec.md @@ -57,4 +57,4 @@ The spec leaves some things to the application layer: ✅ **Full compliance** with draft-ietf-httpapi-idempotency-key-header-07 -All MUST and SHOULD requirements are implemented. The library gives you the flexibility to choose which optional features to enable based on your API's needs. +All MUST and SHOULD requirements are implemented. diff --git a/docs/specs/index.md b/docs/specs/index.md index e17182a..ebf40ff 100644 --- a/docs/specs/index.md +++ b/docs/specs/index.md @@ -1,13 +1,13 @@ --- prev: text: "Why Idempotency" - link: "/why-idempotency" + link: "/learn/why" next: false --- # Cucumber Specifications -RFC 7807-compliant specifications for idempotency middleware implementations. +These Cucumber specifications represent idempot.dev's interpretation and opinions on how [draft-ietf-httpapi-idempotency-key-header-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header-07) should be implemented. While the IETF draft defines the requirements, these specs codify specific implementation choices that ensure consistency across all idempot.dev projects. ## Overview From b221530731937215a4845cbade590f46399b9537 Mon Sep 17 00:00:00 2001 From: Morgan Roderick Date: Fri, 3 Apr 2026 23:45:23 +0200 Subject: [PATCH 2/2] style(specs): improve intro prose using Elements of Style --- docs/specs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/specs/index.md b/docs/specs/index.md index ebf40ff..4db6d0a 100644 --- a/docs/specs/index.md +++ b/docs/specs/index.md @@ -7,7 +7,7 @@ next: false # Cucumber Specifications -These Cucumber specifications represent idempot.dev's interpretation and opinions on how [draft-ietf-httpapi-idempotency-key-header-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header-07) should be implemented. While the IETF draft defines the requirements, these specs codify specific implementation choices that ensure consistency across all idempot.dev projects. +These Cucumber specifications codify idempot.dev's interpretation of [draft-ietf-httpapi-idempotency-key-header-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header-07). The IETF draft defines the requirements; these specs translate them into implementation choices shared by all idempot.dev projects. ## Overview