@@ -139,6 +139,7 @@
     "ILIKE",
     "IMDS",
     "incentivized",
+    "INCRBY",
     "inotify",
     "instrumenta",
     "interrobang",
@@ -297,6 +298,7 @@
     "registrator",
     "Rego",
     "Rekor",
+    "replcia",
     "repost",
     "reposts",
     "RGAA",
 
@@ -9,8 +9,8 @@ tags: ["reliability-and-testing", "prometheus"]
 featured: true
 ---
 
-import alertOutcomeDiagram from './alert-outcome-tracking-for-health-metrics.jpg'
-import decisionTreeDiagram from './decision-tree-for-page-vs-notification-classification.jpg'
+import alertOutcomeDiagram from './diagrams/alert-outcome-tracking-for-health-metrics.jpg'
+import decisionTreeDiagram from './diagrams/decision-tree-for-page-vs-notification-classification.jpg'
 
 *[DataDog]: Observability platform
 *[MTTA]: Mean Time To Acknowledge
 
@@ -9,8 +9,6 @@ tags: ["apis-and-gateways", "aws", "typescript"]
 featured: true
 ---
 
-import Callout from '@components/Callout/index.astro'
-
 *[API]: Application Programming Interface
 
 I once inherited an API version marked "deprecated" two years prior that still handled 30% of production traffic. Three enterprise customers had never migrated. Two of them had contracts that technically guaranteed API availability. The third was our largest account, and nobody wanted to be the engineer who broke their integration.
 
@@ -9,8 +9,8 @@ tags: ["apis-and-gateways", "aws", "typescript"]
 featured: true
 ---
 
-import ApiDeprecationLifecycle from './api-deprecation-lifecycle-with-parallel-migration-support-track.jpg'
-import ConsumerMigrationStatus from './consumer-migration-status-breakdown-for-deprecation-tracking.jpg'
+import ApiDeprecationLifecycle from './diagrams/api-deprecation-lifecycle-with-parallel-migration-support-track.jpg'
+import ConsumerMigrationStatus from './diagrams/consumer-migration-status-breakdown-for-deprecation-tracking.jpg'
 
 *[SDK]: Software Development Kit
 *[RFC]: Request for Comments