Update _docs/concepts/client_library/real-time_executor/index.md

JanStaschulat · ralph-lange · ralph-lange · commit 66c0e8e705ce · 2020-02-07T08:14:12.000+01:00
Co-Authored-By: Ralph Lange &lt;ralph-lange@users.noreply.github.com&gt;
diff --git a/_docs/concepts/client_library/real-time_executor/index.md b/_docs/concepts/client_library/real-time_executor/index.md
@@ -261,7 +261,7 @@ The API of the RCLC-Executor can be divided in two phases: Configuration and Run
 During the configuration phase, the user shall define:
 - the total number of callbacks
 - the sequence of the callbacks
-- trigger contition (optional, default: ANY)
+- trigger condition (optional, default: ANY)
 - data communcation semantics (optional, default ROS2)
 
 As the Executor is intended for embedded controllers, dynamic memory management is crucial. Therefore at initialization of the RCLC-Executor, the user defines the total number of callbacks. The necessary dynamic memory will be allocated only in this phase and no more memory in the running phase. This makes this Executor static in the sense, that during runtime no additional callbacks can be added.
