From e5536cdcd25318dba083ab8b3cd9fd6704aaae24 Mon Sep 17 00:00:00 2001
From: Tomoya Fujita <tomoya.fujita825@gmail.com>
Date: Wed, 15 Jul 2026 11:15:41 +0900
Subject: [PATCH] remove EventsExecutor explanation.

Signed-off-by: Tomoya Fujita <tomoya.fujita825@gmail.com>
---
 .../client-libraries/About-Executors/About-Executors.rst    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/source/ROS-Framework/client-libraries/About-Executors/About-Executors.rst b/source/ROS-Framework/client-libraries/About-Executors/About-Executors.rst
index 4d405147ce6..17663ee09b5 100644
--- a/source/ROS-Framework/client-libraries/About-Executors/About-Executors.rst
+++ b/source/ROS-Framework/client-libraries/About-Executors/About-Executors.rst
@@ -111,9 +111,9 @@ Available in Lyrical Luth onward, the `EventsCBGExecutor <https://github.com/ros
 Instead of the wait sets, it utilizes a *first-in first-out events queue* to process ready events.
 It builds off the core idea that you don't pay for what you're not using, because rather than polling for changes on entities, an entity will enqueue an event to be processed *only when it becomes ready*.
 
-This new executor improves on its predecessor, the ``rclcpp::experimental::EventsExecutor``, by adding support for multiple sources of ROS time (including sim time), addressing `issues with slow running timers leading to a burst of timer events <https://github.com/ros2/rclcpp/issues/2771>`_, and multithreading support.
-Therefore, the new executor can also act as a drop-in replacement for the ``MultiThreadedExecutor``, as it will also create a configurable number of worker threads to process ready events.
-In single-threaded mode, the ``EventsCBGExecutor`` results in less context switching and `exhibits similar performance characteristics to its predecessor <https://discourse.openrobotics.org/t/ros2-state-of-the-events-executors-benchmark-comparison-between-rclcpp-eventsexecutor-and-cm-executors-eventscbgexecutor/50337>`_.
+This executor supports multiple sources of ROS time (including sim time), addresses `issues with slow running timers leading to a burst of timer events <https://github.com/ros2/rclcpp/issues/2771>`_, and provides multithreading support.
+Therefore, the executor can also act as a drop-in replacement for the ``MultiThreadedExecutor``, as it will also create a configurable number of worker threads to process ready events.
+In single-threaded mode, the ``EventsCBGExecutor`` results in less context switching and `exhibits strong performance characteristics <https://discourse.openrobotics.org/t/ros2-state-of-the-events-executors-benchmark-comparison-between-rclcpp-eventsexecutor-and-cm-executors-eventscbgexecutor/50337>`_.
 
 Note: Currently, there is no limit to the number of events that can be added to the queue.
 This means that if the process is overloaded and starts slowing down, the number of ready entities inside the queue can grow unbounded.