From c90563e22df2209b31704e52297b81c2b8047790 Mon Sep 17 00:00:00 2001 From: Ian Wagner Date: Thu, 16 Oct 2025 10:42:29 +0900 Subject: [PATCH] Fix typo in cron schedule documentation --- explore-analyze/alerts-cases/watcher/schedule-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explore-analyze/alerts-cases/watcher/schedule-types.md b/explore-analyze/alerts-cases/watcher/schedule-types.md index 0f4f91f4d5..c4ef118eb9 100644 --- a/explore-analyze/alerts-cases/watcher/schedule-types.md +++ b/explore-analyze/alerts-cases/watcher/schedule-types.md @@ -422,7 +422,7 @@ By default, the `yearly` schedule is evaluated in the UTC time zone. To use a di ## {{watcher}} cron schedule [schedule-cron] -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. +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. ::::{tip} 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) .