From 23f58571a1e1861526280daf817d1495be851663 Mon Sep 17 00:00:00 2001 From: kpbaks Date: Sat, 4 Oct 2025 15:50:47 +0200 Subject: [PATCH] docs: fix typo in declarative-validation.md special not pecial --- content/en/docs/reference/using-api/declarative-validation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/using-api/declarative-validation.md b/content/en/docs/reference/using-api/declarative-validation.md index b48f941b4970e..da2175e4095a4 100644 --- a/content/en/docs/reference/using-api/declarative-validation.md +++ b/content/en/docs/reference/using-api/declarative-validation.md @@ -15,7 +15,7 @@ Kubernetes {{< skew currentVersion >}} includes optional _declarative validation code (`validation.go` files) to ensure that requests against the API are valid. Kubernetes developers, and people [extending the Kubernetes API](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/), can define validation rules directly alongside the API type definitions (`types.go` files). Code authors define -pecial comment tags (e.g., `+k8s:minimum=0`). A code generator (`validation-gen`) then uses these tags to produce +special comment tags (e.g., `+k8s:minimum=0`). A code generator (`validation-gen`) then uses these tags to produce optimized Go code for API validation. While primarily a feature impacting Kubernetes contributors and potentially developers of [extension API servers](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/), cluster administrators should understand its behavior, especially during its rollout phases.