diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md
index 726e9c9b3..386a74008 100644
--- a/docs/CHANGELOG.md
+++ b/docs/CHANGELOG.md
@@ -53,7 +53,7 @@ See also [LTS releases](https://docs.victoriametrics.com/lts-releases/).
 * FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): support client-side TLS configuration for VictoriaMetrics destination specified via `--vm-*` cmd-line flags used in [InfluxDB](https://docs.victoriametrics.com/vmctl/#migrating-data-from-influxdb-1x), [Remote Read protocol](https://docs.victoriametrics.com/vmctl/#migrating-data-by-remote-read-protocol), [OpenTSDB](https://docs.victoriametrics.com/vmctl/#migrating-data-from-opentsdb), [Prometheus](https://docs.victoriametrics.com/vmctl/#migrating-data-from-prometheus) and [Promscale](https://docs.victoriametrics.com/vmctl/#migrating-data-from-promscale) migration modes.
 
 * BUGFIX: do not drop `match[]` filter at [`/api/v1/series`](https://docs.victoriametrics.com/url-examples/#apiv1series) if `-search.ignoreExtraFiltersAtLabelsAPI` command-line flag is set, since missing `match[]` filter breaks `/api/v1/series` requests.
-* BUGFIX: [stream aggregation](https://docs.victoriametrics.com/stream-aggregation/): pick samples with bigger values and timestamps on deduplication interval
+* BUGFIX: [stream aggregation](https://docs.victoriametrics.com/stream-aggregation/): take into account sample timestamp during [deduplication](https://docs.victoriametrics.com/stream-aggregation/#deduplication). If multiple samples have the same timestamp on the configured deduplication interval, then the sample with the biggest value is kept. The logic is aligned with [`-dedup.minScrapeInterval`](https://docs.victoriametrics.com/#deduplication).
 
 ## [v1.99.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.99.0)
 
diff --git a/docs/stream-aggregation.md b/docs/stream-aggregation.md
index 027c7c648..94fc533fb 100644
--- a/docs/stream-aggregation.md
+++ b/docs/stream-aggregation.md
@@ -78,9 +78,10 @@ to the configured `-remoteWrite.url`. The de-duplication can be enabled via the
 
 It is possible to drop the given labels before applying the de-duplication. See [these docs](#dropping-unneeded-labels).
 
-The online de-duplication doesn't take into account timestamps associated with the de-duplicated samples - it just leaves the last seen sample
-on the configured deduplication interval. If you need taking into account timestamps during the de-duplication,
-then use [`-dedup.minScrapeInterval` command-line flag](https://docs.victoriametrics.com/#deduplication).
+The online de-duplication takes into account timestamps associated with the de-duplicated samples - it keeps the sample
+with the newest timestamp on the configured deduplication interval. If multiple samples have the same timestamp on the
+configured deduplication interval, then the sample with the biggest value is kept. The logic is aligned with
+[`-dedup.minScrapeInterval` command-line flag](https://docs.victoriametrics.com/#deduplication).
 
 ## Flush time alignment