reverts v0.22 and fixes code blocks and typos in v0.23

Author: datajanko

doc/source/whatsnew/v0.22.0.txt

@@ -7,3 +7,8 @@ This is a major release from 0.21.1 and includes a number of API changes,
 deprecations, new features, enhancements, and performance improvements along
 with a large number of bug fixes. We recommend that all users upgrade to this
 version.
+
+.. _whatsnew_0220.api_breaking:
+
+Backwards incompatible API changes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

doc/source/whatsnew/v0.23.0.txt

@@ -125,11 +125,11 @@ Current Behavior
 ``.assign()`` accepts dependent arguments
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The :func:`DataFrame.assign()` now accepts dependent kwargs. In earlier versions this throws a Keyerror exception anymore. (:issue: `14207)
+The :func:`DataFrame.assign()` now accepts dependent kwargs. (:issue: `14207)
 
-Specifically, defining a new column inside assign may be referenced in the same assign statement if a callable is used. For example
+Specifically, defining a new column inside ``.assign()`` may be referenced in the same assign statement if a callable is used. For example
 
-.. code-block:: ipython     
+.. ipython:: python     
 
     In [3]: df = pd.DataFrame({'A': [1, 2, 3]})
 
@@ -143,8 +143,10 @@ Specifically, defining a new column inside assign may be referenced in the same
 .. warning::
 
 This may subtly change the behavior of your code when you're
-using ``assign`` to update an existing column. Previously, callables
-refering to other variables being updated would get the "old" values
+using ``.assign()`` to update an existing column. Previously, callables
+referring to other variables being updated would get the "old" values
+
+Previous Behaviour:
 
 .. code-block:: ipython
 
@@ -157,9 +159,9 @@ refering to other variables being updated would get the "old" values
     1  3 -2
     2  4 -3
 
-Now, callables will get the "new" value
+New Behaviour:
 
-.. code-block:: ipython
+.. ipython:: python
 
 
     In [4]: df = pd.DataFrame({"A": [1, 2, 3]})