applied review suggestions

Author: tbazant

references/kubeflow-troubleshooting.adoc

@@ -109,8 +109,8 @@ If you pre-created the AuthorizationPolicy with `kubectl` before the first {helm
   meta.helm.sh/release-namespace=kubeflow --overwrite
 ----
 
-{seaweedfs} pod stuck ContainerCreating::
-On K3s 1.34 + cri-dockerd ({ranchera} Desktop), a race between the CNI and the container runtime can leave the {seaweedfs} pod stuck.
+{seaweedfs} pod stuck on ContainerCreating::
+On K3s 1.34 with cri-dockerd ({ranchera} Desktop), a race between the CNI and the container runtime can leave the {seaweedfs} pod stuck.
 {seaweedfs} acquires a LevelDB file lock on startup.
 If the pod is stuck, the lock is held and the next pod will also fail to start.
 To recover, run the following commands:

references/kubeflow-upgrade-notes.adoc

@@ -51,7 +51,7 @@ When switching database images or StorageClasses, delete the PVC manually first:
 Training operator webhook secret migration (auto)::
 On upgrade from chart versions prior to 0.3.0, a pre-upgrade hook automatically migrates the `training-operator-webhook-cert` Secret from type `kubernetes.io/tls` to `Opaque`.
 No manual action is required.
-If the `kubectl get jobs -n kubeflow` command reports a hook failure, delete the secret manually and re-run `helm upgrade`:
+If the `kubectl get jobs -n kubeflow` command reports a hook failure, delete the secret manually and rerun `helm upgrade`:
 +
 [source,bash,subs="+attributes"]
 ----

tasks/kubeflow-hardening.adoc

@@ -151,7 +151,7 @@ KFP and Dex PodDisruptionBudgets are already enabled by default.
 +
 PDBs protect against voluntary disruptions (node drains) but only provide meaningful coverage with 2 or more replicas.
 With a single replica, the PDB allows full eviction.
-See the xref:kubeflow-limitations[Known limitations] section for which controllers support HA.
+See xref:kubeflow-limitations[Known limitations] for supported HA controllers.
 
 . *Apply resource quotas per user namespace.*
 +

tasks/kubeflow-user-profiles.adoc

@@ -65,7 +65,7 @@ Add the user to your values file and run `helm upgrade`:
   --set "user-namespace.additionalUsers[0].namespace=tux"
 ----
 
-Alternatively, add the user to your values file and re-run the upgrade:
+Alternatively, add the user to your values file and rerun the upgrade:
 
 [source,bash]
 ----