I am torn on this.

I want to agree with the logic.

But many of the best software engineers I know can't spell or format English consistently.

Of course resumes are higher stakes than code comments.

But I care #1 that your resume communicates clearly to me what I need to know to judge whether you would benefit my team. If you typoed something, or your formatting is a bit wonky, even if I notice, I am not likely to care.

(Obviously, an excessive amount of errors can demonstrate a communication issue.)

Another aspect to consider is that weighting English errors strongly can introduce bias against many demographics.

Rather, I find it best to assume good faith, that the candidate prepared their resume to the best of their circumstance. Only evidence to the contrary should hold weight.

Your example likely wouldn't even compile. Get back to me when there's a compiler and testing framework for resumes. Nobody misunderstands when you write "Javascript" once and then "JavaScript" later on. And, even in code, where there are compilers and testing frameworks, bugs happen, even in code written by excellent engineers.

I'm not saying a resume littered with typos is a good thing. But, a couple here and there? Whatever. Tell me you've never made a typo in a document you've written for work.