Add glossary tooltips for resource terms

Help people reading glossary entries understand what those entries
mean by the term "resource".

Author: Tim Bannister

content/en/docs/reference/glossary/api-group.md

@@ -11,9 +11,12 @@ tags:
 - fundamental
 - architecture
 ---
-A set of related paths in Kubernetes API. 
+A set of related paths in Kubernetes API.
 
 <!--more-->
-You can enable or disable each API group by changing the configuration of your API server. You can also disable or enable paths to specific resources. API group makes it easier to extend the Kubernetes API. The API group is specified in a REST path and in the `apiVersion` field of a serialized object.
+
+You can enable or disable each API group by changing the configuration of your API server. You can also disable or enable paths to specific
+{{< glossary_tooltip text="resources" term_id="api-resource" >}}. An API group makes it easier to extend the Kubernetes API.
+The API group is specified in a REST path and in the `apiVersion` field of a serialized {{< glossary_tooltip text="object" term_id="object" >}}.
 
 * Read [API Group](/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning) for more information.

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

@@ -9,7 +9,8 @@ aka:
 tags:
 - tool
 ---
-cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running {{< glossary_tooltip text="containers" term_id="container" >}}.
+cAdvisor (Container Advisor) provides container users an understanding of the {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}}
+usage and performance characteristics of their running {{< glossary_tooltip text="containers" term_id="container" >}}.
 
 <!--more-->
 

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

@@ -10,7 +10,7 @@ aka:
 tags:
 - fundamental
 ---
-A group of Linux processes with optional resource isolation, accounting and limits.
+A group of Linux processes with optional {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}} isolation, accounting and limits.
 
 <!--more--> 
 

content/en/docs/reference/glossary/container-env-variables.md

@@ -14,4 +14,4 @@ tags:
 
 <!--more-->
 
-Container environment variables provide information that is required by the running containerized applications along with information about important resources to the {{< glossary_tooltip text="containers" term_id="container" >}}. For example, file system details, information about the container itself, and other cluster resources such as service endpoints.
+Container environment variables provide information that is required by the running containerized applications along with information about important related details to the {{< glossary_tooltip text="containers" term_id="container" >}}. For example, file system details, information about the container itself, and other cluster resources such as service endpoints.

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

@@ -12,8 +12,10 @@ tags:
 - operation
 - extension
 ---
- Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
+A kind of {{< glossary_tooltip text="API object" term_id="object" >}} that defines a new custom API to add
+to your Kubernetes API server, without building a complete custom server.
 
 <!--more-->
 
-Custom Resource Definitions let you extend the Kubernetes API for your environment if the publicly supported API resources can't meet your needs.
+CustomResourceDefinitions let you extend the Kubernetes API for your environment if the built-in
+{{< glossary_tooltip text="API resources" term_id="api-resource" >}} can't meet your needs.

content/en/docs/reference/glossary/device-plugin.md

@@ -12,7 +12,8 @@ tags:
 ---
  Device plugins run on worker
 {{< glossary_tooltip term_id="node" text="Nodes">}} and provide
-{{< glossary_tooltip term_id="pod" text="Pods">}} with access to resources,
+{{< glossary_tooltip term_id="pod" text="Pods">}} with access to
+infrastructure {{< glossary_tooltip text="resources" term_id="infrastructure-resource" >}},
 such as local hardware, that require vendor-specific initialization or setup
 steps.
 

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

@@ -11,8 +11,8 @@ tags:
 ---
  Disruptions are events that lead to one or more
 {{< glossary_tooltip term_id="pod" text="Pods" >}} going out of service.
-A disruption has consequences for workload resources, such as
-{{< glossary_tooltip term_id="deployment" >}}, that rely on the affected
+A disruption has consequences for workload management {{< glossary_tooltip text="resources" term_id="api-resource" >}},
+such as {{< glossary_tooltip term_id="deployment" >}}, that rely on the affected
 Pods.
 
 <!--more-->

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

@@ -10,8 +10,9 @@ aka:
 tags:
 - networking
 ---
- Endpoints track the IP addresses of Pods with matching  {{< glossary_tooltip text="selectors" term_id="selector" >}}.
+Legacy {{< glossary_tooltip text="API resource" term_id="api-resource" >}} for tracking the IP addresses of Pods that back
+{{< glossary_tooltip text="Services" term_id="service" >}}
 
 <!--more-->
-Endpoints can be configured manually for {{< glossary_tooltip text="Services" term_id="service" >}} without selectors specified.
-The {{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}} resource provides a scalable and extensible alternative to Endpoints.
+The {{< glossary_tooltip text="EndpointSlice" term_id="endpoint-slice" >}} object kind provides a scalable and extensible
+alternative to Endpoints.

content/en/docs/reference/glossary/ephemeral-container.md

@@ -14,6 +14,8 @@ A {{< glossary_tooltip term_id="container" >}} type that you can temporarily run
 
 <!--more-->
 
-If you want to investigate a Pod that's running with problems, you can add an ephemeral container to that Pod and carry out diagnostics. Ephemeral containers have no resource or scheduling guarantees, and you should not use them to run any part of the workload itself.
+If you want to investigate a Pod that's running with problems, you can add an ephemeral container to that Pod and carry out diagnostics.
+Ephemeral containers have no {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}} or scheduling guarantees,
+and you should not use them to run any part of the workload itself.
 
 Ephemeral containers are not supported by {{< glossary_tooltip text="static pods" term_id="static-pod" >}}.

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

@@ -4,19 +4,19 @@ id: event
 date: 2022-01-16
 full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
 short_description: >
-   Events are Kubernetes objects that describe some state change in the system.
+   Kubernetes objects that describe some state change in the cluster.
 aka: 
 tags:
 - core-object
 - fundamental
 ---
-Event is a Kubernetes object that describes state change/notable occurrences in the system.
+A Kubernetes {{< glossary_tooltip text="object" term_id="object" >}} that describes state changes
+or notable occurrences in the cluster.
 
 <!--more-->
-Events have a limited retention time and triggers and messages may evolve with time. 
-Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger, 
-or the continued existence of events with that reason. 
-
+Events have a limited retention time and triggers and messages may evolve with time.
+Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger,
+or the continued existence of events with that reason.
 
 Events should be treated as informative, best-effort, supplemental data.