Update 4.2.0 release notes

Author: michaelklishin

release-notes/4.2.0.md

@@ -315,9 +315,26 @@ compared to other versions.
 
    GitHub issues: [#14403](https://github.com/rabbitmq/rabbitmq-server/pull/14403), [#14406](https://github.com/rabbitmq/rabbitmq-server/pull/14406)
 
+### MQTT Plugin
+
+#### Bug Fixes
+
+ * [Resource alarm](https://www.rabbitmq.com/docs/alarms) handling now uses more context: it is aware of individual resources.
+   When a cluster had multiple resource alarms (namely for memory footprint and free disk space)
+   in effect, the blocking state was prematurely cleared when only one resource was [cleared].
+
+   GitHub issue: [#14795](https://github.com/rabbitmq/rabbitmq-server/pull/14795)
+
 
 ### CLI Tools
 
+#### Bug Fixes
+
+ * `rabbitmqctl export_definitions` could incorrectly serialize policy and operator policy
+   definitions.
+
+   GitHub issue: [#14800](https://github.com/rabbitmq/rabbitmq-server/pull/14800)
+
 #### Enhancements
 
  * `rabbitmq-diagnostics ` is a new command that provides a message size distribution.
@@ -365,7 +382,7 @@ compared to other versions.
 #### Bug Fixes
 
  * Direct AMQP 0-9-1 shovel connections within a cluster (not to be confused with local shovels introduced in this release)
-   are now blocked by [resource alarms]() just like their "network" counterparts are.
+   are now blocked by [resource alarms](https://www.rabbitmq.com/docs/alarms) just like their "network" counterparts are.
 
    GitHub issue: [#14657](https://github.com/rabbitmq/rabbitmq-server/issues/14657)
 
@@ -380,18 +397,38 @@ compared to other versions.
  * Prometheus metric collector failed with an exception when the scraper endpoint
    was hit when one or more shovels were still starting.
 
+
 ### AWS Peer Discovery Plugin
 
 #### Bug Fixes
 
- * The plugin implicitly depended on ordering of `networkInterfaceSet` and `` EC2 API response fields,
+ * The plugin implicitly depended on ordering of `networkInterfaceSet` and `privateIpAddressesSet` EC2 API response fields,
    which could result in obscure cluster formation issues.
 
    GitHub issue: [#14557](https://github.com/rabbitmq/rabbitmq-server/pull/14557)
 
 
+### STOMP Plugin
+
+#### Bug Fixes
+
+ * [Resource alarm](https://www.rabbitmq.com/docs/alarms) handling now uses more context: it is aware of individual resources.
+   When a cluster had multiple resource alarms (namely for memory footprint and free disk space)
+   in effect, the blocking state was prematurely cleared when only one resource was [cleared].
+
+   GitHub issue: [#14795](https://github.com/rabbitmq/rabbitmq-server/pull/14795)
+
+
 ### Web MQTT Plugin
 
+#### Bug Fixes
+
+ * [Resource alarm](https://www.rabbitmq.com/docs/alarms) handling now uses more context: it is aware of individual resources.
+   When a cluster had multiple resource alarms (namely for memory footprint and free disk space)
+   in effect, the blocking state was prematurely cleared when only one resource was [cleared].
+
+   GitHub issue: [#14795](https://github.com/rabbitmq/rabbitmq-server/pull/14795)
+
 #### Enhancements
 
  * HTTP/2 is enabled for WebSocket connections by default.
@@ -428,11 +465,11 @@ their dashboards and/or alerts. If you are using the
 [RabbitMQ-Quorum-Queues-Raft dashboard](https://grafana.com/grafana/dashboards/11340-rabbitmq-quorum-queues-raft/),
 please update it to the latest version for RabbitMQ 4.2 compatibility.
 
-#### More Accurate and Detailed Ra Metrics 
+#### More Accurate and Detailed Ra Metrics
 
 Ra is an internal component implementing the Raft protocol. It's the basis
 for quorum queues, as well as some internal components (currently Khepri
-and Stream Coordinator). For quite some time, Ra metrics were tracked in two places
+and the Stream Coordinator). For quite some time, Ra metrics were tracked in two places
 but RabbitMQ relied on the old metric subsystem. In RabbitMQ 4.2, the old
 Ra metrics subsystem has been removed and RabbitMQ now reports Ra metrics
 from the new subsystem (implemented using [Seshat](https://github.com/rabbitmq/seshat) library).