DOC/BUG: NA string in data gets read as NaN
better docs for `keep_default_na` and `na_values` when used together

I have a field set where "NA" is meaningful, but not meaning "not applicable" (it refers to the name of my school's Homeroom). There's no obvious way to handle this edge case...
On 0.11.0
