Post History

Source: https://writers.stackexchange.com/a/26862
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

I have to edit my own books frequently. But I publish ebooks -- which allows you to update the ebook file if you find errors.

With printed stuff, you really need a second pair of eyes to find typos. The risks are too great -- especially if you are paying for advance copies.

On the other hand, print-on-demand services (like Createspace) do allow you to update the manuscript after publication.

If you are not confident of your quality control process, you might want to look into a distribution method which allows you to update the manuscript after publication date.

Frankly I worry more about typos than about inconsistent punctuation because one typo lowers a reader's confidence about the book's quality.

Also, technical books and manuals have to undergo additional vetting from an editor who does technical review-- because a mistake can result in bad information. At the same time, all technical publishers know that errata will occur and often have a web page on the company site listing issues and corrections.

A typical developer buys a programming book with the near certainty that it will usually contain technical errors. But they don't sweat it as much because it will help them with general concepts, and generally they can spot the error -- even though it may not run properly. The typical developer wouldn't mind an occasional misspelled word as long as the code works or the technical knowledge is basically right. Also, many IT books are out-of-date by the time they are published, making it all the more important to check for errata.

Original score: 0