diff --git a/docs/source/developers/emitting-events.md b/docs/source/developers/emitting-events.md
index c8f357089e..117af25204 100644
--- a/docs/source/developers/emitting-events.md
+++ b/docs/source/developers/emitting-events.md
@@ -43,7 +43,7 @@ def _load_jupyter_server_extension(serverapp: ServerApp):
 Once the event schema is registered, it is ready to be emitted. Note that the core `event_logger` is included in Jupyter Server's tornado settings and listed as a property of `JupyterHandler` API.
 
 :::{attention}
-While you can (technically) create your own instance of an EventLogger from your extension, users/operators will likely only collect events from the instance created by Jupyter Server's `ServerApp`. If you would to provide your own instance, be sure to clearly document how to configure your extension to collect your events.
+While you can (technically) create your own instance of an `EventLogger` from your extension, users/operators will likely only collect events from the instance created by Jupyter Server's `ServerApp`. If you would like to provide your own instance, be sure to clearly document how to configure your extension to collect your events.
 :::
 
 As an example, you can emit an event from a custom request handler by calling `self.event_logger.emit(...)`: