s/State/ScrollController/

we really should factor out these docs into an interface at the foundation layer.

some of these should be plural, e.g. zero or more [UserScrollNotification]s

actually this will fire when it hasn't changed its scroll position, but would have. Basically it's what translates into a glow. On iOS this never fires.

Ah, good to know. :)

this description of OverscrollNotification is incorrect, I believe.

Fixed.

"the sooner it stops" is probably less odd-sounding that "the faster it slows down". :-)

I think modeling is the American spelling

that => that a

[Here and elsewhere]

It would be helpful to explain when the dragDetails are non-null, i.e. the drag gesture ended with a velocity that was too small to trigger a ballistic scroll.

Done.

ot => to

The docs for particle/position/velocity talk about a "particle". We should probably explain the particle angle here or define those methods in terms of the simulation's position; and then mention that position is usually mapped to scroll offset.

Maybe call attention to of() and ensureVisible() here, since those methods will not appear with ListView et al.

It's not clear what this means. The property is used to map from input gestures to scroll offset deltas?

Maybe see-also ensureVisible()