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 5b02a3d..17e1c3d 100644
--- a/content/posts/how-to-write-a-good-bug-report.md
+++ b/content/posts/how-to-write-a-good-bug-report.md
@@ -44,16 +44,17 @@ able to do with the information.
 
 Why would you need to write a bug report/file a ticket in the first place?
 
-What first comes to mind is that sysadmins might not know you have issues. And
-it would probably be beneficial for you, and possibly others, that you tell
-them.
+What first comes to mind is that sysadmins might not know you have issues.
+And it would probably be beneficial for you, and possibly others, that you
+tell them.
 
-A ticket is also helpful to be able to track the progress. This might help
-future you encountering the same issue again be able to fix it yourself, or to
-refer to it later on.
+A ticket is also helpful to be able to track the progress.  This will also
+help other users encountering the same issue and allow them to fix it
+themselves, or allow you to refer to it in a follow-up ticket, ("You know,
+_that_ bug I talked to you about six months ago.")
 
 It is also helpful to track the resolution of an issue, ("What happened to my
-issue?"). Some issues will get fixed and closed, some will not, some might be
+issue?").  Some issues will get fixed and closed, some will not, some might be
 closed for _reasons_, without getting fixed.
 
 ## Why write a good bug report?