Change:
handled.  We encourage the curious to check out Docker's documentation for this feature. Kubernetes allows you to override both the image's default command (docker `Entrypoint`) and args <del> (docker `Cmd`) with the `Command` and `Args` fields of `Container`.  The rules are: </del> <ins> (docker `Cmd`) with the `command` and `args` fields of `container`.  The rules are: </ins> <del> 1.  If you do not supply a `Command` or `Args` for a container, the defaults defined by the image will be used 2.  If you supply a `Command` but no `Args` for a container, only the supplied `Command` will be used; the image's default arguments are ignored 3.  If you supply only `Args`, the image's default command will be used with the arguments you supply 4.  If you supply a `Command` **and** `Args`, the image's defaults will be ignored and the values you supply will be used </del> <ins> 1.  If you do not supply a `command` or `args` for a container, the defaults defined by the image will be used. 2.  If you supply a `command` but no `args` for a container, only the supplied `command` will be used; the image's default arguments are ignored. 3.  If you supply only `args`, the image's default command will be used with the arguments you supply. 4.  If you supply a `command` **and** `args`, the image's defaults will be ignored and the values you supply will be used. </ins> Here are examples for these rules in table format <del> | Image `Entrypoint` |    Image `Cmd`   | Container `Command` |  Container `Args`  |    Command Run   | </del> <ins> | Image `Entrypoint` |    Image `Cmd`   | Container `command` |  Container `args`  |    Command Run   | </ins> |--------------------|------------------|---------------------|--------------------|------------------| |     `[/ep-1]`      |   `[foo bar]`    |   &lt;not set&gt;   |   &lt;not set&gt;  | `[ep-1 foo bar]` | |     `[/ep-1]`      |   `[foo bar]`    |      `[/ep-2]`      |   &lt;not set&gt;  |     `[ep-2]`     |

Discussion:
Some of our docs, such as those copied from design docs, refer to Go types and field names rather than API resource names and json field names. For example, in the following doc, is a Go field name. would be the json field name: A more important example to fix is this one, which mentions and repeatedly rather than and : There's no example on that page, either. The example is here: I wouldn't fix these one by one, but instead would address it as we clean up or replace each doc. cc
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale
/remove-lifecycle rotten
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close