Disable Microsoft.HeadingColons and Microsoft.Percentages, fix Plurals hits
HeadingColons conflicts with this repo's sentence-case heading convention -- same shape as the existing Dashes disable, a house-style conflict rather than a defect. Percentages had zero true positives on the full docs/ tree: it only ever fired on identifier uses of "percent" (cpu.percent, percent resolver), never on an actual spelled-out percentage. Plurals: rewrote the two real hits to always use the plural form instead of the parenthetical (s) construction, per house style.
This commit is contained in:
parent
9a47a837e5
commit
c7c221baeb
3 changed files with 15 additions and 2 deletions
13
.vale.ini
13
.vale.ini
|
|
@ -58,3 +58,16 @@ write-good.E-Prime = NO
|
|||
# Needs an actual rewrite pass through the flagged headings, not a blanket
|
||||
# call either way.
|
||||
Microsoft.HeadingAcronyms = NO
|
||||
|
||||
# --- Ruled on, not wave 2 -- disabled for good, not pending a follow-up pass ---
|
||||
#
|
||||
# Flags this repo's own consistent sentence-case heading convention
|
||||
# ("### Current limitation: state-dir visibility lags topology") for not
|
||||
# capitalizing after the colon. Same shape as Microsoft.Dashes above: a
|
||||
# real house-style conflict, not a defect. Ruled to keep the house style.
|
||||
Microsoft.HeadingColons = NO
|
||||
# Checked every real hit on our docs/ tree: zero true positives. It fires
|
||||
# on the word "percent" used as an identifier (`cpu.percent`, "percent
|
||||
# resolver"), never on an actual spelled-out percentage. A rule with no
|
||||
# observed true positive on this corpus isn't worth keeping enabled.
|
||||
Microsoft.Percentages = NO
|
||||
|
|
|
|||
Loading…
Reference in a new issue