You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -43,9 +43,14 @@ Focus on human-readable text. In rough priority order:
43
43
-**Inconsistent tone** — the project uses a professional but approachable tone. Flag text that is overly formal, too casual, or inconsistent with surrounding text.
44
44
-**Inconsistent terminology** — the same concept described with different words in different places (e.g. mixing "hook" and "check" for the same thing).
45
45
46
+
## Spelling conventions
47
+
48
+
This project uses **British English** spelling (e.g. "behaviour", "colour", "initialise"). Do not change British spellings to American equivalents. When writing new text, prefer British spelling to stay consistent with the existing codebase.
49
+
46
50
## What to ignore
47
51
48
52
-**Identifier names** — variable names, function names, class names, and other code identifiers. These follow naming conventions, not grammar rules.
49
53
-**Third-party content** — text in vendored files, generated files, or lock files.
50
54
-**Technical jargon used correctly** — domain-specific terms (e.g. "pyproject.toml", "pre-commit", "lockfile") are not spelling errors.
51
55
-**Intentional abbreviations** — standard abbreviations like "config", "deps", "args" are fine.
56
+
-**British English spellings** — words like "behaviour", "colour", "favourite", "initialise" are correct in this project. Do not flag or change these.
0 commit comments