doc fixes

Author: tworec

doc/source/io.rst

@@ -4451,25 +4451,25 @@ The key functions are:
 Supported Data Types
 ++++++++++++++++++++
 
-Pandas supports these all `BigQuery data types <https://cloud.google.com/bigquery/data-types>`__:
+Pandas supports all these `BigQuery data types <https://cloud.google.com/bigquery/data-types>`__:
 ``STRING``, ``INTEGER`` (64bit), ``FLOAT`` (64 bit), ``BOOLEAN`` and
 ``TIMESTAMP`` (microsecond precision). Data types ``BYTES`` and ``RECORD``
 are not supported.
 
 Integer and boolean ``NA`` handling
 +++++++++++++++++++++++++++++++++++
 
-.. versionadded:: 0.19
+.. versionadded:: 0.20.0
 
 Since all columns in BigQuery queries are nullable, and NumPy lacks of ``NA``
 support for integer and boolean types, this module will store ``INTEGER`` or
 ``BOOLEAN`` columns with at least one ``NULL`` value as ``dtype=object``.
 Otherwise those columns will be stored as ``dtype=int64`` or ``dtype=bool``
 respectively.
 
-This is opposite to default pandas behaviour which will promote integer
+This is opposite to default pandas behavior which will promote integer
 type to float in order to store NAs. See the :ref:`gotchas<gotchas.intna>`
-for detailed explaination.
+for detailed explanation.
 
 While this trade-off works well for most cases, it breaks down for storing
 values greater than 2**53. Such values in BigQuery can represent identifiers

doc/source/whatsnew/v0.20.0.txt

@@ -81,4 +81,4 @@ Performance Improvements
 Bug Fixes
 ~~~~~~~~~
 
-- The :func:`pandas.io.gbq.to_gbq` method now stores ``INTEGER`` columns as ``dtype=object`` if they contain ``NULL`` values. Othewise they are stored as ``int64``. This prevents precision lost for integers greather than 2**53. Furthermore ``FLOAT`` columns with values above 10**4 are no more casted to ``int64`` which also caused precision lost (:issue: `14064`).
+- The :func:`~DataFrame.to_gbq` method now stores ``INTEGER`` columns as ``dtype=object`` if they contain ``NULL`` values. Otherwise they are stored as ``int64``. This prevents precision lost for integers greater than 2**53. Furthermore ``FLOAT`` columns with values above 10**4 are no more casted to ``int64`` which also caused precision lost (:issue: `14064`).