update generated release notes

Author: edb-slonik

product_docs/docs/tpa/23/rel_notes/tpa_23.42.0_rel_notes.mdx

@@ -87,7 +87,7 @@ escalation command. Refer to the documentation in ansible-and-sudo.md and config
 for detailed usage examples and configuration guidelines.</li>
 </ul>
 </details></td><td></td></tr>
-<tr><td><details><summary>The <code>download-packages</code> command now has a 'refresh repository metadata' option</summary><hr/><p>A new option has been included on the <code>tpaexec download-packages</code> command (<code>--refresh-repository</code>,
+<tr><td><details><summary>The <code>download-packages</code> command now has a 'refresh repository metadata' option.</summary><hr/><p>A new option has been included on the <code>tpaexec download-packages</code> command (<code>--refresh-repository</code>,
 requires Docker &amp; its corresponding Docker image to work). Prior to this change,
 we relied on the user to have the commands required to manually recreate the local
 repository, depending on its cluster and OS. This fix provides
@@ -96,7 +96,7 @@ are being placed and the new version of said packages is selected on the configu
 file. It also includes documentation covering the steps that need to be taken,
 given the different air-gapped conditions that can be found, and minor fixes that
 were discovered related to the DNF repository in an air-gapped scenario.</p>
-</details></td><td>52313, 52313, 52313</td></tr>
+</details></td><td>52313</td></tr>
 </tbody></table>
 
 
@@ -193,7 +193,7 @@ at configure time if one has not been specified already. Note that TPA will not
 automatically select a cluster network that contains the provided IP addresses,
 so the <code>--network</code> option should be used to specify a matching CIDR.</p>
 </details></td><td></td></tr>
-<tr><td><details><summary>Fixed an issue with undefined Patroni SSL facts during upgrade and test phases</summary><hr/><p>SSL-related facts set during deployment were not persisted across playbook
+<tr><td><details><summary>Fixed an issue with undefined Patroni SSL facts during upgrade and test phases.</summary><hr/><p>SSL-related facts set during deployment were not persisted across playbook
 runs, causing errors such as <code>'patroni_ssl_ca_file' is undefined</code> when running
 <code>upgrade</code> or <code>test</code> against a Patroni cluster with SSL enabled. These facts are
 now set by a dedicated <code>patroni/facts</code> role included at the relevant points in
@@ -279,7 +279,7 @@ for all etcd nodes using pyformat_hostvars, it looked for etcd_protocol in each
 host's hostvars, however, only the current host had set this fact during an upgrade.
 This caused a KeyError when accessing other hosts.</p>
 </details></td><td></td></tr>
-<tr><td><details><summary>Fixed an issue with 'basic' authentication in 'etcd_authentication_mode'</summary><hr/><p>When selecting 'basic' authentication for 'etcd_authentication_mode', the
+<tr><td><details><summary>Fixed an issue with 'basic' authentication in 'etcd_authentication_mode'.</summary><hr/><p>When selecting 'basic' authentication for 'etcd_authentication_mode', the
 execution of the deployment would fail on the task that grants permissions to
 the 'patroni' role in etcd, responsible for making calls to the etcd cluster.
 This was due to a fact variable not being properly defined in the scope of the