docs: Add various small tweaks

Author: Techassi

modules/ROOT/partials/release-notes/release-25.11.adoc

@@ -92,36 +92,35 @@ The Stackable platform now provides an operator for OpenSearch.
 We initially support version link:#new-product-versions-25_11_0[3.1.0], which is also marked as the LTS line going forward.
 
 OpenSearch is a powerful search and analytics engine built on Apache Lucene.
-OpenSearch clusters can be specified in custom resources similar to other Stackable operators.
+OpenSearch clusters can be defined via custom resources similar to other Stackable operators.
 For instance, a cluster with OpenSearch nodes of different types and replication factors can be defined.
 Logging, Monitoring and service exposition with ListenerClasses is supported as well.
 As the operator is still in an early development phase, special care was taken to allow extensive overriding with xref:concepts:overrides.adoc#config-overrides[`configOverrides`] and xref:concepts:overrides.adoc#pod-overrides[`podOverrides`].
 
 The operator only manages the OpenSearch back-end.
 The OpenSearch Dashboards front-end can be installed via the https://github.com/opensearch-project/helm-charts/tree/opensearch-dashboards-3.1.0/charts/opensearch-dashboards[official Helm chart].
-Stackable provides a supported image for OpenSearch Dashboard which can be used with this Helm chart.
+Stackable provides a supported image for OpenSearch Dashboards which can be used with this Helm chart.
 
 See the xref:opensearch:index.adoc[OpenSearch documentation] page for more details.
 
 ===== Trino
 
-* The operator now supports configuring fault-tolerant execution for Trino via the TrinoCluster CRD.
+* The operator now supports configuring fault-tolerant execution via the TrinoCluster CRD.
   See the xref:trino:usage-guide/fault-tolerant-execution.adoc[documentation page] and https://github.com/stackabletech/trino-operator/pull/779[trino-operator#779].
 * The Trino client spooling protocol can now be configured using the `spec.clusterConfig.clientProtocol.spooling` property.
-// TODO: Is this an S3Connection (CR)?
-  Users can configure an S3 connection and the location or spooling segments.
-  Additional properties can be added using the `configOverrides` mechanism for the `spooling-manager.properties` file.
+  Users can configure an xref:concepts:s3.adoc[S3Connection] and the location of spooling segments.
+  Additional properties can be added using the xref:concepts:overrides.adoc#config-overrides[`configOverrides`] mechanism for the `spooling-manager.properties` file.
   See the xref:trino:usage-guide/client-spooling-protocol.adoc[client spooling protocol] documentation page and https://github.com/stackabletech/trino-operator/pull/793[trino-operator#793].
 
 ==== Platform improvements
 
-===== Vulnerabilities
+===== General
+
+====== Vulnerabilities
 
 37 CVEs were fixed in the Stackable product images.
 This includes 2 critical and 18 high-severity CVEs.
 
-===== General
-
 ====== Observability
 
 This release includes various improvements in regards to metrics collection and exposition.
@@ -256,10 +255,10 @@ helm --set preset=stable-nodes # or ephemeral-nodes or none
 
 [source,shell]
 ----
-stackablectl --listener-class-preset stable-nodes # or ephemeral-nodes or none <1>
+stackablectl --listener-class-preset stable-nodes # or ephemeral-nodes or none
 ----
 
-<1> It should be noted that `stackablectl` automatically detects k3s and kind clusters and uses the `stable-nodes` preset.
+It should be noted that `stackablectl` automatically detects k3s and kind clusters and uses the `stable-nodes` preset since version xref:management:stackablectl:release-notes.adoc#_1_2_0[1.2.0].
 
 See the tracking issue https://github.com/stackabletech/issues/issues/770[issues#770] for more details.
 --
@@ -549,7 +548,7 @@ See https://github.com/stackabletech/spark-k8s-operator/issues/600[spark-k8s-ope
 ===== Apache Superset
 
 Previously, there was a chance containers would not start, because Superset was starting too slowly and was killed because of a failing liveness probe.
-Now, we add a proper startup probe, which allows Superset startup to succeed and not be killed.
+This has now been fixed by adding a proper startup probe, which allows Superset startup to succeed and not be killed.
 See https://github.com/stackabletech/superset-operator/pull/654[superset-operator#654].
 
 ===== Open Policy Agent
@@ -582,7 +581,7 @@ The following new product versions are now supported:
 * Apache HBase: https://github.com/stackabletech/docker-images/issues/1269[2.6.3 (LTS)]
 * Apache Hadoop: https://github.com/stackabletech/docker-images/issues/1270[3.4.2 (LTS)]
 * Apache Hive: https://github.com/stackabletech/docker-images/issues/1235[4.1.0]
-* Apache Kafka: https://github.com/stackabletech/docker-images/issues/1236[4.1.o (experimental)]
+* Apache Kafka: https://github.com/stackabletech/docker-images/issues/1236[4.1.0 (experimental)]
 * Apache NiFi: https://github.com/stackabletech/docker-images/issues/1237[2.6.0 (LTS)]
 * Apache Spark: https://github.com/stackabletech/docker-images/issues/1273[3.5.7 (LTS)], https://github.com/stackabletech/docker-images/issues/1273[4.0.1 (experimental)]
 * Apache Superset: https://github.com/stackabletech/docker-images/issues/1274[4.1.4 (LTS)]
@@ -657,7 +656,7 @@ These OpenShift versions are no longer supported:
 
 ====== Upgrade with a single command
 
-Starting with stackablectl Release 1.0.0 the multiple consecutive commands described below can be shortened to just one command, which executes exactly those steps on its own.
+Starting with `stackablectl` xref:management:stackablectl:release-notes.adoc#_1_0_0[1.0.0] the multiple consecutive commands described below can be shortened to just one command, which executes exactly those steps on its own.
 
 [source,console]
 ----