Fix UPGRADE files for framework.messenger.reset_on_message option

Author: fancyweb

UPGRADE-5.4.md

@@ -38,6 +38,7 @@ FrameworkBundle
  * Deprecate `get()`, `has()`, `getDoctrine()`, and `dispatchMessage()` in `AbstractController`, use method/constructor injection instead
  * Deprecate the `cache.adapter.doctrine` service: The Doctrine Cache library is deprecated. Either switch to Symfony Cache or use the PSR-6 adapters provided by Doctrine Cache.
  * In `framework.cache` configuration, using `cache.adapter.pdo` adapter with a Doctrine DBAL connection is deprecated, use `cache.adapter.doctrine_dbal` instead.
+ * Deprecate not setting the `framework.messenger.reset_on_message` config option, its default value will change to `true` in 6.0
 
 HttpKernel
 ----------
@@ -62,13 +63,12 @@ Messenger
 
  * Deprecate not setting the `delete_after_ack` config option (or DSN parameter) using the Redis transport,
    its default value will change to `true` in 6.0
- * Deprecate not setting the `reset_on_message` config option, its default value will change to `true` in 6.0
 
 Monolog
 -------
 
  * Deprecate `ResetLoggersWorkerSubscriber` to reset buffered logs in messenger
-   workers, use "reset_on_message" option in messenger configuration instead.
+   workers, use `framework.messenger.reset_on_message` option in FrameworkBundle messenger configuration instead.
 
 SecurityBundle
 --------------

UPGRADE-6.0.md

@@ -172,7 +172,6 @@ Messenger
  * Removed the `prefetch_count` parameter in the AMQP bridge.
  * Removed the use of TLS option for Redis Bridge, use `rediss://127.0.0.1` instead of `redis://127.0.0.1?tls=1`
  * The `delete_after_ack` config option of the Redis transport now defaults to `true`
- * The `reset_on_message` config option now defaults to `true`
 
 Mime
 ----