From 9f929d319578d1256cbee0773d4530f3eb4de226 Mon Sep 17 00:00:00 2001
From: Laube <75902023+LPAube@users.noreply.github.com>
Date: Fri, 17 Mar 2023 19:28:31 -0400
Subject: [PATCH] missing word: of (#5669)

---
 beta/src/content/learn/responding-to-events.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/beta/src/content/learn/responding-to-events.md b/beta/src/content/learn/responding-to-events.md
index 1f3fa923..782b6c0f 100644
--- a/beta/src/content/learn/responding-to-events.md
+++ b/beta/src/content/learn/responding-to-events.md
@@ -454,7 +454,7 @@ function Button({ onClick, children }) {
 }
 ```
 
-You could add more code to this handler before calling the parent `onClick` event handler, too. This pattern provides an *alternative* to propagation. It lets the child component handle the event, while also letting the parent component specify some additional behavior. Unlike propagation, it's not automatic. But the benefit of this pattern is that you can clearly follow the whole chain code that executes as a result of some event.
+You could add more code to this handler before calling the parent `onClick` event handler, too. This pattern provides an *alternative* to propagation. It lets the child component handle the event, while also letting the parent component specify some additional behavior. Unlike propagation, it's not automatic. But the benefit of this pattern is that you can clearly follow the whole chain of code that executes as a result of some event.
 
 If you rely on propagation and it's difficult to trace which handlers execute and why, try this approach instead.