From d884ce7ce04c9865e6acf47e5dda26f7dbbb64e9 Mon Sep 17 00:00:00 2001
From: Yuvraj Shekhawat <56301121+yuvraj9@users.noreply.github.com>
Date: Sun, 6 Mar 2022 02:49:14 +0530
Subject: [PATCH] Fixing typo error

---
 .../migrating-telemetry-and-security-agents.md                  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md
index 87ab93b1fc..13219bfd6d 100644
--- a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md
+++ b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md
@@ -22,7 +22,7 @@ Historically, Kubernetes was written to work specifically with Docker Engine.
 Kubernetes took care of networking and scheduling, relying on Docker Engine for launching
 and running containers (within Pods) on a node. Some information that is relevant to telemetry,
 such as a pod name, is only available from Kubernetes components. Other data, such as container
-metrics, is not the responsibility of the container runtime. Early yelemetry agents needed to query the
+metrics, is not the responsibility of the container runtime. Early telemetry agents needed to query the
 container runtime **and** Kubernetes to report an accurate picture. Over time, Kubernetes gained
 the ability to support multiple runtimes, and now supports any runtime that is compatible with
 the container runtime interface.