From 3415c996f23b2ad85cdca3f567c7a6f96aa301a8 Mon Sep 17 00:00:00 2001 From: nurayko <88191393+nurayko@users.noreply.github.com> Date: Fri, 6 Jan 2023 13:09:24 +0200 Subject: [PATCH] Fix typo --- content/en/docs/concepts/policy/limit-range.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/policy/limit-range.md b/content/en/docs/concepts/policy/limit-range.md index a1428b0e4b..e1e0d0b93a 100644 --- a/content/en/docs/concepts/policy/limit-range.md +++ b/content/en/docs/concepts/policy/limit-range.md @@ -50,7 +50,7 @@ The name of a LimitRange object must be a valid ## LimitRange and admission checks for Pods -A `LimitRange` does **not** check the consistency of the default values it applies. This means that a default value for the _limit_ that is set by `LimitRange` may be less than the _request_ value specified for the container in the spec that a client submits to the API server. If that happens, the final Pod will not be scheduleable. +A `LimitRange` does **not** check the consistency of the default values it applies. This means that a default value for the _limit_ that is set by `LimitRange` may be less than the _request_ value specified for the container in the spec that a client submits to the API server. If that happens, the final Pod will not be schedulable. For example, you define a `LimitRange` with this manifest: