editing as per the reviews.

Signed-off-by: Ritikaa96 <ritika@india.nec.com>

content/en/docs/concepts/overview/working-with-objects/labels.md

@@ -201,8 +201,11 @@ For example: `partition in (customerA, customerB),environment!=qa`.
 
 ### LIST and WATCH filtering
 
-LIST and {{< glossary_tooltip text="WATCH" term_id="watch" >}} operations may specify label selectors to filter the sets of objects
-returned using a query parameter. Both requirements are permitted
+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
 (presented here as they would appear in a URL query string):
 
 * _equality-based_ requirements: `?labelSelector=environment%3Dproduction,tier%3Dfrontend`

content/en/docs/concepts/workloads/controllers/deployment.md

@@ -815,7 +815,7 @@ apply multiple fixes in between pausing and resuming without triggering unnecess
   ```
 * {{< glossary_tooltip text="Watch" term_id="watch" >}} the status of the rollout until it's done.
   ```shell
-  kubectl get rs -w
+  kubectl get rs --watch
   ```
 
   The output is similar to this:

content/en/docs/reference/access-authn-authz/authorization.md

@@ -61,7 +61,7 @@ Kubernetes reviews only the following API request attributes:
  * **extra** - A map of arbitrary string keys to string values, provided by the authentication layer.
  * **API** - Indicates whether the request is for an API resource.
  * **Request path** - Path to miscellaneous non-resource endpoints like `/api` or `/healthz`.
- * **API request verb** - API verbs like `get`, `list`, `create`, `update`, `patch`, `{{< glossary_tooltip text="watch" term_id="watch" >}}`, `delete`, and `deletecollection` are used for resource requests. To determine the request verb for a resource API endpoint, see [request verbs and authorization](/docs/reference/access-authn-authz/authorization/#determine-the-request-verb).
+ * **API request verb** - API verbs like `get`, `list`, `create`, `update`, `patch`, `watch`, `delete`, and `deletecollection` are used for resource requests. To determine the request verb for a resource API endpoint, see [request verbs and authorization](/docs/reference/access-authn-authz/authorization/#determine-the-request-verb).
  * **HTTP request verb** - Lowercased HTTP methods like `get`, `post`, `put`, and `delete` are used for non-resource requests.
  * **Resource** - The ID or name of the resource that is being accessed (for resource requests only) -- For resource requests using `get`, `update`, `patch`, and `delete` verbs, you must provide the resource name.
  * **Subresource** - The subresource that is being accessed (for resource requests only).

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

@@ -407,7 +407,7 @@ the bundle with their own arbitrary but stable ordering.
 ClusterTrustBundle objects should be considered world-readable within the
 cluster. If your cluster uses [RBAC](/docs/reference/access-authn-authz/rbac/)
 authorization, all ServiceAccounts have a default grant that allows them to
-**get**, **list**, and **{{< glossary_tooltip text="watch" term_id="watch" >}}** all ClusterTrustBundle objects.
+**get**, **list**, and **watch** all ClusterTrustBundle objects.
 If you use your own authorization mechanism and you have enabled
 ClusterTrustBundles in your cluster, you should set up an equivalent rule to
 make these objects public within the cluster, so that they work as intended.

content/en/docs/reference/glossary/watch.md

@@ -11,7 +11,8 @@ 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 excellent detection of changes.
+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-->
 

content/en/docs/reference/using-api/api-concepts.md

@@ -19,7 +19,9 @@ fine grained authorization (such as separate views for Pod details and
 log retrievals), and can accept and serve those resources in different
 representations for convenience or efficiency.
 
-Kubernetes supports efficient change notifications on resources via *{{< glossary_tooltip text="watches" term_id="watch" >}}*.
+Kubernetes supports efficient change notifications on resources via
+_watches_:
+{{< glossary_definition prepend="in the Kubernetes API, watch is" term_id="watch" length="short" >}}
 Kubernetes also provides consistent list operations so that API clients can
 effectively cache, track, and synchronize the state of resources.