feedback by mgorny

Author: cfbolz

posts/2021/12/error-message-style-guides.txt

@@ -28,12 +28,15 @@ other programming languages.
 Wonderfully, people answered me with lots of helpful links (`full list`_ at the
 end of the post), thank you everybody! All those sources are very interesting
 and contain many great points, I recommend reading them directly! In this
-post, I'll try to summarize some common themes or topics that I found
+post, I'll try to summarize some common themes or topics that I thought were
 particularly interesting.
 
-Several guides (such as Flix and Flow) point out a 80/20 rule: 80% of the time an error message is
+Several guides (such as Flix and Flow) point out a 80/20 rule: 80% of the times an error message is
 read, the developer knows that message well and knows exactly what to do. For
-this use case it's important that the message is short. On the other hand, 20% of the time this same message will have to be understood by a developer who has never seen it before and is confused, and so the message needs to contain enough information
+this use case it's important that the message is short. On the other hand, 20%
+of the times this same message will have to be understood by a developer who
+has never seen it before and is confused, and so the message needs to contain
+enough information
 to allow them to find out what is going on.
 
 Almost all guides stress the need for plain and simple English, as well as