In this edition of The Linux Week in Review, I will demonstrate how to use tools readily available in GNU/Linux to do quality assurance checks on texts before submitting them to a professor, publisher, code reviewer, reader, editor, or other authority. The principles that I will present are applicable to ANYTHING, not just writing.
I have learned the hard way that quality assurance takes time, patience, diligence, and commitment. It means slowing things way down, and doing quality assurance in small manageable chunks. I have learned these lessons through thousands of hours of writing, proofreading, and also through trial-and-error. What I am presenting here is the best system that I have come up with, and the one that allows the smallest percentage of errors to get through.