Questions about retroactively applied TTL behaviour

[kpanic9]

Describe the bug

I am a beginner to RabbitMQ and experimenting with RabbitMQ TTL. https://www.rabbitmq.com/docs/ttl#message-ttl-dead-lettering and https://www.rabbitmq.com/docs/ttl#message-ttl-applied-retroactively reads as this behaviour only applies to per-message TTL, not per-queue TTL.
It would be great if it can be updated to reflect that it applies to both TTLs avoiding confusion.

Reproduction steps

1. Read https://www.rabbitmq.com/docs/ttl#message-ttl-dead-lettering and https://www.rabbitmq.com/docs/ttl#message-ttl-applied-retroactively .
   ...

Expected behavior

The docs should mention this behaviour is same for both per-queue and per-message TTL.

Additional context

No response

[michaelklishin]

@kpanic9 you are the only person to ponder this question in many years. Feel free to submit a PR with suggested edits, this is open source software after all.

I'm not going to guess what wording would be clear to a complete beginner in this case.

[michaelklishin]

You can change a message TTL of an existing queue by applying a policy. You cannot update the TTL/expires field of an already published message. Hence this section talks about the scenario where a policy with TTL keys is applied to a queue that already has messages.

In addition, one section immediately follows the other so it's kind of silly to make one link to another.

I do not understand what you are looking for, so please submit a PR and we will see.