Page 12: The chart lists, for the Thug occupation, Coercion as a basic ability and Coercion as a specialty thereof. I am sure you meant intimidation. This would be less egregious if the error wasn't reproduced in the description on page 20. Also, I'm pretty sure that the guy who rides a horse is a member of the cavalry, and that this particular biblical allusion is unintentional.
A decision was made last minute to make sure no ability would seem to mirror OGL games too much (because Eldritch RPG is not OGL). This decision created some issues in late drafts that were missed.
As for the cavalry, yep, you are absolutely right. Jesus, that was dumb!
Page 13: Oh, here's "page xx" again. Right column, just above "For Example:."
Yep, all of those errors were noted too late. I promise It won't happen ever again in future product.
Page 14, sidebar: "See if any of the basic abilities are close to the idea, and name [it? them?] whatever you want."
Yes, that sentence could be improved.
Page 14: Also, under the example calculation for passive defense points, I think there is an arithmetical error in resilience. It is correct that 2xResistance (12) + Willpower (4)=16. However, his Arcanum dice chain should only be D4+D4, for an additional 8, and a final value of 24, rather than 26. Or, perhaps I have misunderstood.
No, you're right, it is an error in the arithmetic.
Page 18: Coercion>Coercion, again. Okay, I guess, potentially, this could have been intentional, but I really hope not. It's just repeated so damned many times, I begin to doubt my assumption that abilities are named in a sensible way. On to the right column: the Engineering specialty under Knowledge is listed three times. No other specialization gets this treatment, so I guess it's unintentional.
The first issue is due to the fact that we changed the Ability name from Intimidation to Coercion. Originally that would have been "Intimidation > Coercion". It should have been reversed. The second issue is due to somebody really liking Engineering as a skill. Heh. The skill succession lists were a brainstorm to give ideas on specializations and masteries for the game, which are infinitely customizable and changeable. But yes, I agree it was probably overkill listing Engineering as a specialization of knowledge three times on our example list.
I'm sure the ERP community will expand and improve on this list over time.