diff --git a/src/client/general/event_queues.md b/src/client/general/event_queues.md
index 2dff202..e67b063 100644
--- a/src/client/general/event_queues.md
+++ b/src/client/general/event_queues.md
@@ -42,7 +42,7 @@ Let's explain the arguments of this method one by one:
    related to a mechanism of `wayland-client` that allows composition by delegating `Dispatch` implementations
    to fields of your state struct. This is detailed below.
 2. The second argument is a proxy representing the Wayland object with which this event is associated
-3. The first argument is an enum representing the content of the event. You are thus expected to match it
+3. The third argument is an enum representing the content of the event. You are thus expected to match it
    in order to process it.
 4. The fourth argument is a reference to the user data associated with this object.
 5. The fifth argument is a reference to the underlying [`Connection`]. Most of the time you will not need to
@@ -141,4 +141,4 @@ With all this context given, we are now ready to initialize our first app!
 [`Connection::new_event_queue()`]: https://docs.rs/wayland-client/latest/wayland_client/struct.Connection.html#method.new_event_queue
 [`EventQueue::handle()`]: https://docs.rs/wayland-client/0.30.2/wayland_client/struct.EventQueue.html#method.handle
 [`EventQueue::blocking_dispatch()`]: https://docs.rs/wayland-client/0.30.2/wayland_client/struct.EventQueue.html#method.blocking_dispatch
-[`delegate_dispatch!`]: https://docs.rs/wayland-client/0.30.2/wayland_client/macro.delegate_dispatch.html
\ No newline at end of file
+[`delegate_dispatch!`]: https://docs.rs/wayland-client/0.30.2/wayland_client/macro.delegate_dispatch.html