From c5230bd0e206704cdd99b3b6a00be4d91ca4328f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tanja=20Mili=C4=8Di=C4=87?=
 <156105538+tanja-milicic@users.noreply.github.com>
Date: Fri, 6 Jun 2025 15:37:05 +0200
Subject: [PATCH] Fix typo at eck-stack-monitoring.md

---
 deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md
index 6a12ccdbe6..e32354f1c5 100644
--- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md
+++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md
@@ -38,7 +38,7 @@ However, for maximum efficiency and minimizing resource consumption, or advanced
 
 To enable stack monitoring, reference the monitoring {{es}} cluster in the `spec.monitoring` section of their specification. 
 
-The monitoring cluster must be managed by ECK in the same Kubernetes cluster as the monitored one. To learn how to connect an external monitoring cluster, refer to [Connect ot an external monitoring {{es}} cluster](#k8s_connect_to_an_external_monitoring_elasticsearch_cluster).
+The monitoring cluster must be managed by ECK in the same Kubernetes cluster as the monitored one. To learn how to connect an external monitoring cluster, refer to [Connect to an external monitoring {{es}} cluster](#k8s_connect_to_an_external_monitoring_elasticsearch_cluster).
 
 The following example shows how {{stack}} components can be configured to send their monitoring data to a separate {{es}} cluster in the same Kubernetes cluster.