Update image name

Author: olaru

public/md-articles/dotkernel-api/what-production-ready-means-for-dotkernel-api.md

@@ -12,7 +12,9 @@ language: "en"
 
 ## TL;DR
 
-Dotkernel API ships a complete, tested application layer — pipeline, OAuth2 auth, RBAC, validation, error responses, OpenAPI. It does not ship the infrastructure layer around it: rate limiting, an API gateway, federated identity, error tracking, health checks, or caching/background jobs. Those are deliberate boundaries, not gaps, and the linked documentation page lists each one with what to configure before going live.
+Dotkernel API ships a complete, tested application layer — pipeline, OAuth2 auth, RBAC, validation, error responses, OpenAPI.
+It does not ship the infrastructure layer around it: rate limiting, an API gateway, federated identity, error tracking, health checks, or caching/background jobs.
+Those are deliberate boundaries, not gaps, and the linked documentation page lists each one with what to configure before going live.
 
 Dotkernel API describes itself as production ready, and it is — but the phrase covers less ground than most people assume, and the difference is worth naming.
 

public/opengraph/article/dotkernel-production-ready-twitter-card.png

@@ -2794,7 +2794,7 @@
                 },
                 "isObsolete": false,
                 "isTwig": false,
-                "opengraph_img": "/opengraph/article/dotkernel-production-ready-twitter-card.png",
+                "opengraph_img": "/opengraph/article/twitter-card-dotkernel-api-production-ready.png",
                 "excerpt": "Dotkernel API describes itself as production ready. Here is exactly what that covers — and the infrastructure layer (rate limiting, gateway, federated identity, error tracking, health checks, caching) that stays yours to add before launch.",
                 "tl_dr": "Dotkernel API ships a complete, tested application layer — pipeline, OAuth2 auth, RBAC, validation, error responses, OpenAPI. It does not ship the infrastructure layer around it: rate limiting, an API gateway, federated identity, error tracking, health checks, or caching/background jobs. Those are deliberate boundaries, not gaps, and the linked documentation page lists each one with what to configure before going live.",
                 "tags": []