Tidy up release notes for Gazpacho release

Change-Id: I9a7ba73ed499dd5edeea5f8fec6a4aef72d026cb
Signed-off-by: Bertrand Lanson <bertrand.lanson@infomaniak.com>

16 files changed, 36 insertions, 40 deletions

diff --git a/releasenotes/notes/add_neutron_external_interface_length_check-e7c4456b92cae281.yaml b/releasenotes/notes/add_neutron_external_interface_length_check-e7c4456b92cae281.yaml
index c66c808a9..76531ed03 100644
--- a/releasenotes/notes/add_neutron_external_interface_length_check-e7c4456b92cae281.yaml
+++ b/releasenotes/notes/add_neutron_external_interface_length_check-e7c4456b92cae281.yaml
@@ -1,10 +1,9 @@
 ---
 features:
   - |
-    Add neutron interface<->bridge parity validation.
-    Validates that the number of neutron_external_interface
-    entries matches the number of neutron_bridge_name entries
-    in the configuration. This prevents misconfigurations
-    that could cause deployment failures or incorrect
-    networking behavior.
+    Added a validation check to ensure the number of
+    ``neutron_external_interface`` entries matches the number of
+    ``neutron_bridge_name`` entries in the configuration.
+    This prevents misconfigurations that could cause deployment
+    failures or incorrect networking behavior.
     `LP#1864832 <https://launchpad.net/bugs/1864832>`__
diff --git a/releasenotes/notes/add_rabbitmq_mgm_tls-86706572b96aacfa.yaml b/releasenotes/notes/add_rabbitmq_mgm_tls-86706572b96aacfa.yaml
index 83a03b83b..864e56ea6 100644
--- a/releasenotes/notes/add_rabbitmq_mgm_tls-86706572b96aacfa.yaml
+++ b/releasenotes/notes/add_rabbitmq_mgm_tls-86706572b96aacfa.yaml
@@ -1,4 +1,6 @@
 ---
 features:
   - |
-    Added support for RabbitMQ management interface SSL configuration.
+    Added TLS support for the RabbitMQ management API and UI. When
+    ``rabbitmq_enable_tls`` is set to ``true``, TLS is now also enabled
+    for the RabbitMQ management interface.
diff --git a/releasenotes/notes/barbican-uwsgi-845123de69b4a30a.yaml b/releasenotes/notes/barbican-uwsgi-845123de69b4a30a.yaml
index 81b658029..91e4ca7b4 100644
--- a/releasenotes/notes/barbican-uwsgi-845123de69b4a30a.yaml
+++ b/releasenotes/notes/barbican-uwsgi-845123de69b4a30a.yaml
@@ -1,5 +1,5 @@
 ---
 upgrade:
   - |
-    ``barbican`` uWSGI configuration has been reworked to use the same service
-    role as other Ansible roles.
+    ``barbican-api`` uWSGI configuration has been migrated to use the
+    ``service-uwsgi-config`` role, consistent with other Kolla-Ansible roles.
diff --git a/releasenotes/notes/bug-2073159-67532593585a1e10.yaml b/releasenotes/notes/bug-2106219-67532593585a1e10.yaml
index a9e60b073..a9e60b073 100644
--- a/releasenotes/notes/bug-2073159-67532593585a1e10.yaml
+++ b/releasenotes/notes/bug-2106219-67532593585a1e10.yaml
diff --git a/releasenotes/notes/bug-2131993-d67c68845ddf5556.yaml b/releasenotes/notes/bug-2131993-d67c68845ddf5556.yaml
index 8c06ba28b..ad4ad91d9 100644
--- a/releasenotes/notes/bug-2131993-d67c68845ddf5556.yaml
+++ b/releasenotes/notes/bug-2131993-d67c68845ddf5556.yaml
@@ -3,4 +3,4 @@ fixes:
   - |
     Fixes issue where ProxySQL certificates were copied over even
     with ``kolla_externally_managed_cert`` set to True.
-    `LP#2073159 <https://launchpad.net/bugs/2131993>`__
+    `LP#2131993 <https://launchpad.net/bugs/2131993>`__
diff --git a/releasenotes/notes/bug-2138498-564e7475f1d4cc27.yaml b/releasenotes/notes/bug-2138498-564e7475f1d4cc27.yaml
index dcbd2c54d..41c353134 100644
--- a/releasenotes/notes/bug-2138498-564e7475f1d4cc27.yaml
+++ b/releasenotes/notes/bug-2138498-564e7475f1d4cc27.yaml
@@ -4,5 +4,4 @@ fixes:
     Fixed an issue where Neutron sub-services (RPC server, maintenance and
     periodic workers) would crash when ``enable_neutron_vpnaas`` was set to
     ``yes`` due to missing ``neutron_vpnaas.conf`` file injection.
-    neutron: inject neutron_vpnaas.conf into auxiliary services
     `LP#2138498 <https://launchpad.net/bugs/2138498>`__
diff --git a/releasenotes/notes/bug-2143979-7c81b4560bba6efd.yaml b/releasenotes/notes/bug-2143979-7c81b4560bba6efd.yaml
index 5a9f4729b..8d8575416 100644
--- a/releasenotes/notes/bug-2143979-7c81b4560bba6efd.yaml
+++ b/releasenotes/notes/bug-2143979-7c81b4560bba6efd.yaml
@@ -5,6 +5,6 @@ fixes:
     unnecessarily restarted during every ``reconfigure``
     operation. The container handler now correctly includes
     the ``healthcheck`` configuration, ensuring idempotency
-    by matching the container's runtime definition  with
+    by matching the container's runtime definition with
     the service defaults.
     `LP#2143979 <https://launchpad.net/bugs/2143979>`__
diff --git a/releasenotes/notes/bugfix-bump-mariadb-innodb-log-file-size-6d280b738baa3897.yaml b/releasenotes/notes/bugfix-bump-mariadb-innodb-log-file-size-6d280b738baa3897.yaml
index 3dafce0c8..038557bb7 100644
--- a/releasenotes/notes/bugfix-bump-mariadb-innodb-log-file-size-6d280b738baa3897.yaml
+++ b/releasenotes/notes/bugfix-bump-mariadb-innodb-log-file-size-6d280b738baa3897.yaml
@@ -2,22 +2,17 @@
 features:
   - |
     Increased the default value of ``innodb_log_file_size`` from 96MB to 2GB.
-    This change improves overall performance of MariaDB.
-    However, the recovery of MariaDB may take longer time as a tradeoff.
-    Users can adjust the value by overriding K-A variable
-    ``mariadb_innodb_log_file_size_mb``.
-    The allowed minimum is 4MB and maximum is 524288MB (512GB)
+    This change improves overall MariaDB performance, though crash recovery
+    may take longer as a tradeoff. Users can adjust the value by overriding
+    the ``mariadb_innodb_log_file_size_mb`` variable. The allowed range is
+    4MB to 524288MB (512GB).
 upgrade:
   - |
     The default value of ``innodb_log_file_size`` has increased from 96MB to
-    2GB.
-    This improves MariaDB performance but recovery time from crash may take
-    longer time as a tradeoff.
-    Users are recommended to consider the recovery time with new default
-    before upgrade.
-    Users are recommended to check if disk space is enough with larger InnoDB
-    log file.
+    2GB. This improves MariaDB performance but crash recovery may take longer.
+    Before upgrading, ensure sufficient disk space is available for the larger
+    InnoDB log file.
 fixes:
   - |
-    Fixes bug `LP#2129930 <https://bugs.launchpad.net/kolla-ansible/+bug/2129930>`__
-    which made Zuul CI to fail MariaDB backup test sometimes.
+    Fixed an intermittent Zuul CI failure in the MariaDB backup test.
+    `LP#2129930 <https://launchpad.net/bugs/2129930>`__
diff --git a/releasenotes/notes/drop-influxdb-telegraf-53da82866d55c3e5.yaml b/releasenotes/notes/drop-influxdb-telegraf-53da82866d55c3e5.yaml
index 92deca5d7..4f8a2159e 100644
--- a/releasenotes/notes/drop-influxdb-telegraf-53da82866d55c3e5.yaml
+++ b/releasenotes/notes/drop-influxdb-telegraf-53da82866d55c3e5.yaml
@@ -1,12 +1,10 @@
 ---
 upgrade:
   - |
-    Support for deploying ``influxdb`` has been dropped, because Kolla
-    delivers a community end of life version v1, and there are no plans
-    to upgrade influxdb to v2 - there are better open source alternatives
-    out there.
-    Existing users need to remove influxdb containers and their
-    configuration manually.
+    Support for deploying ``influxdb`` has been dropped. Kolla delivered
+    the community end-of-life version v1, and there are no plans to upgrade
+    to v2. Users should migrate to an alternative monitoring solution and
+    remove influxdb containers and their configuration manually.
   - |
     Support for deploying ``telegraf`` has been dropped after earlier
     deprecation.
diff --git a/releasenotes/notes/harden_haproxy_tls_config-edeea2ed54316bad.yaml b/releasenotes/notes/harden_haproxy_tls_config-edeea2ed54316bad.yaml
index 1adcdcec1..c5c2a235b 100644
--- a/releasenotes/notes/harden_haproxy_tls_config-edeea2ed54316bad.yaml
+++ b/releasenotes/notes/harden_haproxy_tls_config-edeea2ed54316bad.yaml
@@ -1,7 +1,7 @@
 ---
 features:
   - |
-    Harden the HAProxy TLS configuration according to Mozilla SSL
-    recommendations for HAProxy 2.8.15 and OpenSSL 3.x
+    The HAProxy TLS configuration has been hardened following Mozilla SSL
+    Modern recommendations for HAProxy 2.8.15 and OpenSSL 3.x
     (Rocky Linux and Ubuntu):
     `<https://ssl-config.mozilla.org/#server=haproxy&version=2.8.15&config=modern&openssl=3.0.13&guideline=5.7>`__
diff --git a/releasenotes/notes/ironic-drop-legacy-6ab1fa7c20a80ff7.yaml b/releasenotes/notes/ironic-drop-legacy-6ab1fa7c20a80ff7.yaml
index 0fe4e9821..07308c265 100644
--- a/releasenotes/notes/ironic-drop-legacy-6ab1fa7c20a80ff7.yaml
+++ b/releasenotes/notes/ironic-drop-legacy-6ab1fa7c20a80ff7.yaml
@@ -1,4 +1,5 @@
 ---
 upgrade:
   - |
-    ``Ironic`` legacy upgrade mechanism has been dropped.
+    The legacy (non-rolling) ``ironic`` upgrade mechanism has been dropped.
+    Ironic upgrades now exclusively use the rolling upgrade mechanism.
diff --git a/releasenotes/notes/new-datasource-alertmanager-d724981bd971da92.yaml b/releasenotes/notes/new-datasource-alertmanager-d724981bd971da92.yaml
index 0a63da14b..53591f203 100644
--- a/releasenotes/notes/new-datasource-alertmanager-d724981bd971da92.yaml
+++ b/releasenotes/notes/new-datasource-alertmanager-d724981bd971da92.yaml
@@ -1,4 +1,5 @@
 ---
 features:
   - |
-    Added new Alertmanager datasource in Grafana.
+    An Alertmanager datasource is now automatically configured in Grafana
+    when ``enable_prometheus_alertmanager`` is set to ``true``.
diff --git a/releasenotes/notes/remove-distro-python-version-09adac8895cb87d1.yaml b/releasenotes/notes/remove-distro-python-version-09adac8895cb87d1.yaml
index 6f19718c3..c3629c123 100644
--- a/releasenotes/notes/remove-distro-python-version-09adac8895cb87d1.yaml
+++ b/releasenotes/notes/remove-distro-python-version-09adac8895cb87d1.yaml
@@ -1,4 +1,5 @@
 ---
 upgrade:
   - |
-    The global variable ``distro_python_version`` has been removed
+    The global variable ``distro_python_version`` has been removed as it is
+    no longer needed. Python path handling is now done at the image level.
diff --git a/releasenotes/notes/stop-grafana-plugin-install-via-ui-6c437ae59b68ef53.yaml b/releasenotes/notes/stop-grafana-plugin-install-via-ui-6c437ae59b68ef53.yaml
index bfba78baa..c49655271 100644
--- a/releasenotes/notes/stop-grafana-plugin-install-via-ui-6c437ae59b68ef53.yaml
+++ b/releasenotes/notes/stop-grafana-plugin-install-via-ui-6c437ae59b68ef53.yaml
@@ -3,4 +3,4 @@ fixes:
   - |
     Prevents users installing plugins via the Grafana UI which will cause
     Grafana instances to become out-of-sync in multinode deployments.
-    See `LP#2122587 <https://bugs.launchpad.net/kolla-ansible/+bug/2122587>`_.
+    `LP#2122587 <https://launchpad.net/bugs/2122587>`__
diff --git a/releasenotes/notes/uwsgi-designate-649599b4b9a1bdfd.yaml b/releasenotes/notes/uwsgi-designate-649599b4b9a1bdfd.yaml
index 65097770c..64280ae73 100644
--- a/releasenotes/notes/uwsgi-designate-649599b4b9a1bdfd.yaml
+++ b/releasenotes/notes/uwsgi-designate-649599b4b9a1bdfd.yaml
@@ -1,4 +1,4 @@
 ---
 upgrade:
   - |
-    ``designate-api`` is now running under uWSGI and now supports backend TLS.
+    ``designate-api`` is now running under uWSGI and supports backend TLS.
diff --git a/releasenotes/notes/uwsgi-magnum-6702c72f30286978.yaml b/releasenotes/notes/uwsgi-magnum-6702c72f30286978.yaml
index d8794b4c8..47e5bf7a9 100644
--- a/releasenotes/notes/uwsgi-magnum-6702c72f30286978.yaml
+++ b/releasenotes/notes/uwsgi-magnum-6702c72f30286978.yaml
@@ -1,4 +1,4 @@
 ---
 upgrade:
   - |
-    ``magnum-api`` is now running under uWSGI and now supports backend TLS.
+    ``magnum-api`` is now running under uWSGI and supports backend TLS.