this is mostly targeted at the oauth1 docs. i haven't gotten into oauth2 yet.

there are 2 rather annoying bits:

1. all the args dealing with tokens use token. it would be a lot better if they used terms like request_token and access_token.
2. when there are dicts/objects involved, I think it might make more sense to have a package that lists the various 'interfaces' that are expected.

for example, save_request_token in 'request_validator' expects token to be a dictionary that includes at least 3 terms. meanwhile save_verifier expects token to be a string and implements a verifier dict that has several oauth_ prefixed items. while it's great that these are documented very well, the repetition of terms and concepts in difference contexts can be very confusing.