From 46f596fd5b2cd086ad7c94f838a7c78c7ea2cbfc Mon Sep 17 00:00:00 2001 From: PingWang Date: Tue, 8 Oct 2019 11:25:11 +0800 Subject: [PATCH] Fix typos (#16731) Signed-off-by: PingWang Fix typos in limit-range.md Signed-off-by: PingWang --- content/en/docs/concepts/policy/limit-range.md | 4 ++-- content/en/docs/concepts/scheduling/kube-scheduler.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/policy/limit-range.md b/content/en/docs/concepts/policy/limit-range.md index 6fb7b1dcd6..5fe14e18dc 100644 --- a/content/en/docs/concepts/policy/limit-range.md +++ b/content/en/docs/concepts/policy/limit-range.md @@ -58,7 +58,7 @@ Neither contention nor changes to limitrange will affect already created resourc The following section discusses the creation of a LimitRange acting at Container Level. A Pod with 04 containers is first created; each container within the Pod has a specific `spec.resource` configuration -each containerwithin the pod is handled differently by the LimitRanger admission controller. +each container within the pod is handled differently by the LimitRanger admission controller. Create a namespace `limitrange-demo` using the following kubectl command @@ -107,7 +107,7 @@ kubectl apply -f https://k8s.io/examples/admin/resource/limit-range-pod-1.yaml - ``` ### Container spec with valid CPU/Memory requests and limits -View the the `busybox-cnt01` resource configuration +View the `busybox-cnt01` resource configuration ```shell kubectl get po/busybox1 -n limitrange-demo -o json | jq ".spec.containers[0].resources" diff --git a/content/en/docs/concepts/scheduling/kube-scheduler.md b/content/en/docs/concepts/scheduling/kube-scheduler.md index ef18b49b92..53aaa33ae2 100644 --- a/content/en/docs/concepts/scheduling/kube-scheduler.md +++ b/content/en/docs/concepts/scheduling/kube-scheduler.md @@ -86,7 +86,7 @@ kube-scheduler has a default set of scheduling policies. ### Filtering - `PodFitsHostPorts`: Checks if a Node has free ports (the network protocol kind) - for the Pod ports the the Pod is requesting. + for the Pod ports the Pod is requesting. - `PodFitsHost`: Checks if a Pod specifies a specific Node by it hostname.