From 5a020093f5bfb59f3bb683ff28686f97b6d7b9c8 Mon Sep 17 00:00:00 2001 From: Ray Droplet Date: Mon, 27 Jul 2026 05:59:53 +0000 Subject: [PATCH] Fix typo in .rules (#61693) ## Objective A phrase in `.rules` was missing a verb. ## Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content adheres to Zed's UI standards ([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) and [icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md) guidelines) - [ ] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable --- Release Notes: - N/A --- .rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.rules b/.rules index 4b4eb08c368..f4acf4d19b2 100644 --- a/.rules +++ b/.rules @@ -117,7 +117,7 @@ Often event handlers will want to update the entity that's in the current `Conte Actions are dispatched via user keyboard interaction or in code via `window.dispatch_action(SomeAction.boxed_clone(), cx)` or `focus_handle.dispatch_action(&SomeAction, window, cx)`. -Actions with no data defined with the `actions!(some_namespace, [SomeAction, AnotherAction])` macro call. Otherwise the `Action` derive macro is used. Doc comments on actions are displayed to the user. +Actions with no data are defined with the `actions!(some_namespace, [SomeAction, AnotherAction])` macro call. Otherwise the `Action` derive macro is used. Doc comments on actions are displayed to the user. Action handlers can be registered on an element via the event handler `.on_action(|action, window, cx| ...)`. Like other event handlers, this is often used with `cx.listener`.