update changelog
diff --git a/03-kmsg-cont-order.patch b/03-kmsg-cont-order.patch
index eb2d4c8..94d4a63 100644
--- a/03-kmsg-cont-order.patch
+++ b/03-kmsg-cont-order.patch
@@ -5,14 +5,15 @@
 case the console is locked the fragment must be queued up in the cont
 buffer.
 
-When the continuation line is complete and no part of it was written to the
-console up to this point, we just store the entire line as record.
+If the continuation line is complete and no part of it was written to the
+console up to this point, we can just store the entire line as a regular
+record and free the buffer earlier.
 
-If the console is busy and other messages are still queued up, we should not
-try flush fragments of continuation lines, but sort them after the queued
-up messages.
+If the console is busy and earlier messages are already held back, we
+should not try flush fragments of continuation lines, but store them after
+the queued up messages.
 
-This keeps the console output better readable in case printk()s case against
+This keeps the console output better readable in case printk()s race against
 each other, or we receive over-long continuation lines we need to flush.
 
 Signed-off-by: Kay Sievers <kay@vrfy.org>