It's difficult. Technically, your explanation is ambiguous too. For continuous replications, only each new revision _after the request to the changes feed is started is checked.

I would say simply that the filter function acts on the entries in the changes feed, filtering the entries that appear. Developers can call the changes feed with various options if they want more information. I think including the further details is confusing, particularly as we're likely to remove continuous replications from the sync libraries (terrible for battery life).