nits

rubenfiszel · rubenfiszel · commit 072275d43165 · 2025-01-31T10:53:09.000+01:00
diff --git a/docs/core_concepts/42_autoscaling/index.mdx b/docs/core_concepts/42_autoscaling/index.mdx
@@ -72,7 +72,7 @@ Every 30s, for every worker group autoscaling configuration:
 
 1. It checks if the current number of workers (`count`) is within the allowed range (between `min_workers` and `max_workers`). If not, it adjusts the number to fit within this range.
 2. If there are more than (`full_scale_jobs_waiting` OR `max_workers` if not defined) jobs , it will increase the number of workers up to `max_workers` if there are less (otherwise if workers already above or equal taret, do nothing), that's a "full scale-out". Note that full-scale out events are not subject to the cooldown period since they are meant to handle sudden spike.
-3. The function looks at the last autoscaling event (`last_event`) to see if it's too soon to make another change (this is called a cooldown period, defined by `full_scale_cooldown_seconds` for full scale out events or `cooldown_seconds` for normal events). Note that a full scale
+3. The function looks at the last autoscaling event (`last_event`) to see if it's too soon to make another change (this is called a cooldown period, defined by `full_scale_cooldown_seconds` for full scale out events or `cooldown_seconds` for normal events).
 4. If there are enough jobs waiting in the queue (more than `full_scale_jobs_waiting` OR `max_workers` if not defined), it will increase the number of workers up to `max_workers`.
 
 5. If there aren't many jobs waiting, it looks at how busy the current workers are using the `occupancy` data:
