I don't know if you meant to imply this, but if you think having "Javascript" in one place, and "JavaScript" in another is a "glaring mistake," I think you might just be too damn picky.
void f(const std::vector<std::string>& arg);
void f(const std::vector<std::string> arg);
You could say that this is a poor design of C++, but pick your language, there's usually something like this somewhere. At least in any of the commonly used languages. (Although, C++ is particularly bad about it.)
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.
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.
You can go pretty far down this rabbit hole and be a grammar Nazi. All it shows is that you’re a grammar Nazi.