diff --git a/content/en/docs/concepts/overview/working-with-objects/names.md b/content/en/docs/concepts/overview/working-with-objects/names.md
index 02fb2fd1ecfa2..70028903a125b 100644
--- a/content/en/docs/concepts/overview/working-with-objects/names.md
+++ b/content/en/docs/concepts/overview/working-with-objects/names.md
@@ -34,9 +34,9 @@ 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 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.
+to. Even though the name is generated, it may conflict with existing names resulting in an HTTP 409 response. This
+became far less likely to happen in Kubernetes v1.31 and later, since the server will make up to 8 attempts to generate a
+unique name before returning an HTTP 409 response.
 
 Below are four types of commonly used name constraints for resources.