If you feel like you can't help it and need to post typos, I don't mind, but let's keep them all in one thread. Just list the Chapter and page number and the error here.

Chapter 1
pg 25: ...then you might ust as easily... [typo]

pg 25,26: [code examples not formatted as code]

pg 27: ... it's HTML content was set to "Wow"... [grammar]

Chapter 2:
pg 64: #c extent will retun the earliest... [typo]

pg 68: [variable 'yScale' not formatted as code]

pg 70: ...use of pregenerated content. [typo, missing dash]

Chapter 3:
pg 75: [.html() method not formatted as code]

pg 77: Here we see an ifsie, ... [quote made-up word]

pg 79: ... it's position in the array,... [grammar]

pg 79: ...is important because it we don't... [extraneous]

pg 85: This require using the quantize scale [grammar]

Excellent! The only one I'd take issue with is "ifsie" which I've heard people actually use in talks to refer to their inline if statements (perhaps with a different spelling, though) but a quick Google search shows that's not a common thing, so I'll pull it. All words are made up, it just depends on whether or not enough people use them.

Oh, I have no problem at all with your usage; I had never heard it called such, but it was catchy. Just quote it.

(Page numbers are from D3.js_in_Action_v4_MEAP.pdf)

Chapter 4, p.98
flat layout of data in graphical manner
should be
flat layout of data in a graphical manner

Chapter 4, p.101
having more or less friends
s/b
having more or fewer friends

I think these are fixed, Steve, and that we just haven't had a MEAP update recently, but I'll double-check.

Page 29: figure 1.11 caption. Should it read "magnifying glass" not "hourglass"?
Love the book so far.

Chapter 1, section 1.5, page 67. "Users who feels like they're exploring rather than reading"