Merge pull request #1264 from zhxcai/typo
Automatic merge from submit-queue. fix some typos
This commit is contained in:
commit
38100fe2cb
|
@ -301,7 +301,7 @@ that the returned value is not in the known type.
|
|||
We add the `contentEncoding` field here to preserve room for future
|
||||
optimizations like encryption-at-rest or compression of the nested content.
|
||||
Clients should error when receiving an encoding they do not support.
|
||||
Negotioting encoding is not defined here, but introducing new encodings
|
||||
Negotiating encoding is not defined here, but introducing new encodings
|
||||
is similar to introducing a schema change or new API version.
|
||||
|
||||
A client should use the `kind` and `apiVersion` fields to identify the
|
||||
|
|
|
@ -18,7 +18,7 @@ schema). `get` supports a `wide` mode that includes additional columns. Users ca
|
|||
flag. Headers corresponding to the columns are optionally displayed.
|
||||
|
||||
`kubectl describe` shows a textual representation of individual objects that describes individual fields as subsequent
|
||||
lines and uses indendation and nested tables to convey deeper structure on the resource (such as events for a pod or
|
||||
lines and uses indentation and nested tables to convey deeper structure on the resource (such as events for a pod or
|
||||
each container). It sometimes retrieves related objects like events, pods for a replication controller, or autoscalers
|
||||
for a deployment. It supports no significant flags.
|
||||
|
||||
|
|
|
@ -124,7 +124,7 @@ In addition, if an object popped from `dirtyQueue` is marked as "GC in progress"
|
|||
* To avoid racing with another controller, it requeues the object if `observedGeneration < Generation`. This is best-effort, see [unhandled cases](#unhandled-cases).
|
||||
* Checks if the object has dependents
|
||||
* If not, send a PUT request to remove the `GCFinalizer`;
|
||||
* If so, then add all dependents to the `dirtryQueue`; we need bookkeeping to avoid adding the dependents repeatedly if the owner gets in the `synchronousGC queue` multiple times.
|
||||
* If so, then add all dependents to the `dirtyQueue`; we need bookkeeping to avoid adding the dependents repeatedly if the owner gets in the `synchronousGC queue` multiple times.
|
||||
|
||||
## Controllers
|
||||
|
||||
|
|
|
@ -77,7 +77,7 @@ superseded-by:
|
|||
## Table of Contents
|
||||
|
||||
A table of contents is helpful for quickly jumping to sections of a KEP and for
|
||||
highlighting any addtional information provided beyond the standard KEP
|
||||
highlighting any additional information provided beyond the standard KEP
|
||||
template. [Tools for generating][] a table of contents from markdown are
|
||||
available.
|
||||
|
||||
|
|
Loading…
Reference in New Issue