The title of the article cites bad grammar, but the example doesn't have any grammatical problems. It has clear typos and questionable abbreviations but it doesn't have any of the bad grammar signs that grate on me, like comprise vs. compose or over utilization of "utilize" where "use" would do just fine.
You might say that "let's circle back" is annoying business jargon, but it is a very common phrase and aside from the typos correctly applied in this example.
Not even in the northern hemisphere. Celestial navigation is about shooting altitudes for known bright stars. At least three ideally five. This could include Polaris, but it doesn't need to. Source: watched some old training videos about celestial navigation after reading Fate is the Hunter a while back.
That core idea is simple. But the details, such as credit and debit having the opposite meaning to casual bank account accounting, and the use of a variety of accounts makes things not intuitive.
There are different categories of things you might see:
1. This is wrong. I can tell from reading your code that it doesn't do what the description of this PR or the name of a test or some other indicator shows its supposed to do. This should be communicated in a tone of "you must not merge this".
2. This violates our agreed-upon style or best practices. The strictness of enforcement is part of that agreement and company culture. At my current company, this would be communicated along the lines of "this is not how we prefer to do this, so unless you have a good reason why our standard method is wrong, change it"
3. This is confusing to me, or I have a suggestion for improvement. This should be communicated as a suggestion or general feedback. If you're getting miffed about people not taking the suggestions, maybe it's actually in a category above, or maybe you need to adjust your own assumptions about how much stylistic consistency to insist on, since it sounds like you don't have a consensus.
4. You are new, either to software engineering or at least to this company, and your style is inconsistent with how things are done in this code. This is the same as #3 but should be communicated more strongly and depending on your company normals may be effectively a requirement.