Here are four examples that show why bible typos are the best typos

We all have to deal with typos. Here at DeadState, we do our best to avoid them and even then they still slip by, even after a draft goes through a team of editors.

But when a typo appears in a sacred or historical text, the impact is a little serious – for some people anyway. We just think it’s incredibly funny.

(h/t: io9)

Look:

The Printer’s Bible, 1612: Psalm 119:161 reads “Printers have persecuted me without a cause” rather than “Princes have persecuted…”
The Wicked Bible, 1631: In the Ten Commandments the word “not” is missing from the Seventh Commandment.
The Fools Bible, 1631: Psalm 14 reads, “The fool hath said in his heart there is a God,” rather than “The fool hath said in his heart there is no God.”
The Vinegar Bible, 1717: Although rife with errors, the most-known one is in the chapter heading for Luke 20, which reads “The Parable of the Vinegar” instead of “The Parable of the Vineyard.”