diff --git a/release-notes/4.0.1.md b/release-notes/4.0.1.md
index 601dda9e52ea..42831a3f6fb7 100644
--- a/release-notes/4.0.1.md
+++ b/release-notes/4.0.1.md
@@ -70,13 +70,14 @@ accidentally sacrificed.
 ### AMQP 0.9.1 x-death header
 
 Up to RabbitMQ 3.13, when an AMQP 0.9.1 client (re-)published a message to RabbitMQ, RabbitMQ interpreted the
-AMQP 0.9.1 [x-death](https://www.rabbitmq.com/docs/dlx#effects) header in the published message's `basic_message.content.properties.headers` field.
+AMQP 0.9.1 [`x-death`](https://www.rabbitmq.com/docs/dlx#effects) header in the published message's `basic_message.content.properties.headers` field.
 
 RabbitMQ 4.x will not interpret this `x-death` header anymore when clients (re-)publish a message.
 Note that RabbitMQ 4.x will continue to set and update the `x-death` header every time a message is dead-lettered, including when a client **rejects** the message.
 
-If you have a use case where you relied on RabbitMQ incrementing the `count` fields within the `x-death` header array elements for new messages **(re-)published**
-(instead of existing messages being rejected), consider introducing and incrementing [your own custom non `x-` header](https://github.com/rabbitmq/rabbitmq-server/issues/10709#issuecomment-1997083246) instead.
+Applications that rely on RabbitMQ incrementing the `count` fields within the `x-death` header array elements for new messages **(re-)published**
+(instead of existing messages being rejected), should introduce and increment [a separate `x-` header](https://github.com/rabbitmq/rabbitmq-server/issues/10709#issuecomment-1997083246),
+with a name that would not be updated by RabbitMQ itself.
 
 ### CQv1 Storage Implementation was Removed