Update reference/fleet/alert-templates.md

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

Author: karenzone

reference/fleet/alert-templates.md

@@ -33,7 +33,7 @@ You can find these rules in **Stack Management** > **Alerts and Insights** > **R
 | [Elastic Agent] Dropped events | Checks if the percentage of dropped events to acked events from the pipeline is greater than or equal to 5%. Rows are distinguished by agent ID and component ID. |
 | [Elastic Agent] Excessive memory usage|  Checks if {{agent}} or any of its processes have a high memory usage or memory usage that is trending higher. This could signal a memory leak in an application and warrant further investigation.<br>- Condition: Alert on `system.process.memory.rss.pct` > 50%<br>- Default: Enabled |
 | [Elastic Agent] Excessive restarts| Checks for excessive restarts on a host which require further investigation. Some restarts can have a business impact and getting alerts for them can enable timely mitigation.<br>- Condition: Alert on restarts > 10 restarts in a 5 minute window<br>- Default: Enabled |
-| [Elastic Agent] High pipeline queue | Checks if max of `beat.stats.libbeat.pipeline.queue.filled.pct` exceeds 90%. Rows are distinct by agent id and component id. |
+| [Elastic Agent] High pipeline queue | Checks if max of `beat.stats.libbeat.pipeline.queue.filled.pct` exceeds 90%. Rows are distinguished by agent ID and component ID. |
 | [Elastic Agent] Output errors | Checks if errors per minute from an agent component is greater than 5. Rows are distinguished by agent ID and component ID. |
 | [Elastic Agent] Unhealthy status | Checks logs for an agent status change to `error` using the new `elastic_agent.status_change` datastreams. |