From eafb5c9fc3f4e3e628cf02fa3a4e5b4fa0ac1c8f Mon Sep 17 00:00:00 2001
From: wjhendry <90383531+wjhendry@users.noreply.github.com>
Date: Thu, 28 Nov 2024 13:32:32 +0000
Subject: [PATCH] Update index.mdx

---
 .../006_core-business-logic-event-handler/index.mdx             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/001_develop/02_server-capabilities/006_core-business-logic-event-handler/index.mdx b/docs/001_develop/02_server-capabilities/006_core-business-logic-event-handler/index.mdx
index 9a7df24719..beb3a36a2b 100644
--- a/docs/001_develop/02_server-capabilities/006_core-business-logic-event-handler/index.mdx
+++ b/docs/001_develop/02_server-capabilities/006_core-business-logic-event-handler/index.mdx
@@ -170,7 +170,7 @@ A successful event can also send data back to the client as part of an `ack`. A
 
 ### `nack`
 
-A nack statement signifies that an event failed. This is ypically sent during `onValidate` and sometimes during `onEvent`. 
+A nack statement signifies that an event failed. This is typically sent during `onValidate` and sometimes during `onEvent`. 
 
 It can take a string argument, which is the error message passed back to the client.