Merge pull request #34071 from lostick/fix-typos-content-docs

Fix typos in tasks docs
This commit is contained in:
Kubernetes Prow Robot
2022-05-31 15:09:23 -07:00
committed by GitHub
4 changed files with 5 additions and 5 deletions
@@ -280,7 +280,7 @@ kubectl patch deployment valid-deployment --type json -p='[{"op": "remove", "
# Add a new element to a positional array
kubectl patch sa default --type='json' -p='[{"op": "add", "path": "/secrets/1", "value": {"name": "whatever" } }]'
# Update a deployment's replicas count by patching it's scale subresource
# Update a deployment's replica count by patching its scale subresource
kubectl patch deployment nginx-deployment --subresource='scale' --type='merge' -p '{"spec":{"replicas":2}}'
```
@@ -24,7 +24,7 @@ This document describes using `telepresence` to develop and debug services runni
## Connecting your local machine to a remote Kubernetes cluster
After installing `telepresence`, run `telepresence connect` to launch it's Daemon and connect your local workstation to the cluster.
After installing `telepresence`, run `telepresence connect` to launch its Daemon and connect your local workstation to the cluster.
```
$ telepresence connect
@@ -444,7 +444,7 @@ spec:
served: true
# One and only one version must be marked as the storage version.
storage: true
# Each version can define it's own schema when there is no top-level
# Each version can define its own schema when there is no top-level
# schema is defined.
schema:
openAPIV3Schema:
@@ -512,7 +512,7 @@ spec:
served: true
# One and only one version must be marked as the storage version.
storage: true
# Each version can define it's own schema when there is no top-level
# Each version can define its own schema when there is no top-level
# schema is defined.
schema:
openAPIV3Schema:
@@ -400,7 +400,7 @@ scaling in that direction.
### Stabilization window
The stabilization window is used to restrict the [flapping](#flapping) of
replicas count when the metrics used for scaling keep fluctuating. The autoscaling algorithm
replica count when the metrics used for scaling keep fluctuating. The autoscaling algorithm
uses this window to infer a previous desired state and avoid unwanted changes to workload
scale.