Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update the to include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.

Discussion:
### LIST and WATCH filtering <del> LIST and WATCH operations may specify label selectors to filter the sets of objects returned using a query parameter. Both requirements are permitted </del> <ins> For **list** and **watch** operations, you can specify label selectors to filter the sets of objects returned; you specify the filter using a query parameter. (To learn in detail about watches in Kubernetes, read [efficient detection of changes](/docs/reference/using-api/api-concepts/#efficient-detection-of-changes)). Both requirements are permitted </ins> (presented here as they would appear in a URL query string): * _equality-based_ requirements: `?labelSelector=environment%3Dproduction,tier%3Dfrontend`

``` deployment.apps/nginx-deployment resumed ``` <del> * Watch the status of the rollout until it's done. </del> <ins> * {{< glossary_tooltip text="Watch" term_id="watch" >}} the status of the rollout until it's done. </ins> ```shell <del> kubectl get rs -w </del> <ins> kubectl get rs --watch </ins> ``` The output is similar to this:

<ins> --- title: Watch id: watch date: 2024-07-02 full_link: /docs/reference/using-api/api-concepts/#api-verbs short_description: > A verb that is used to track changes to an object in Kubernetes as a stream. aka: tags: - API verb - fundamental --- A verb that is used to track changes to an object in Kubernetes as a stream. It is used for the efficient detection of changes. <!--more--> A verb that is used to track changes to an object in Kubernetes as a stream. Watches allow efficient detection of changes; for example, a {{< glossary_tooltip term_id="controller" text="controller">}} that needs to know whenever a ConfigMap has changed can use a watch rather than polling. See [Efficient Detection of Changes in API Concepts](/docs/reference/using-api/api-concepts/#efficient-detection-of-changes) for more information. </ins>

log retrievals), and can accept and serve those resources in different representations for convenience or efficiency. <del> Kubernetes supports efficient change notifications on resources via *watches*. </del> <ins> Kubernetes supports efficient change notifications on resources via _watches_: {{< glossary_definition prepend="in the Kubernetes API, watch is" term_id="watch" length="short" >}} </ins> Kubernetes also provides consistent list operations so that API clients can effectively cache, track, and synchronize the state of resources.

``` As you can see from the results of the command, the cron job has not scheduled or run any jobs yet. <del> Watch for the job to be created in around one minute: </del> <ins> {{< glossary_tooltip text="Watch" term_id="watch" >}} for the job to be created in around one minute: </ins> ```shell kubectl get jobs --watch

{{% code_sample file="application/web/web.yaml" %}} You will need to use at least two terminal windows. In the first terminal, use <del> [`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) to watch the creation </del> <ins> [`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) to {{< glossary_tooltip text="watch" term_id="watch" >}} the creation </ins> of the StatefulSet's Pods. ```shell