auto-docs: Update Helm spec

Author: vbotbuildovich

modules/reference/pages/k-redpanda-helm-spec.adoc

@@ -2,8 +2,8 @@
 
 :description: Find the default values and descriptions of settings in the Redpanda Helm chart.
 
-image:https://img.shields.io/badge/Version-5.9.13-informational?style=flat-square[Version:
-5.9.13]
+image:https://img.shields.io/badge/Version-5.9.14-informational?style=flat-square[Version:
+5.9.14]
 image:https://img.shields.io/badge/Type-application-informational?style=flat-square[Type:
 application]
 image:https://img.shields.io/badge/AppVersion-v24.2.7-informational?style=flat-square[AppVersion:
@@ -791,8 +791,7 @@ resources documentation].
 Redpanda makes use of a thread per core model. For details, see this
 https://redpanda.com/blog/tpc-buffers[blog]. For this reason, Redpanda
 should only be given full cores. Note: You can increase cores, but
-decreasing cores is not currently supported. See the
-https://github.com/redpanda-data/redpanda/issues/350[GitHub issue]. This
+decreasing cores is supported only from 24.3 Redpanda version. This
 setting is equivalent to `--smp`, `resources.requests.cpu`, and
 `resources.limits.cpu`. For production, use `4` or greater. To maximize
 efficiency, use the `static` CPU manager policy by specifying an even
@@ -820,14 +819,14 @@ Enables memory locking. For production, set to `true`.
 enable_memory_locking: false It is recommended to have at least 2Gi of
 memory per core for the Redpanda binary. This memory is taken from the
 total memory given to each container. The Helm chart allocates 80% of
-the container’s memory to Redpanda, leaving the rest for the Seastar
-subsystem (reserveMemory) and other container processes. So at least
-2.5Gi per core is recommended in order to ensure Redpanda has a full
-2Gi. These values affect `--memory` and `--reserve-memory` flags passed
-to Redpanda and the memory requests/limits in the StatefulSet. Valid
-suffixes: k, M, G, T, P, Ki, Mi, Gi, Ti, Pi To create `Guaranteed` Pod
-QoS for Redpanda brokers, provide both container max and min values for
-the container. For details, see
+the container’s memory to Redpanda, leaving the rest for other container
+processes. So at least 2.5Gi per core is recommended in order to ensure
+Redpanda has a full 2Gi. These values affect `--memory` and
+`--reserve-memory` flags passed to Redpanda and the memory
+requests/limits in the StatefulSet. Valid suffixes: k, M, G, T, P, Ki,
+Mi, Gi, Ti, Pi To create `Guaranteed` Pod QoS for Redpanda brokers,
+provide both container max and min values for the container. For
+details, see
 https://kubernetes.io/docs/tasks/configure-pod-container/quality-service-pod/#create-a-pod-that-gets-assigned-a-qos-class-of-guaranteed
 * Every container in the Pod must have a memory limit and a memory
 request. * For every container in the Pod, the memory limit must equal