spell fix: seperated -> separated
Fix many spelling mistakes in the docs.
Make consistent use of acronyms, and US spellings for serializ*
Merge pull request #7742 from lexual/docs_spell_fix

spell fix: seperated -> separated
Merge pull request #7745 from lexual/docs_fixes

Docs fixes
DOC: Fix typo conncection -> connection
Merge pull request #7747 from ElDeveloper/typo-fix

DOC: Fix typo conncection -> connection
DOC: update RELEASE.md to point to stable whatsnew
ENH: upgrade categoricals to a first class pandas type
     GH3943, GH5313, GH5314, GH7444

ENH: delegate _reduction and ops from Series to the categorical
     to support min/max and raise TypeError on other ops (numerical) and reduction

Add Categorical Properties to Series

Default to 'ordered' Categoricals if values are ordered

Categorical: add level assignments and reordering + changed default for ordered

Add a `Categorical.reorder_levels()` method. Change some naming in `Series`,
so that the methods do not clash with established standards and rename the
other categorical methods accordingly.

Also change the default for `ordered` to True if values + levels are passed
in at creation time.

Initial doc version for working with Categorical data

Categorical: add Categorical.mode() and use that in Series.mode()

Categorical: implement remove_unused_levels()

Categorical: implement value_count() for categorical series

Categorical: make Series.astype("category") work

ENH: add setitem to Categorical

BUG: assigning to levels not in level set now raises ValueError

API: disallow numpy ufuncs with categoricals

Categorical: Categorical assignment to int/obj column

ENH: add support for fillna to Categoricals

API: deprecate old style categorical constructor usage and change default

Before it was possible to pass in precomputed labels/pointer and the
corresponding levels (e.g.: `Categorical([0,1,2], levels=["a","b","c"])`).

This could lead to subtle errors in case of integer categoricals: the
following could be both interpreted as "precomputed pointers and
levels" or "values and levels", but converting it back to a integer
array would result in different arrays:

`np.array(Categorical([1,2], levels=[1,2,3]))`
interpreted as pointers: `[2,3]`
interpreted as values: `[1,2]`

Up to now we would favour old style "pointer and levels" if these
values could be interpreted as such (see code for details...). With
this commit we favour new style "values and levels" and only attempt
to interprete them as "pointers and levels" if "compat=True" is passed
to the constructor.

BREAKS: This will break code which uses Categoricals with "pointer and
levels". A short google search and a search on stackoverflow revealed
no such useage.

Categorical: document constructor changes and small fixes

Categorical: document that inappropriate numpy functions won't work anymore

ENH: concat support
Categorical: Thanks for Jan Schulz for much of the work on Categoricals

Doc: Add Release notes for #7217

DOC: update v0.15.0 notes

Categorical: .codes should be immutable

ERR: codes modification raises ValueError always

Categorical: use Categorical.from_codes() in a few places

Categorical: Fix assigning a Categorical to an existing string column

CLN: CategoricalDtype repr now yields category
DISPLAY: show dtype when displaying Categorical series (for consistency)

BUG: fix groupby with multiple non-compressed categoricals

Categorical: minor doc cleanups

ENH: add a metaclass to CategoricalDtype to provide issubclass support (for select_dtypes)

TST: io/pytables.py tests now raise NotImplementedError for dtype==category

DOC: document the new category dtype in select_dtypes
Merge pull request #7217 from jreback/categorical

WIP: categoricals as an internal CategoricalBlock GH5313