Do you want a no-fuss command-line tool to lint the quality of the prose in your technical documentation project, or in your technical writing projects? Do you want something that has an uncomplicated interface, yet provides rich feedback? Then come learn about proselint.
Are the words in your technical documentation strong, sharp, direct, and powerful? Or are they passive, weasely, and replete with clichés and adverbs? If you want to make them stronger than they are now, then come learn about write-good.
When you&rsquo;re reviewing generated HTML content, broken link&rsquo;s are the last thing you want. However, given the massive amount of documentation in modern projects, manually hunting for broken links isn&rsquo;t practical. So how do you deal with this problem?