cleaned up a bit of the diagnostics answer text.

Removed confusing bit of first-person wording and filled in some words that were missing.

Author: pnkfelix

posts/inside-rust/2022-07-29-compiler-team-2022-midyear-report.md

@@ -762,7 +762,7 @@ and in other cases, what we learn of their usage is informing our plans going fo
 
 The most common thing is people picking up a project that’s too advanced for them, which demotivates them. We try to both steer them away beforehands and to closely mentor them as they work on things. A cleaner codebase with more machinery for non-standard things (like typechecking opportunistically in the parser, to give an example of something impossible to do today) would allow some of the things people have tried to be done by almost anyone.
 
-@estebank believes that diagnostics are super important and everyone's concern. I think that efforts like librarification could unblock very powerful heuristics to massively improve here, but such a project *shouldn't* be started *only* for diagnostics improvements (as there's plenty of things to do already).
+@estebank believes that diagnostics are super important and everyone's concern. Efforts like librarification could unblock very powerful heuristics to massively improve our user experience here, but such a project *shouldn't* be started *only* for diagnostics improvements (as there's plenty of things to do already).
 
 What would make @estebank change their focus to something else? Simply put: Seeing no one complain about how hard Rust is to learn and seeing absolutely no new "confusing errors" complaints.