chore: fix diagrams

Author: dreamorosi

docs/features/event-handler/rest.md

@@ -223,9 +223,8 @@ incoming request and your route handler. They provide a way to implement cross-c
 concerns like authentication, logging, validation, and response transformation without
 cluttering your route handlers.
 
-Each middleware function receives the following arguments:
+Each middleware function receives two arguments:
 
-* **params** - Route parameters extracted from the URL path
 * **reqCtx** - Request context containing the event, Lambda context, request, and response objects
 * **next** - A function to pass control to the next middleware in the chain
 

examples/snippets/event-handler/rest/diagrams/middleware_early_return.mermaid

@@ -7,9 +7,9 @@ sequenceDiagram
     participant Handler as Route Handler
 
     Request->>Router: Incoming Request
-    Router->>M1: Execute (params, reqCtx, next)
+    Router->>M1: Execute ({ reqCtx, next })
     Note over M1: Pre-processing
-    M1->>M2: Call next()
+    M1->>M2: Call await next()
     Note over M2: Pre-processing
     M2->>M2: Return Response (early return)
     Note over M2: Post-processing

examples/snippets/event-handler/rest/diagrams/middleware_error_handling.mermaid

@@ -7,9 +7,9 @@ sequenceDiagram
     participant Handler as Route Handler
 
     Request->>Router: Incoming Request
-    Router->>M1: Execute (params, reqCtx, next)
+    Router->>M1: Execute ({ reqCtx, next })
     Note over M1: Pre-processing
-    M1->>M2: Call next()
+    M1->>M2: Call await next()
     Note over M2: Throws Error
     M2-->>M1: Error propagated
     M1-->>Router: Error propagated

examples/snippets/event-handler/rest/diagrams/middleware_execution_order.mermaid

@@ -6,11 +6,11 @@ sequenceDiagram
     participant Handler as Route Handler
 
     Request->>Router: Incoming Request
-    Router->>GM: Execute (params, reqCtx, next)
+    Router->>GM: Execute ({ reqCtx, next })
     Note over GM: Pre-processing
-    GM->>RM: Call next()
+    GM->>RM: Call await next()
     Note over RM: Pre-processing
-    RM->>Handler: Call next()
+    RM->>Handler: Call await next()
     Note over Handler: Execute handler
     Handler-->>RM: Return
     Note over RM: Post-processing

examples/snippets/event-handler/rest/diagrams/middleware_handled_error.mermaid

@@ -6,12 +6,12 @@ sequenceDiagram
     participant Handler as Route Handler
 
     Request->>Router: Incoming Request
-    Router->>M1: Execute (params, reqCtx, next)
+    Router->>M1: Execute ({ reqCtx, next })
     Note over M1: Pre-processing
-    M1->>M2: Call next()
+    M1->>M2: Call await next()
     Note over M2: Error thrown & caught
     Note over M2: Handle error gracefully
-    M2->>Handler: Call next()
+    M2->>Handler: Call await next()
     Note over Handler: Execute handler
     Handler-->>M2: Return
     Note over M2: Post-processing

examples/snippets/event-handler/rest/diagrams/middleware_throwing_error.mermaid

@@ -7,9 +7,9 @@ sequenceDiagram
     participant Handler as Route Handler
 
     Request->>Router: Incoming Request
-    Router->>M1: Execute (params, reqCtx, next)
+    Router->>M1: Execute ({ reqCtx, next })
     Note over M1: Pre-processing
-    M1->>M2: Call next()
+    M1->>M2: Call await next()
     Note over M2: Intentionally throws error
     M2-->>M1: Error propagated
     M1-->>Router: Error propagated