📒 docs: restore SSE middleware wording

Agent-Logs-Url: https://github.com/gofiber/fiber/sessions/e15ef545-45b5-4ca4-8f1a-0cf1bcbe0198

Co-authored-by: gaby <835733+gaby@users.noreply.github.com>

Author: Copilot

docs/middleware/sse.md

@@ -4,7 +4,7 @@ id: sse
 
 # SSE
 
-The SSE handler provides the transport pieces for Server-Sent Events: response headers, event formatting, flushing, heartbeat comments, and disconnect detection through `Flush` errors.
+The SSE middleware provides the transport pieces for Server-Sent Events: response headers, event formatting, flushing, heartbeat comments, and disconnect detection through `Flush` errors.
 
 It intentionally does not include a hub, topics, authentication, replay storage, metrics, or external pub/sub bridges. Those are application concerns that can be composed around the stream handler.
 

docs/whats_new.md

@@ -1683,7 +1683,7 @@ For more details on these changes and migration instructions, check the [Session
 
 ### SSE
 
-Fiber now includes an [SSE handler](./middleware/sse.md) for Server-Sent Events. It handles native
+Fiber now includes an [SSE middleware](./middleware/sse.md) for Server-Sent Events. It handles native
 `SendStreamWriter` setup, SSE response headers, event formatting, flushing, heartbeat comments, and
 disconnect detection through flush errors while leaving application-level hubs, topics, replay stores, and
 pub/sub bridges to user code or recipes.