clarifying iterator trait documentation

I found these things to be ambiguous, or at least worth stating explicitly to reduce the amount a user/developer needs to think about the API.
As above, this is geared towards the user, not the implementor. That first sentence should say "can be thought of" instead of "should be thought of", as the reader is by no means required to think of it that way.