No phrase or sentence is set in capitals
A node is written in the ordinary case of its language, and a name quoted from the code keeps its spelling. Outside such a name, capitals may stand on one word or on two running (REST API); a phrase or a sentence, three words or more running, is never set in capitals: what must stand out is said in the words.
Set in capitals, a phrase reads as more binding than the words around it, although every word of a rule binds alike, and a reader who meets capitals on every line starts reading the capitals instead of the sentence. A style spreads by imitation, because a rule is written like the rules around it, so one rule in capitals is copied by its neighbours. A word or two in capitals are most often an abbreviation or a name keeping its own spelling, which no check tells from a word stressed, so they are left alone. Three words running are seldom anything but stress, and a run of abbreviations as long is rare enough to be worded around.
The links made to it
The decisions taken on it
- Problem
The check refused two words in capitals running, so two abbreviations side by side, such as REST API, were refused as stress although this rule let an abbreviation keep its capitals; and a single word stressed in capitals, which this rule forbade, no check could tell from an abbreviation.
- Ruling
The owner: a single word, or two running, may stand in capitals; a phrase or a sentence, from three words running, never does.
The tests bound to it
- skills/tools/test/unit/validate.test.ts · s-m6upmfq64kw5h4r refuses three words or more running in capitals, letters beyond ASCII included, two words left out