vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

docs: disable write-good.TooWordy -- 100% dictionary mismatch on this corpus

Browse source 
Checked all 114 hits on the full docs/ tree by hand, not sampled: every
single one flags a precise, normal technical/formal word from
write-good's default corporate-bloat wordlist (validate, monitor,
therefore, however, multiple, additional, previously, subsequent,
equivalent, sufficient, exclusively, finalize, terminate, enumerate,
minimize, consolidate, eliminate, acquire, evaluate, satisfy,
implement, "it IS"/"it is"/"it was", "all of", "is responsible for",
"in addition"), not an actual verbose phrase. None of the genuinely
wordy multi-word bloat this rule exists to catch (due to the fact
that, in order to, at the present time, for the purpose of) appears
even once. Rewriting 114 instances of precise vocabulary into vaguer
prose to satisfy a dictionary mismatch would make the docs worse, not
better -- same shape as the Microsoft.Percentages/Microsoft.Dashes/
Microsoft.HeadingColons entries already in this file's "ruled on, not
wave 2" section.

Full evidence (the actual word/phrase breakdown, and why the 13
closest hits -- "it is"/"it was"/"all of"/"is responsible for"/"in
addition" -- were manually read in context and still don't count) was
already posted on hyperhive#4042; this just applies the conclusion.

Verified: nix shell nixpkgs#vale --command sh -c 'vale sync && vale
docs' before/after -- 908 -> 794 warnings (-114, exactly the disabled
rule's own hit count), 49 errors unchanged (all Microsoft.Avoid/
Contractions, unrelated to this rule), zero remaining TooWordy hits.
This commit is contained in:
iris 2026-09-08 11:52:51 +02:00 • committed by mara
commit 08e67520ed
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
.vale.ini
View file

@ -76,3 +76,12 @@ Microsoft.HeadingColons = NO
# 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
# Checked all 114 hits by hand, not sampled: every single one flags a
# precise, normal technical/formal word from write-good's default
# corporate-bloat wordlist ("validate", "monitor", "therefore",
# "however", "multiple", ...), not an actual verbose phrase -- none of
# the genuinely wordy multi-word bloat this rule exists to catch ("due
# to the fact that", "in order to", "at the present time") appears even
# once. Rewriting precise vocabulary into vaguer prose to satisfy a
# dictionary mismatch would make the docs worse, not better.
write-good.TooWordy = NO