8000 fix: typos · kubernetes/website@a5d40c6 · GitHub
[go: up one dir, main page]
Skip to content

Commit a5d40c6

Browse files
JPBotelhoJPBotelho
committed
fix: typos
1 parent c4a92ea commit a5d40c6

File tree

22 files changed

+29
-29
lines changed

22 files changed

+29
-29
lines changed

‎content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -475,7 +475,7 @@ changes:
475475
### Ensure that the mutating webhooks in your cluster are idempotent {#ensure-mutating-webhook-idempotent}
476476

477477
Every mutating admission webhook should be _idempotent_. The webhook should be
478-
able to run on an object that it already modifed without making additional
478+
able to run on an object that it already modified without making additional
479479
changes beyond the original change.
480480

481481
Additionally, all of the mutating webhooks in your cluster should, as a

‎content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ then the values of other parameters will not be inherited as the default
229229
values and will be set to zero. In order to provide custom values, you
230230
should provide all the thresholds respectively. You can also set the kubelet config
231231
MergeDefaultEvictionSettings to true in the kubelet configuration file.
232-
If set to true and any paramater is changed, then the other parameters will
232+
If set to true and any parameter is changed, then the other parameters will
233233
inherit their default values instead of 0.
234234

235235
The `containerfs.available` and `containerfs.inodesFree` (Linux nodes) default

‎content/en/docs/concepts/workloads/pods/pod-lifecycle.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -287,7 +287,7 @@ explains the behaviour of `init containers` when specify `restartpolicy` field o
287287
feature_gate_name="ContainerRestartRules" >}}
288288

289289
If your cluster has the feature gate `ContainerRestartRules` enabled, you can specify
290-
`restartPolicy` and `restartPolicyRules` on _inidividual containers_ to override the Pod
290+
`restartPolicy` and `restartPolicyRules` on _individual containers_ to override the Pod
291291
restart policy. Container restart policy and rules applies to {{< glossary_tooltip text="app containers" term_id="app-container" >}}
292292
in the Pod and to regular [init containers](/docs/concepts/workloads/pods/init-containers/).
293293

@@ -331,7 +331,7 @@ spec:
331331
```
332332
333333
A Pod with Always restart policy with an init container that only execute once. If the init
334-
container fails, the Pod fails. This alllows the Pod to fail if the initialiaztion failed,
334+
container fails, the Pod fails. This allows the Pod to fail if the initialiaztion failed,
335335
but also keep running once the initialization succeeds:
336336
337337
```yaml

‎content/en/docs/reference/access-authn-authz/authentication.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ Read [X.509 client certificates](#x509-client-certificates) to learn about how t
243243
certificate.
244244

245245
If you do issue certificates to clients, it is up to you (as a cloud platform administrator)
246-
to make sure that the certicate validity period, and other design choices you make, provide a
246+
to make sure that the certificate validity period, and other design choices you make, provide a
247247
suitable level of security.
248248

249249
### OpenID Connect tokens

‎content/en/docs/reference/access-authn-authz/certificate-signing-requests.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ Signers abstractly represent the entity or entities that might sign, or have
112112
signed, a security certificate.
113113

114114
Any signer that is made available for outside a particular cluster should provide information
115-
about how the signer works, so that consumers can understand what that means for CertifcateSigningRequests
115+
about how the signer works, so that consumers can understand what that means for CertificateSigningRequests
116116
and (if enabled) [ClusterTrustBundles](#cluster-trust-bundles).
117117
This includes:
118118

‎content/en/docs/reference/command-line-tools-reference/feature-gates/ReloadKubeletServerCertificateFile.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,4 +14,4 @@ stages:
1414
Enable the kubelet TLS server to update its certificate if the specified certificate file are changed.
1515

1616
This feature is useful when specifying `tlsCertFile` and `tlsPrivateKeyFile` in kubelet configuration.
17-
The feature gate has no effect for other cases such as using TLS boostrap.
17+
The feature gate has no effect for other cases such as using TLS bootstrap.

‎content/en/docs/reference/command-line-tools-reference/feature-gates/SchedulerQueueingHints.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ stages:
2323
fromVersion: "1.34"
2424
---
2525
Enables scheduler [queueing hints](/docs/concepts/scheduling-eviction/scheduling-framework/#queueinghint),
26-
which benefits to reduce the useless requeueing.
26+
which benefits to reduce the useless requeuing.
2727
The scheduler retries scheduling pods if something changes in the cluster that could make the pod scheduled.
2828
Queueing hints are internal signals that allow the scheduler to filter the changes in the cluster
2929
that are relevant to the unscheduled pod, based on previous scheduling attempts.

‎content/en/docs/reference/config-api/apiserver-audit.v1.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,7 @@ be specified per rule in which case the union of both are omitted.</p>
253253
<td>
254254
<p>OmitManagedFields indicates whether to omit the managed fields of the request
255255
and response bodies from being written to the API audit log.
256-
This is used as a global default - a value of 'true' will omit the managed fileds,
256+
This is used as a global default - a value of 'true' will omit the managed fields,
257257
otherwise the managed fields will be included in the API audit log.
258258
Note that this can also be specified per rule in which case the value specified
259259
in a rule will override the global default.</p>
@@ -527,7 +527,7 @@ An empty list means no restrictions will apply.</p>
527527
and response bodies from being written to the API audit log.</p>
528528
<ul>
529529
<li>a value of 'true' will drop the managed fields from the API audit log</li>
530-
<li>a value of 'false' indicates that the managed fileds should be included
530+
<li>a value of 'false' indicates that the managed fields should be included
531531
in the API audit log
532532
Note that the value, if specified, in this rule will override the global default
533533
If a value is not specified then the global default specified in

‎content/en/docs/reference/config-api/kubeadm-config.v1beta3.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -591,7 +591,7 @@ control-plane node to the cluster.</p>
591591
</td>
592592
<td>
593593
<p><code>caCertPath</code> is the path to the SSL certificate authority used to secure
594-
comunications between a node and the control-plane.
594+
communications between a node and the control-plane.
595595
Defaults to &quot;/etc/kubernetes/pki/ca.crt&quot;.</p>
596596
</td>
597597
</tr>

‎content/en/docs/reference/config-api/kubeconfig.v1.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,21 +55,21 @@ TODO(jlowdermilk): remove this after eliminating downstream dependencies.</p>
5555
<a href="#NamedCluster"><code>[]NamedCluster</code></a>
5656
</td>
5757
<td>
58-
<p>Clusters is a map of referencable names to cluster configs</p>
58+
<p>Clusters is a map of referenceable names to cluster configs</p>
5959
</td>
6060
</tr>
6161
<tr><td><code>users</code> <B>[Required]</B><br/>
6262
<a href="#NamedAuthInfo"><code>[]NamedAuthInfo</code></a>
6363
</td>
6464
<td>
65-
<p>AuthInfos is a map of referencable names to user configs</p>
65+
3E14 <p>AuthInfos is a map of referenceable names to user configs</p>
6666
</td>
6767
</tr>
6868
<tr><td><code>contexts</code> <B>[Required]</B><br/>
6969
<a href="#NamedContext"><code>[]NamedContext</code></a>
7070
</td>
7171
<td>
72-
<p>Contexts is a map of referencable names to context configs</p>
72+
<p>Contexts is a map of referenceable names to context configs</p>
7373
</td>
7474
</tr>
7575
<tr><td><code>current-context</code> <B>[Required]</B><br/>

0 commit comments

Comments
 (0)
0