docs(review): minor fixes from review (#11920)

Signed-off-by: prmellor <[email protected]>

Author: PaulRMellor

documentation/modules/configuring/con-maintenance-time-window-definition.adoc

@@ -62,7 +62,7 @@ spec:
   #...
 ----
 
-NOTE: The Cluster Operator doesn't adhere strictly to the time windows 
+NOTE: The Cluster Operator doesn't adhere strictly to the time windows. 
 Maintenance operations are triggered by the first reconciliation that occurs within the specified time window. 
 If the time window is shorter than the interval between reconciliations, there's a risk that the reconciliation may happen outside of the time window, 
 Therefore, maintenance time windows must be at least as long as the interval between reconciliations.

documentation/modules/configuring/ref-list-of-kafka-cluster-resources.adoc

@@ -39,7 +39,6 @@ The following resources are created by the Cluster Operator in the Kubernetes cl
 `<kafka_cluster_name>-kafka-<listener_name>-<pod_id>`:: Service used to route traffic from outside the Kubernetes cluster to individual pods. This resource is created only when an external listener is enabled. The new service name will be used for all other external listeners.
 `<kafka_cluster_name>-kafka-<listener_name>-bootstrap`:: Bootstrap route for clients connecting from outside the Kubernetes cluster. This resource is created only when an external listener is enabled and set to type `route`. The new route name will be used for all other external listeners.
 `<kafka_cluster_name>-kafka-<listener_name>-<pod_id>`:: Route for traffic from outside the Kubernetes cluster to individual pods. This resource is created only when an external listener is enabled and set to type `route`. The new route name will be used for all other external listeners.
-`<kafka_cluster_name>-kafka-config`:: ConfigMap containing the Kafka ancillary configuration, which is mounted as a volume by the broker pods when the `UseStrimziPodSets` feature gate is disabled.
 `<kafka_cluster_name>-<pool_name>-<pod_id>_`:: Secret with Kafka node public and private keys.
 `<kafka_cluster_name>-network-policy-kafka`:: Network policy managing access to the Kafka services.
 `strimzi-_namespace-name_-<kafka_cluster_name>-kafka-init`:: Cluster role binding used by the Kafka brokers.

documentation/modules/metrics/con-metrics-cruise-control.adoc

@@ -16,7 +16,7 @@ The metrics are used to xref:proc-generating-optimization-proposals-str[generate
 Cruise Control metrics are available for real-time monitoring of Cruise Control operations.
 For example, you can use Cruise Control metrics to monitor the status of rebalancing operations that are running or provide alerts on any anomalies that are detected in an operation's performance.
 
-You expose Cruise Control metrics by xref:assembly-metrics-setup-{context}[enabling the {JMXExporter} in the Cruise Control configuration].
+For more information on exposing Cruise Control metrics, see xref:assembly-metrics-setup-str[Using Prometheus with Strimzi].
 
 NOTE: For a full list of available Cruise Control metrics, which are known as _sensors_, see the {CruiseControlSensorsDocs}
 

documentation/modules/security/con-certificate-renewal.adoc

@@ -99,7 +99,7 @@ However, the Cluster Operator regenerates them to align their validity period wi
 
 . Restarts the components to trust the new Cluster CA certificate and use the renewed internal certificates.
 
-=== Clients CA renewal
+== Clients CA renewal
 
 To renew the Clients CA certificate, the Cluster Operator and User Operator each perform part of the process: