summaryrefslogtreecommitdiff
path: root/doc/develop/event.rst
diff options
context:
space:
mode:
authorHugo Villeneuve <[email protected]>2023-04-25 09:46:45 -0400
committerTom Rini <[email protected]>2023-05-03 18:30:46 -0400
commited356ac9300b6efca238d7058bbe8395aa9ff8c6 (patch)
tree4122f91369f045657af35c6a98e181dae34b2dec /doc/develop/event.rst
parentb42303723a5feeec027126c7b7cb962fbbd9a513 (diff)
event: fix comments syntax error
Fix comments syntax error in event description: creasted -> created Signed-off-by: Hugo Villeneuve <[email protected]> Reviewed-by: Simon Glass <[email protected]>
Diffstat (limited to 'doc/develop/event.rst')
-rw-r--r--doc/develop/event.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/develop/event.rst b/doc/develop/event.rst
index 4ff59348371..e60cbf65691 100644
--- a/doc/develop/event.rst
+++ b/doc/develop/event.rst
@@ -12,7 +12,7 @@ Rather than using weak functions and direct calls across subsystemss, it is
often easier to use an event.
An event consists of a type (e.g. EVT_DM_POST_INIT) and some optional data,
-in `union event_data`. An event spy can be creasted to watch for events of a
+in `union event_data`. An event spy can be created to watch for events of a
particular type. When the event is created, it is sent to each spy in turn.