From 8a4e75e961b5f738d80d2ee9cf01647f934d3fe7 Mon Sep 17 00:00:00 2001 From: Pascal Hofmann Date: Sun, 16 Nov 2025 06:49:08 +0100 Subject: [PATCH] docs: fix typo in job retry section --- docs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.md b/docs/index.md index 9cc0ccd184..8066357cab 100644 --- a/docs/index.md +++ b/docs/index.md @@ -79,7 +79,7 @@ The Instance Termination Watcher is creating log and optional metrics for termin This feature is Beta, changes will not trigger a major release as long in beta. -The Job Retry will allow you to retry scaling when a job is not started. When enabled the scale up lambda will send a retry message to the a SQS queue. The Job Retry lambda will check after a delay if the job is still queued, and if so, it will send a retry command to the scale up lambda via SQS. The feature is designed to be used with ephemeral runners. The feature is opt in, it will not be created by default. +The Job Retry will allow you to retry scaling when a job is not started. When enabled the scale up lambda will send a retry message to the SQS queue. The Job Retry lambda will check after a delay if the job is still queued, and if so, it will send a retry command to the scale up lambda via SQS. The feature is designed to be used with ephemeral runners. The feature is opt in, it will not be created by default. Consequences of enabling the feature are: