From f66b69caa0671e8491f9686395120b4739148a83 Mon Sep 17 00:00:00 2001 From: Roy Hvaara Date: Fri, 11 Oct 2019 21:05:40 +0200 Subject: [PATCH] Fix wording --- content/en/docs/concepts/architecture/nodes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md index 751c04a3ea740..7f1c84df94f81 100644 --- a/content/en/docs/concepts/architecture/nodes.md +++ b/content/en/docs/concepts/architecture/nodes.md @@ -102,8 +102,8 @@ Describes the resources available on the node: CPU, memory and the maximum number of pods that can be scheduled onto the node. The fields in the capacity block indicate the total amount of resources that a -Node has. The allocatable block indicates the amount of resources that on a -Node that are available to be consumed by normal Pods. +Node has. The allocatable block indicates the amount of resources on a +Node that is available to be consumed by normal Pods. You may read more about capacity and allocatable resources while learning how to [reserve compute resources](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) @@ -244,7 +244,7 @@ For self-registration, the kubelet is started with the following options: - `--node-labels` - Labels to add when registering the node in the cluster (see label restrictions enforced by the [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction) in 1.13+). - `--node-status-update-frequency` - Specifies how often kubelet posts node status to master. -When the [Node authorization mode](/docs/reference/access-authn-authz/node/) and +When the [Node authorization mode](/docs/reference/access-authn-authz/node/) and [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction) are enabled, kubelets are only authorized to create/modify their own Node resource.