From d53c074a7ffa329d9746d852e32daac6ed665e01 Mon Sep 17 00:00:00 2001
From: Arhell <arhell333@gmail.com>
Date: Sun, 29 Dec 2024 00:22:44 +0200
Subject: [PATCH] [zh] typo

---
 .../zh-cn/docs/concepts/overview/working-with-objects/names.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/zh-cn/docs/concepts/overview/working-with-objects/names.md b/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
index d69fd51ddc..7ab5930e33 100644
--- a/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
+++ b/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
@@ -66,7 +66,7 @@ In cases when objects represent a physical entity, like a Node representing a ph
 <!--
 The server may generate a name when `generateName` is provided instead of `name` in a resource create request.
 When `generateName` is used, the provided value is used as a name prefix, which server appends a generated suffix
-to. Even though the name is generated, it may conflict with existing names resulting in a HTTP 409 resopnse. This
+to. Even though the name is generated, it may conflict with existing names resulting in a HTTP 409 response. This
 became far less likely to happen in Kubernetes v1.31 and later, since the server will make up to 8 attempt to generate a
 unique name before returning a HTTP 409 response.
 -->