How to Write a PR Description That Sounds Native

How to Write a PR Description That Actually Sounds Native I've reviewed thousands of PRs from developers across 6 countries. The code is usually fine. The English? That's where things get interesting. Here's a collection of real patterns I've seen (anonymized), what native speakers actually think when they read them, and how to fix each one. The "Please Kindly" Pattern What non-native speakers write: Please kindly review this PR. I have made some changes to the authentication module. Please let me know if you have any questions. Thank you for your time. What native speakers think: "This reads like a customer service email, not a PR description." What to write instead: ## What Refactored the auth module to use JWT refresh tokens. ## Why Session tokens were expiring mid-workflow (see #142). Refresh tokens let us extend sessions without re-auth. ## How - Added `refreshToken()` to AuthService - Updated middleware to auto-refresh on 401 - Migration: new `refresh_tokens` table The rule: PR d