Many authors of technical books don't publish errata on the Web. It just means that there's no way of telling what's right and what's wrong. Of course, they don't make as many mistakes as I do, but that's because Mr Ritchie has the unfair advantage of having actually designed the language, which is definitely cheating. If you use the Errata as a tool to help you gain more understanding about C, just as you use the book for that same purpose, you'll be onto a winning strategy. This is not intended to be merely a guilt list with which you can smack me around the head in comp.lang.c .
Errors come in various flavours.
Most of the errors I've found so far are typographical - font flaws, tabulation trouble, that sort of thing. It won't always be possible to follow the 'fix' directions without making a complete mess of the book. The fixes basically indicate the corrective action that you would perform if you had complete control over the layout and content of the book. If there is a 'Reported By' column for a particular chapter, it means that at least one of the errors in that chapter was reported by a gentle reader, or by one of my esteemed co-authors. So - here endeth the Introduction.