updates

doc/source/development/policies.rst

@@ -11,25 +11,31 @@ Version Policy
 
 .. versionchanged:: 1.0.0
 
-Pandas uses a variant of `SemVer`_ to govern deprecations, API compatibility, and version numbering.
+Pandas uses a loose variant of semantic versioning (`SemVer`_) to govern
+deprecations, API compatibility, and version numbering.
 
 A pandas release number is made up of ``MAJOR.MINOR.PATCH``.
 
-API breaking changes should only occur in **major** releases. Theses changes will be documented,
-with clear guidance on what is changing, why it's changing, and how to migrate existing code to the
-new behavior.
+API breaking changes should only occur in **major** releases. Theses changes
+will be documented, with clear guidance on what is changing, why it's changing,
+and how to migrate existing code to the new behavior.
 
-Whenever possible, a deprecation path will be provided rather than an outright breaking change.
+Whenever possible, a deprecation path will be provided rather than an outright
+breaking change.
 
-Pandas will introduce deprecations in **minor** releases. These deprecations will
-preserve the existing behavior while emitting a warning that provide guidance
+Pandas will introduce deprecations in **minor** releases. These deprecations
+will preserve the existing behavior while emitting a warning that provide
+guidance on:
 
 * How to achieve similar behavior if an alternative is available
 * The pandas version in which the deprecation will be enforced.
 
 We will not introduce new deprecations in patch releases.
 
-Deprecations will only be enforced in **major** releases.
+Deprecations will only be enforced in **major** releases. For example, if a
+behavior is deprecated in pandas 1.2.0, it will continue to work, with a
+warning, for all releases in the 1.x series. The behavior will change and the
+deprecation removed in the next next major release (2.0.0).
 
 .. note::