Doc polishing

Author: garyrussell

src/reference/asciidoc/kafka.adoc

@@ -1989,9 +1989,9 @@ When a deserializer fails to deserialize a message, Spring has no way to handle
 To solve this problem, version 2.2 introduced the `ErrorHandlingDeserializer2`.
 This deserializer delegates to a real deserializer (key or value).
 If the delegate fails to deserialize the record content, the `ErrorHandlingDeserializer2` returns a `null` value and a `DeserializationException` in a header, containing the cause and raw bytes.
-When using a record-level `MessageListener`, if either the key or value contains a `DeserializationException` header, the container's `ErrorHandler` is called with the failed `ConsumerRecord`; the record is not passed to the listener.
+When using a record-level `MessageListener`, if the `ConsumerRecord` contains a `DeserializationException` header for either the key or value, the container's `ErrorHandler` is called with the failed `ConsumerRecord`; the record is not passed to the listener.
 
-Alternatively, you can configure a `failedDeserializationFunction` which is a `BiConsumer<byte[], Headers, T>`.
+Alternatively, you can configure the `ErrorHandlingDeserializer2` to create a custom value by providing a `failedDeserializationFunction` which is a `BiConsumer<byte[], Headers, T>`.
 This function is invoked to create an instance of `T` which is passed to the listener, as normal.
 The raw record value and headers are provided to the function.
 The `DeserializationException` can be found (as a serialized Java object) in headers; see the javadocs for the `ErrorHandlingDeserializer2` for more information.