Apply suggestions from code review

Co-authored-by: Kevin DiMichel <56850465+kevin-dimichel@users.noreply.github.com>
Signed-off-by: Alan Smith <209585+mo-getter@users.noreply.github.com>

Author: mo-getter

docs/orchestrators/configuring-kubernetes-orchestrator.md

@@ -467,18 +467,17 @@ fom.register_orchestrator(
 > FiftyOne UI's log viewer for delegated-operator runs — it depends on
 > the sidecar to capture per-operation logs.
 
-If your deployment runs telemetry (the helm chart and docker compose
-files include it by default), you can attach a per-Job telemetry
+If your deployment runs telemetry (the Helm chart includes 
+it by default), you can attach a per-Job telemetry
 sidecar to on-demand Kubernetes orchestrators as well.
 This emits per-operation metrics back to the same Redis backend so the
 Settings → Metrics page sees individual delegated runs.
 
-Use of a Kubernetes
+We use Kubernetes
 [native sidecar](https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/)
-(an `initContainer` with `restartPolicy: Always`, requires Kubernetes
-1.29+).
-A regular sidecar container would block Job completion — the Job stays
-in `Running` until every container exits.
+(an `initContainer` with `restartPolicy: Always`).
+A regular sidecar container would block Job completion where the Job stays
+in `Running` status until every container exits.
 Native sidecars are auto-terminated by the kubelet when all non-sidecar
 containers complete, so the Job finalizes cleanly.
 
@@ -822,7 +821,7 @@ spec:
 ```
 
 The `telemetry-sidecar` init container above is optional.
-If you are not running telemetry, remove all of the following from the
+To opt out of running telemetry, remove all of the following from the
 template:
 
 - the `telemetry-sidecar` init container

helm/docs/upgrading.md

@@ -150,7 +150,7 @@ FiftyOne Enterprise v2.19.0 adds observability features viewable by
 admins directly in the FiftyOne UI.
 These are powered by a `telemetry-sidecar` container injected into the
 `teams-api`, `fiftyone-app`, `teams-plugins`, and delegated-operator
-workloads (and as a native init-sidecar on on-demand delegated-operator
+workloads (and as a native sidecar on on-demand delegated-operator
 `Job` pods), plus an in-cluster Redis `Deployment` + `Service` that
 buffers the streamed metrics and logs.
 
@@ -161,8 +161,8 @@ A default deploy adds four sidecars
 delegated-operator), so expect roughly **+400m CPU** and **+2 GiB
 memory** in additional resource usage, plus the bundled Redis (`250m`
 CPU / `512Mi` memory, request == limit) backed by an `emptyDir`.
-Tune via `telemetry.sidecar.resources` and `telemetry.redis.resources`;
-opt into a `PersistentVolumeClaim` with
+Tune via `telemetry.sidecar.resources` and `telemetry.redis.resources`.
+Opt into a `PersistentVolumeClaim` with
 `telemetry.redis.persistence.enabled: true`.
 
 ##### Cluster Requirements
@@ -205,7 +205,7 @@ telemetry:
 ```
 
 > [!IMPORTANT]
-> The sidecar powers the FiftyOne UI's delegated-operator log viewer.
+> The telemetry sidecars power the FiftyOne UI's delegated-operator log viewer.
 > Disabling telemetry (`telemetry.enabled: false`) will leave that log
 > viewer empty.
 

helm/fiftyone-teams-app/values.yaml

@@ -1621,7 +1621,7 @@ teamsAppSettings:
   # -- Volumes for `teams-app` pods. [Reference][volumes].
   volumes: []
 
-# In-cluster telemetry. Renders a Redis Deployment + Service, a Role/RoleBinding
+# In-cluster telemetry. Renders a Redis Deployment, Service, a Role/RoleBinding
 # granting `pods/log` read access, and a `telemetry-sidecar` injected into the
 # `teams-api`, `fiftyone-app`, `teams-plugins`, and delegated-operator workloads.
 telemetry: