From 1d853754d69caabeae48626da67729d28f421d75 Mon Sep 17 00:00:00 2001 From: Tim Date: Sat, 12 Jul 2025 16:32:56 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: SpecificProtagonist --- release-content/release-notes/event_split.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/release-content/release-notes/event_split.md b/release-content/release-notes/event_split.md index 9e7a2c8e87..4ef947f368 100644 --- a/release-content/release-notes/event_split.md +++ b/release-content/release-notes/event_split.md @@ -29,7 +29,7 @@ or an observer event with `EventReader`, leaving the user wondering why the even **Bevy 0.17** aims to solve this ambiguity by splitting the event traits into `Event`, `EntityEvent`, and `BufferedEvent`. - `Event`: A shared trait for observer events. -- `EntityEvent`: An observer `Event` that additionally supports targeting specific entities and propagating the event from one entity to another. +- `EntityEvent`: An `Event` that additionally supports targeting specific entities and propagating the event from one entity to another. - `BufferedEvent`: An event that supports usage with `EventReader` and `EventWriter` for pull-based event handling. ## Using Events @@ -92,7 +92,7 @@ let armor_piece = commands commands.trigger_targets(Damage { amount: 10.0 }, armor_piece); ``` -To allow an event to be used with the buffered API, you can derive `BufferedEvent`: +To allow an event to be used with the buffered API, you can instead derive `BufferedEvent`: ```rust #[derive(BufferedEvent)]