From 86435e460d4303f50bfd2115e577cd31b89c164d Mon Sep 17 00:00:00 2001
From: William Dumont <william.dumont@grafana.com>
Date: Fri, 31 Jan 2025 11:12:15 +0100
Subject: [PATCH] typo

---
 docs/sources/reference/config-blocks/foreach.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/reference/config-blocks/foreach.md b/docs/sources/reference/config-blocks/foreach.md
index c2e8a0d201..f9c8724a38 100644
--- a/docs/sources/reference/config-blocks/foreach.md
+++ b/docs/sources/reference/config-blocks/foreach.md
@@ -126,7 +126,7 @@ On the other hand, `discovery.*` components such as `discovery.kubernetes` outpu
 {{< /collapse >}}
 
 You can use a `foreach` to loop over each target and start a separate component pipeline for it.
-The following example configuration shows how a `prometheus.exporter.redis` instance is started for each Redis instance discoverd by `discovery.kubernetes`.
+The following example configuration shows how a `prometheus.exporter.redis` instance is started for each Redis instance discovered by `discovery.kubernetes`.
 Additional Kubernetes labels from `discovery.kubernetes` are also added to the metrics created by `prometheus.exporter.redis`.
 
 ```alloy