From d200811dac9fe157f2bc1e3b3113ed94c4eb28ca Mon Sep 17 00:00:00 2001 From: Gallardot Date: Wed, 14 Apr 2021 05:51:12 +0800 Subject: [PATCH] fix tiny typo (#1243) Signed-off-by: Gallardot Co-authored-by: Max Smythe --- docs/RELEASE.md | 2 +- website/docs/intro.md | 2 +- website/docs/mutation.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/RELEASE.md b/docs/RELEASE.md index 430d00facc2..fb59b258b8a 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -28,7 +28,7 @@ Prerequisites: Usage: `./third_party/k8s.io/kubernetes/hack/cherry_pick_pull.sh upstream/release-3.1 123` For example, this will cherry pick PR #123 into `upstream/release-3.1` branch and will create a PR for you. -You can also combine multiple PRs by seperating them with spaces (`./third_party/k8s.io/kubernetes/hack/cherry_pick_pull.sh upstream/release-3.1 123 456`) +You can also combine multiple PRs by separating them with spaces (`./third_party/k8s.io/kubernetes/hack/cherry_pick_pull.sh upstream/release-3.1 123 456`) If you want to run the script with dry run mode, set `DRY_RUN` to `true`. diff --git a/website/docs/intro.md b/website/docs/intro.md index 1217084dc8e..5c282f3ee68 100644 --- a/website/docs/intro.md +++ b/website/docs/intro.md @@ -7,7 +7,7 @@ slug: / ## Goals -Every organization has policies. Some are essential to meet governance and legal requirements. Others help ensure adherance to best practices and institutional conventions. Attempting to ensure compliance manually would be error-prone and frustrating. Automating policy enforcement ensures consistency, lowers development latency through immediate feedback, and helps with agility by allowing developers to operate independently without sacrificing compliance. +Every organization has policies. Some are essential to meet governance and legal requirements. Others help ensure adherence to best practices and institutional conventions. Attempting to ensure compliance manually would be error-prone and frustrating. Automating policy enforcement ensures consistency, lowers development latency through immediate feedback, and helps with agility by allowing developers to operate independently without sacrificing compliance. Kubernetes allows decoupling policy decisions from the inner workings of the API Server by means of [admission controller webhooks](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/), which are executed whenever a resource is created, updated or deleted. Gatekeeper is a validating (mutating TBA) webhook that enforces CRD-based policies executed by [Open Policy Agent](https://github.com/open-policy-agent/opa), a policy engine for Cloud Native environments hosted by CNCF as an incubation-level project. diff --git a/website/docs/mutation.md b/website/docs/mutation.md index 040b2dd35ba..e43f18ae042 100644 --- a/website/docs/mutation.md +++ b/website/docs/mutation.md @@ -102,7 +102,7 @@ parameters: The `location` element can specify either a simple subelement or an element in a list. For example the location `spec.containers[name:foo].imagePullPolicy` would be parsed as follows: - ***spec**.containers[name:foo].imagePullPolicy* - the spec element -- *spec.**containers[name:foo]**.imagePullPolicy* - container subelement of spec. The container element is a list. Out of the list choosen, an element with the `name` element having the value `foo`. +- *spec.**containers[name:foo]**.imagePullPolicy* - container subelement of spec. The container element is a list. Out of the list chosen, an element with the `name` element having the value `foo`. - *spec.containers[name:foo].**imagePullPolicy*** - in the element from the list chosen in the previous step the element `imagePullPolicy` is chosen The yaml illustrating the above `location`: