DOC: make RST files conform to pandas token usage

doc/source/development/contributing.rst

@@ -134,7 +134,7 @@ want to clone your fork to your machine::
     git remote add upstream https://github.com/pandas-dev/pandas.git
 
 This creates the directory ``pandas-yourname`` and connects your repository to
-the upstream (main project) *pandas* repository.
+the upstream (main project) pandas repository.
 
 Note that performing a shallow clone (with ``--depth==N``, for some ``N`` greater
 or equal to 1) might break some tests and features as ``pd.show_versions()``
@@ -1381,7 +1381,7 @@ using ``.`` as a separator. For example::
 
 will only run the ``GroupByMethods`` benchmark defined in ``groupby.py``.
 
-You can also run the benchmark suite using the version of ``pandas``
+You can also run the benchmark suite using the version of pandas
 already installed in your current Python environment. This can be
 useful if you do not have virtualenv or conda, or are using the
 ``setup.py develop`` approach discussed above; for the in-place build

doc/source/whatsnew/v0.13.0.rst

@@ -46,7 +46,7 @@ API changes
 - Text parser now treats anything that reads like inf ("inf", "Inf", "-Inf",
   "iNf", etc.) as infinity. (:issue:`4220`, :issue:`4219`), affecting
   ``read_table``, ``read_csv``, etc.
-- ``pandas`` now is Python 2/3 compatible without the need for 2to3 thanks to
+- pandas now is Python 2/3 compatible without the need for 2to3 thanks to
   @jtratner. As a result, pandas now uses iterators more extensively. This
   also led to the introduction of substantive parts of the Benjamin
   Peterson's ``six`` library into compat. (:issue:`4384`, :issue:`4375`,

doc/source/whatsnew/v0.14.0.rst

@@ -101,7 +101,7 @@ API changes
     you have a local variable that is *not* a column you must still refer to
     it with the ``'@'`` prefix.
   - You can have an expression like ``df.query('@a < a')`` with no complaints
-    from ``pandas`` about ambiguity of the name ``a``.
+    from pandas about ambiguity of the name ``a``.
   - The top-level :func:`pandas.eval` function does not allow you use the
     ``'@'`` prefix and provides you with an error message telling you so.
   - ``NameResolutionError`` was removed because it isn't necessary anymore.

doc/source/whatsnew/v0.17.1.rst

@@ -8,7 +8,7 @@ Version 0.17.1 (November 21, 2015)
 
 .. note::
 
-   We are proud to announce that *pandas* has become a sponsored project of the (`NumFOCUS organization`_). This will help ensure the success of development of *pandas* as a world-class open-source project.
+   We are proud to announce that pandas has become a sponsored project of the (`NumFOCUS organization`_). This will help ensure the success of development of pandas as a world-class open-source project.
 
 .. _numfocus organization: http://www.numfocus.org/blog/numfocus-announces-new-fiscally-sponsored-project-pandas
 

doc/source/whatsnew/v0.18.0.rst

@@ -1274,7 +1274,7 @@ Bug fixes
 - Bug in ``.groupby`` where a ``KeyError`` was not raised for a wrong column if there was only one row in the dataframe (:issue:`11741`)
 - Bug in ``.read_csv`` with dtype specified on empty data producing an error (:issue:`12048`)
 - Bug in ``.read_csv`` where strings like ``'2E'`` are treated as valid floats (:issue:`12237`)
-- Bug in building *pandas* with debugging symbols (:issue:`12123`)
+- Bug in building pandas with debugging symbols (:issue:`12123`)
 
 
 - Removed ``millisecond`` property of ``DatetimeIndex``. This would always raise a ``ValueError`` (:issue:`12019`).

doc/source/whatsnew/v0.23.0.rst

@@ -454,7 +454,7 @@ These bugs were squashed:
 ``Series.str.cat`` has gained the ``join`` kwarg
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Previously, :meth:`Series.str.cat` did not -- in contrast to most of ``pandas`` -- align :class:`Series` on their index before concatenation (see :issue:`18657`).
+Previously, :meth:`Series.str.cat` did not -- in contrast to most of pandas -- align :class:`Series` on their index before concatenation (see :issue:`18657`).
 The method has now gained a keyword ``join`` to control the manner of alignment, see examples below and :ref:`here <text.concatenate>`.
 
 In v.0.23 ``join`` will default to None (meaning no alignment), but this default will change to ``'left'`` in a future version of pandas.

doc/source/whatsnew/v1.2.0.rst

@@ -188,7 +188,7 @@ Alternatively, you can also use the dtype object:
 Index/column name preservation when aggregating
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-When aggregating using :meth:`concat` or the :class:`DataFrame` constructor, Pandas
+When aggregating using :meth:`concat` or the :class:`DataFrame` constructor, pandas
 will attempt to preserve index (and column) names whenever possible (:issue:`35847`).
 In the case where all inputs share a common name, this name will be assigned to the
 result. When the input names do not all agree, the result will be unnamed. Here is an