docs: turn the last one-mould pages into headings that answer a question - #608
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Thank you for following the naming conventions! 🙏 |
3a884d2 to
1382c94
Compare
commit: |
Stacked on #607. This takes
T-06to zero.Most of what was left was the classifier being too narrow, not the pages being wrong. Two corrections, recorded in
corrections.md:Where the byte counts come fromandWhich number moves your billare the same shape as the ones ending on?, and a page built on them is a set of answers.Try it against your numbersandAsk it from your editorboth read as nouns. It is now 89. Words that are evlog's own nouns first (log,route,stream,trace,filter,drain) are deliberately kept out: counting## Route filteringas an imperative would weaken the rule rather than correct it.That cleared 8 pages. The four that remained genuinely argued, and their headings are rewritten: the comparison page now says what you call in a handler rather than
Core API, and the enricher sections are named after the factory you actually call. Inbound anchors follow.Corpus after: 114 clean pages of 120, average 99.7. What is left is 8 findings across 6 pages: two register seams, two unbacked comparisons, two epigram rates, two metronome rhythms.