Hmm, that is a good point that `useActionState` accepts a reducer-like function (although I think it's async in this case?). And yeah, half of Redux's terminol

Hmm, that is a good point that `useActionState` accepts a reducer-like function (although I think it's async in this case?). And yeah, half of Redux's terminology is simply because the existing Flux Architecture libraries from the prior year all used those terms. There were several debates in the issues about whether to name them "actions", "events", or something else, and the conclusion was "let's just stick with the existing Flux terminology": - https://github.com/reduxjs/redux/issues/891#issuecomment-147666329 https://github.com/reduxjs/redux/issues/891#issuecomment-147... FWIW, as I've revamped the Redux docs over the years, I have specifically made sure we describe the "actions === events" aspect: - https://redux.js.org/style-guide/#model-actions-as-events-not-setters https://redux.js.org/style-guide/#model-actions-as-events-no... - https://redux.js.org/tutorials/essentials/part-1-overview-concepts#actions https://redux.js.org/tutorials/essentials/part-1-overview-co...