Code review friction rarely stems from poor wording — it stems from teams lacking shared norms. Engineering managers should establish three things: severity signals (blocking vs. non-blocking comments), a clear scope of what gets reviewed, and an escalation path for disagreements. Automating style concerns with linters removes unnecessary human conflict. Moving architectural discussions upstream, before code is written, reduces defensiveness at review time. The fix is structural, not linguistic.