CONSISTENCY MATTERS IN DOCS

You're changing one example of a line that appears dozens of times in the docs. Every time anybody on the team submits a docs diff, I find myself repeating the same thing over and over... YOU must be the editor. It is YOUR responsibility to maintain consistency of voice and style. @geekbrother, here you are ruining the consistency by introducing a change that is not reflected elsewhere in the docs.

Please, please, please keep this in mind going forward. I am getting increasingly frustrated by the fact that nobody on the team seems to take this responsibility seriously.

Please do not pass docs diffs to me until @varun has taken a look

Second point – because very few people on the team are able to submit or review docs diffs, and because I get very frustrated when passed a docs diff, we have a new system in place where all docs diffs go through @varun first. Please do not pass me docs diffs until @varun has taken a look, because the chance of getting a response like this is >80% (just looking at the numbers).

You need a lot more details in your test plan

The diff only changes behavior if brew install node@16 return a non-zero exit code. In order to evaluate this diff, we need to know in what scenarios brew install node@16 will return a non-zero exit code. @geekbrother, you'll need to provide this info. It would also be helpful to understand what problem exactly you're solving here, or what issue you encountered that led you to put up this diff.

What's the problem that this diff solves? Need more context