[E&A] Checks triggers.

Author: szabosteve

explore-analyze/alerts-cases/watcher/trigger-schedule.md

@@ -4,20 +4,16 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trigger-schedule.html
 ---
 
-
-
 # Schedule trigger [trigger-schedule]
 
-
 Schedule [triggers](trigger.md) define when the watch execution should start based on date and time. All times are in UTC time unless a timezone is explicitly specified in the schedule.
 
 {{watcher}} uses the system clock to determine the current time. To ensure schedules are triggered when expected, you should synchronize the clocks of all nodes in the cluster using a time service such as [NTP](http://www.ntp.org/).
 
-::::{note} 
+::::{note}
 {{watcher}} can’t correct for manual adjustments to the system clock. Be aware when making such changes that watch execution may be affected with watches being skipped or repeated if the adjustment covers their target execution time. This applies to changes made via NTP as well.
 ::::
 
-
 When specifying a timezone for a watch, keep in mind the effect daylight savings time transitions may have on the schedule, especially if the watch is scheduled to run during the transition. Here’s how {{watcher}} handles watches scheduled during discontinuities:
 
 ## Gap Transitions [_gap_transitions]
@@ -26,11 +22,8 @@ These occur when the clock moves forward, such as when daylight savings time sta
 
 Example: If a watch is scheduled to run daily at 1:30AM in the `Europe/London` time zone and the clock moves forward one hour from 1:00AM (GMT+0) to 2:00AM (GMT+1), the watch is executed at 2:30AM (GMT+1) which would have been 1:30AM before the transition. Subsequent executions happen at 1:30AM (GMT+1).
 
-
 ## Overlap Transitions [_overlap_transitions]
 
 These occur when the clock moves backward, such as when daylight savings time ends and cause certain hours or minutes to be repeated. If your watch is scheduled to run during an overlap transition, only the first occurrence of the time causes to the watch to execute with the second being skipped.
 
 Example: If a watch is scheduled to run at 1:30 AM and the clock moves backward one hour from 2:00AM to 1:00AM, the watch is executed at 1:30AM and the second occurrence after the change is skipped.
-
-

explore-analyze/alerts-cases/watcher/trigger.md

@@ -4,15 +4,8 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trigger.html
 ---
 
-
-
 # Triggers [trigger]
 
-
 Every watch must have a `trigger` that defines when the watch execution process should start. When you create a watch, its trigger is registered with the appropriate *Trigger Engine*. The trigger engine is responsible for evaluating the trigger and triggering the watch when needed.
 
 {{watcher}} is designed to support different types of triggers, but only time-based [`schedule`](trigger-schedule.md) triggers are currently available.
-
-
-
-