From ef78a04263fe7e33ee48b17eb36d34815ee6420c Mon Sep 17 00:00:00 2001
From: gharbi-mohamed-dev
 <133573945+gharbi-mohamed-dev@users.noreply.github.com>
Date: Wed, 8 Jan 2025 09:07:43 +0100
Subject: [PATCH] docs: fix typo (#10870)

---
 .../fundamentals/events-and-subscribers/emit-event/page.mdx     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/apps/book/app/learn/fundamentals/events-and-subscribers/emit-event/page.mdx b/www/apps/book/app/learn/fundamentals/events-and-subscribers/emit-event/page.mdx
index 657c53d27c..b9fffd3c68 100644
--- a/www/apps/book/app/learn/fundamentals/events-and-subscribers/emit-event/page.mdx
+++ b/www/apps/book/app/learn/fundamentals/events-and-subscribers/emit-event/page.mdx
@@ -14,7 +14,7 @@ In your customization, you can emit an event, then listen to it in a subscriber
 
 There are two types of events in Medusa:
 
-1. Worflow event: an event that's emitted in a workflow after a commerce feature is performed. For example, Medusa emits the `order.placed` event after a cart is completed.
+1. Workflow event: an event that's emitted in a workflow after a commerce feature is performed. For example, Medusa emits the `order.placed` event after a cart is completed.
 2. Service event: an event that's emitted to track, trace, or debug processes under the hood. For example, you can emit an event with an audit trail.
 
 ### Which Event Type to Use?