Skip to content

Commit de3ee54

Browse files
ianthetechierhr323
authored andcommitted
Fix typo in cron schedule documentation (elastic#3494)
Title says it all. Simple typo fix.
1 parent 88539fd commit de3ee54

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -422,7 +422,7 @@ By default, the `yearly` schedule is evaluated in the UTC time zone. To use a di
422422
## {{watcher}} cron schedule [schedule-cron]
423423

424424

425-
Defines a [`schedule`](trigger-schedule.md) using a [cron expression](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#api-cron-expressions) that specifiues when to execute a watch.
425+
Defines a [`schedule`](trigger-schedule.md) using a [cron expression](elasticsearch://reference/elasticsearch/rest-apis/api-conventions.md#api-cron-expressions) that specifies when to execute a watch.
426426

427427
::::{tip}
428428
While cron expressions are powerful, a regularly occurring schedule is easier to configure with the other schedule types. If you must use a cron schedule, make sure you verify it with [`elasticsearch-croneval`](elasticsearch://reference/elasticsearch/command-line-tools/elasticsearch-croneval.md) .

0 commit comments

Comments
 (0)