As a technical writer, I use Vale every day. It helps protect consistency and style. I wrote a brief tutorial here: https://passo.uno/posts/first-steps-with-the-vale-prose-lint...
To over-simplify, vale runs hundreds of pre-built regexes that suggest changes to over-used phrases, likely function names etc etc. Google etc have pre-built fairly good defaults I suspect.
(To be fair this is trying to get consistency across huge document bases, and will never replace a human's authentic voice for communication. But sometimes you just want to make sure there are the same number of blueberries in each muffin)
Ok - my mission after next - get something like this brought in at work
* creating my own style guide
* using one of the existing ones
We have a DevDocsReadme that has some style rules we enforce manually. Is the best way to get going with vale to start with that doc and write rules for that?
Can you apply rules to asciidoc and markdown source docs, or do you have to apply it to the end product (HTML, etc)?
It seems like such a cool idea. Any pointers to 'get started' for existing largeish documentation sets would be much appreciated. (I will read your tutorial, @remoquete.)