From c19c669c7c9b54f7c742790025c2c3d1ad05a22f Mon Sep 17 00:00:00 2001 From: Carlone Date: Thu, 6 Jun 2019 09:28:12 +0800 Subject: [PATCH] Fix typo in limit-range.md. (#14730) --- 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 3b28cc5fe0..97b70358a1 100644 --- a/content/en/docs/concepts/policy/limit-range.md +++ b/content/en/docs/concepts/policy/limit-range.md @@ -19,7 +19,7 @@ Within a namespace, a Pod or Container can consume as much CPU and memory as def A limit range, defined by a `LimitRange` object, provides constraints that can: -- Enforce minimun and maximum compute resources usage per Pod or Container in a namespace. +- Enforce minimum and maximum compute resources usage per Pod or Container in a namespace. - Enforce minimum and maximum storage request per PersistentVolumeClaim in a namespace. - Enforce a ratio between request and limit for a resource in a namespace. - Set default request/limit for compute resources in a namespace and automatically inject them to Containers at runtime.