From c6af25655612999f501037631b4824f21d5c37f4 Mon Sep 17 00:00:00 2001 From: Nicolas Hansse Date: Fri, 5 Dec 2025 15:37:08 +0100 Subject: [PATCH] fix(error-handling): typo --- docs/patterns/error-handling.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/patterns/error-handling.md b/docs/patterns/error-handling.md index 7ad6e6a2..1d79b224 100644 --- a/docs/patterns/error-handling.md +++ b/docs/patterns/error-handling.md @@ -286,8 +286,8 @@ But for `status` it can be a little bit confusing, since it can be used both as It could either be **return** or **throw** based on your specific needs. -- If an `status` is **throw**, it will be caught by `onError` middleware. -- If an `status` is **return**, it will be **NOT** caught by `onError` middleware. +- If a `status` is **throw**, it will be caught by `onError` middleware. +- If a `status` is **return**, it will be **NOT** caught by `onError` middleware. See the following code: