Section 8.7 of the JMS 2.0 spec has a malformed sentence

Nobody has claimed this yet.

There is a confusing/malformed sentence in section 8.7 of the JMS 2.0 spec (also present in section 4.5.2 of 1.1 spec). The sentence is "Well behaved listeners should catch
such exceptions and attempt to divert messages causing them to some form
of application-specific 'unprocessable message' destination."

Is this trying to say ".. and attempt to divert messages to some form of application-specific ...
? In other words I feel like the words "causing them" should be removed from this sentence. In any case, it needs to be reworded somehow to make the meaning clear, in my opinion.

=== Larger quote:

8.7\. Receiving messages asynchronously
...

It is possible for a listener to throw a RuntimeException; however, this is
considered a client programming error. Well behaved listeners should catch
such exceptions and attempt to divert messages causing them to some form
of application-specific 'unprocessable message' destination.

Thanks!
John Lindwall
#### Environment
N/A
#### Affected Versions
[1.1, 2.0]

Start by reading section 8.7 of the JMS 2.0 specification and the corresponding section 4.5.2 of the 1.1 specification, focusing on the quoted sentence and its surrounding context. Update the wording so the intended relationship between exceptions and diverting messages is unambiguous in both versions, then verify that the revised sentence preserves the specification's meaning.

Written by the indexing model from the issue text.