Clarify Kibana scalability guidance around interactive and background workloads (#7026)

Author: Copilot

deploy-manage/production-guidance/kibana-in-production-environments.md

@@ -19,9 +19,9 @@ How you deploy {{kib}} largely depends on your use case. If you are the only use
 
 ## Scalability
 
-With the introduction of new capabilities such as [{{kib}} Alerting](/explore-analyze/alerting.md) and the [Detection Rules](/solutions/security/detect-and-alert.md) engine, critical components for [Observability](/solutions/observability.md) and [Security](/solutions/security.md) solutions, the scalability factors have evolved significantly.
+Scaling {{kib}} requires accounting for a mix of interactive UI traffic, API requests, and background work. The relative impact of each can vary depending on the features and solutions you use.
 
-Now, Kibana’s resource requirements extend beyond user activity. The system must also handle workloads generated by automated processes, such as scheduled alerts, background detection rules, and other periodic tasks. These operations are managed by [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md), which is responsible for scheduling, executing, and coordinating all background tasks.
+Background work includes alerting rules, detection rules, reports, and other periodic tasks that [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md) schedules, executes, and coordinates.
 
 Additionally, the task manager enables distributed coordination across multiple {{kib}} instances, allowing {{kib}} to function as a logical cluster in certain aspects.