The teams i'm on have a rule about nits, "only fix nits if you are going to touch the code again". So if there's a misspelled word in a comment or a formatting/

The teams i'm on have a rule about nits, "only fix nits if you are going to touch the code again". So if there's a misspelled word in a comment or a formatting/code conciseness cleanup, it can be ignored unless there are other actual bugs to fix. It works out pretty well, the marginal cost of fixing the nits is very low when there's other changes to be made, so they get done. If they aren't addressed because there are no actual problems with the code, those things will get addressed later. (all the members of the team tend to take cleanup passes occasionally when they aren't feeling up to the deep work stuff but still want to do something productivish). The net effect is the codebase stays reasonably tidy without feeling bogged down in the "bureaucracy" of nitpicking.