make object's 'Content' type more generic (from *bytes.Reader to io.Read...

...er)

I'm thinking that when creating an object with content, the content can be anything that's readable. One gotcha that would need to be documented would be that users passing in a ReadCloser would need to "Close" the "Reader" in their app code. Thoughts?