docs: update references to RFC 9457 and streamline external links

- Updated all remaining RFC 7807 mentions to RFC 9457 across adoption guides and index.md
- Simplified external links in index.md, keeping only canonical Medium article and GitHub repository
- Ensured consistent canonical reference alignment for SEO and documentation clarity

Author: bsayli

docs/adoption/client-side-adoption-pom.md

@@ -245,4 +245,4 @@ cleanly and consistently across builds.
 
 * Resolve templates dynamically from the current OpenAPI Generator version.
 * Apply your overlay Mustache templates automatically.
-* Generate **RFC 7807‑aware**, `data + meta` aligned clients ready for production use.
+* Generate **RFC 9457‑aware**, `data + meta` aligned clients ready for production use.

docs/adoption/client-side-adoption.md

@@ -8,7 +8,7 @@ nav_order: 2
 # Client‑Side Integration Guide
 
 This guide describes how to integrate the **generics‑aware OpenAPI client** into your own project, aligned with the
-new `{ data, meta }` response structure and RFC 7807 `ProblemDetail` error model introduced in the updated
+new `{ data, meta }` response structure and RFC 9457 `ProblemDetail` error model introduced in the updated
 `customer-service` / `customer-service-client` architecture.
 
 ---
@@ -17,7 +17,7 @@ new `{ data, meta }` response structure and RFC 7807 `ProblemDetail` error model
 
 * Generate thin, **type‑safe wrappers** extending `ServiceClientResponse<T>` instead of duplicating envelopes.
 * Support **nested generics** such as `ServiceClientResponse<Page<CustomerDto>>`.
-* Decode non‑2xx responses into **RFC 7807 ProblemDetail** and raise `ClientProblemException`.
+* Decode non‑2xx responses into **RFC 9457 ProblemDetail** and raise `ClientProblemException`.
 * Allow seamless injection into Spring Boot apps using a pooled `RestClient`.
 
 ---

docs/adoption/server-side-adoption.md

@@ -270,7 +270,7 @@ public class AutoWrapperSchemaCustomizer {
 
 ---
 
-## 6️⃣ Global Problem Responses (RFC 7807)
+## 6️⃣ Global Problem Responses (RFC 9457)
 
 Add automatic `ProblemDetail` registration and standard error responses for all operations.
 
@@ -304,7 +304,7 @@ public class GlobalErrorResponsesCustomizer {
 
 ---
 
-### Optional: Problem extensions (RFC7807)
+### Optional: Problem extensions (RFC 9457)
 
 Some projects enrich `ProblemDetail` with structured error data inside `extensions.errors`.
 These simple records provide a reusable base for that purpose.

docs/index.md

@@ -40,7 +40,7 @@ ServiceClientResponse<Page<CustomerDto>>
 
 * **Unified response model:** `{ data, meta }` replaces legacy status/message/errors structure.
 * **Nested generics support:** Handles both `ServiceResponse<T>` and `ServiceResponse<Page<T>>`.
-* **RFC 7807 compliant errors:** All non-2xx responses are mapped into `ProblemDetail` and thrown as
+* **RFC 9457 compliant errors:** All non-2xx responses are mapped into `ProblemDetail` and thrown as
   `ClientProblemException`.
 * **Generics-aware OpenAPI Generator overlay:** Mustache templates produce thin, type-safe wrappers.
 * **Simple integration:** Works with any Spring Boot service exposing `/v3/api-docs.yaml`.
@@ -128,7 +128,6 @@ Instant serverTime = response.getMeta().serverTime();
   <ul>
     <li>🌐 <a href="https://github.com/bsayli/spring-boot-openapi-generics-clients" target="_blank" rel="noopener">GitHub Repository</a></li>
     <li>📘 <a href="https://medium.com/@baris.sayli/type-safe-generic-api-responses-with-spring-boot-3-4-openapi-generator-and-custom-templates-ccd93405fb04" target="_blank" rel="noopener">Medium — We Made OpenAPI Generator Think in Generics</a></li>
-    <li>💬 <a href="https://dev.to/barissayli/spring-boot-openapi-generator-type-safe-generic-api-clients-without-boilerplate-3a8f" target="_blank" rel="noopener">Dev.to — We Made OpenAPI Generator Think in Generics</a></li>
   </ul>
 </div>