From 33559b932670e3df31a3c64b0f34c1d75a1ef7d4 Mon Sep 17 00:00:00 2001
From: pikammmmm <124257101+pikammmmm@users.noreply.github.com>
Date: Fri, 1 May 2026 22:29:46 +0200
Subject: [PATCH] Fix `behaivor` -> `behavior` typo in subscribers.md

---
 Documentation/basics/subscribers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/basics/subscribers.md b/Documentation/basics/subscribers.md
index 5b18ab792..abacba77d 100644
--- a/Documentation/basics/subscribers.md
+++ b/Documentation/basics/subscribers.md
@@ -75,7 +75,7 @@ By default any exceptions thrown by a subscriber are **swallowed**
 by EventFlow after it has been logged as an error. Depending on the
 application this might be the preferred behavior, but in some cases
 it isn't. If a subscriber exception should be thrown, and thus allowing
-them to be caught in e.g. command handlers, the behaivor can be disabled
+them to be caught in e.g. command handlers, the behavior can be disabled
 by setting the `ThrowSubscriberExceptions` to `true` when configuring EventFlow.
 
 ## Asynchronous subscribers