dispatchAfterResponse should use dispatch not dispatchNow

[Braunson]

While queueing a job I went to use dispatchAfterResponse which as one would expect should queue the job after the response. However it instead ran immediately skipping being queued (database driver) entirely. Under the hook it's calling dispatchNow() but I would expect it to call dispatch()?

Perhaps the wording could be changed to reflect what happens, i.e. dispatchAfterResponse -> dispatchNowAfterResponse and dispatchAfterResponse would instead use dispatch() under the hood.

What's your experience with this, confusing or not?