[DOCS-11327] Add note that throttle limit is per Worker

layouts/shortcodes/observability_pipelines/processors/throttle.md

@@ -3,6 +3,8 @@ Use this processor to set a limit on the number of logs sent within a specific t
 To set up the processor:
 
 1. Define a [filter query](#filter-query-syntax). Only logs that match the specified filter query are processed. All matched logs get throttled. Logs that are sent within the throttle limit and logs that do not match the filter are sent to the next step. Logs sent after the throttle limit has been reached, are dropped.
-1. Set the throttling rate. This is the number of events allowed for a given bucket during the set time window.
+1. Set the throttling rate. This is the number of events allowed for a given bucket during the set time window. **Note**: This rate limit is applied on a per-worker level. If you scale the number of workers up or down, you may want to adjust the processor rate limit accordingly. You can do this programmatically using the [Observability Pipelines API][10210].
 1. Set the time window.
-1. Optionally, click **Add Field** if you want to group by a field.
+1. Optionally, click **Add Field** if you want to group by a field.
+
+[10210]: /api/latest/observability-pipelines/#update-a-pipeline