Update _docs/tutorials/core/programming_rcl_rclc/index.md

JanStaschulat · ralph-lange · web-flow · commit da5cbb8a699d · 2020-06-02T10:37:00.000Z
Co-authored-by: Ralph Lange &lt;ralph-lange@users.noreply.github.com&gt;
diff --git a/_docs/tutorials/core/programming_rcl_rclc/index.md b/_docs/tutorials/core/programming_rcl_rclc/index.md
@@ -510,7 +510,7 @@ typedef struct
   rcl_subscription_t * sub2;
 } sub_trigger_object_t;
 ```
-The executor for the publishers, shall publish when any of corresponding timers for the publishers is ready. That is the or-logic. You could also use the predefined  `rclc_executor_trigger_any` trigger condition, but this example shows, how you can write your own trigger conditions.
+The executor for the publishers shall publish when any of corresponding timers for the publishers is ready. That is the or-logic. You could also use the predefined  `rclc_executor_trigger_any` trigger condition, but this example shows how you can write your own trigger conditions.
 
 In principle the condition gets a list of handles, the length of this list, and the pre-defined condition type, in this case we expect `pub_trigger_object_t`. First, the parameter `obj` is cased to this type (`comm_obj`). Then, each element of the handle list is checked for new data (or a timer is ready) by evaluating the field `handles[i].data_available` and its handle pointer is compared to the pointer of the communicatoin object. If at least one timer is ready, then the trigger condition returns true.
 ```C
