diff --git a/content/posts/how-to-write-a-good-bug-report.md b/content/posts/how-to-write-a-good-bug-report.md
index f5376ac..8492bdb 100644
--- a/content/posts/how-to-write-a-good-bug-report.md
+++ b/content/posts/how-to-write-a-good-bug-report.md
@@ -65,24 +65,20 @@ message, if available, or information about your system can easily be obtained
 and put into the report.
 
 Others might not want to bother, or "don't have time" to write good bug
-reports. There are a few issue with this if you wish to have your ticket
-resolved.
+reports.  There are a few issue with this if you wish to have your ticket
+resolved.  Questions you don't answer in this first ticket will eventually
+need to asked some way or another.
 
-Forgetting about the job for a second, in the context of a free software
-project for example, where people often volunteer, they might just not bother
-answering you in return if you don't do any effort.
-
-For my use-case, as I am paid to provide support, the issue is that questions
-you don't answer in this first ticket will eventually need to asked some way
-or another. Every detail you can give is that much time gained avoiding back
-and forth for both parties.
+Every detail you can give is that much time gained avoiding back and forth for
+both parties.  Some projects will even dismiss your tickets if they think it
+would take them too much effort to get useful information out of you.
 
 Sysadmins might know about common issues or errors and ways to fix them, but
 we don't have magical powers (unfortunately?) and we need your help to
-understand the issue.
+understand what's happening.
 
-An unhelpful party is only making the process more painful for all parties
-involved.
+An unhelpful party is only making the process more time consuming for all
+parties involved.
 
 ## What is a bug?