From 8d0823792310d45b808729eab6dff4b89cea9bc7 Mon Sep 17 00:00:00 2001
From: zhaojinxin409 <5874804+zhaojinxin409@users.noreply.github.com>
Date: Tue, 1 Aug 2023 15:09:01 +0800
Subject: [PATCH] Update stream-aggregation.md for `speed` misspelling (#4752)

---
 docs/stream-aggregation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/stream-aggregation.md b/docs/stream-aggregation.md
index acbb9ecb7..9be338bac 100644
--- a/docs/stream-aggregation.md
+++ b/docs/stream-aggregation.md
@@ -83,7 +83,7 @@ Sometimes [alerting queries](https://docs.victoriametrics.com/vmalert.html#alert
 disk IO and network bandwidth at metrics storage side. For example, if `http_request_duration_seconds` histogram is generated by thousands
 of application instances, then the alerting query `histogram_quantile(0.99, sum(increase(http_request_duration_seconds_bucket[5m])) without (instance)) > 0.5`
 can become slow, since it needs to scan too big number of unique [time series](https://docs.victoriametrics.com/keyConcepts.html#time-series)
-with `http_request_duration_seconds_bucket` name. This alerting query can be sped up by pre-calculating
+with `http_request_duration_seconds_bucket` name. This alerting query can be speed up by pre-calculating
 the `sum(increase(http_request_duration_seconds_bucket[5m])) without (instance)` via [recording rule](https://docs.victoriametrics.com/vmalert.html#recording-rules).
 But this recording rule may take too much time to execute too. In this case the slow recording rule can be substituted
 with the following [stream aggregation config](#stream-aggregation-config):