7 files changed, 14 insertions, 14 deletions
diff --git a/Doc/c-api/arg.rst b/Doc/c-api/arg.rst
index 3429a4e..28bf046 100644
--- a/Doc/c-api/arg.rst
+++ b/Doc/c-api/arg.rst
@@ -305,7 +305,7 @@ the minimal value for the corresponding signed integer type of the same size.
 ``D`` (:class:`complex`) [Py_complex]
    Convert a Python complex number to a C :c:type:`Py_complex` structure.
 
-.. deprecated:: next
+.. deprecated:: 3.15
 
    For unsigned integer formats ``B``, ``H``, ``I``, ``k`` and ``K``,
    :exc:`DeprecationWarning` is emitted when the value is larger than
diff --git a/Doc/c-api/bytes.rst b/Doc/c-api/bytes.rst
index 0a73c47..9bddfe4 100644
--- a/Doc/c-api/bytes.rst
+++ b/Doc/c-api/bytes.rst
@@ -236,7 +236,7 @@ PyBytesWriter
 The :c:type:`PyBytesWriter` API can be used to create a Python :class:`bytes`
 object.
 
-.. versionadded:: next
+.. versionadded:: 3.15
 
 .. c:type:: PyBytesWriter
 
diff --git a/Doc/c-api/complex.rst b/Doc/c-api/complex.rst
index aa91b85..d135637 100644
--- a/Doc/c-api/complex.rst
+++ b/Doc/c-api/complex.rst
@@ -16,7 +16,7 @@ Complex Number Objects
 
       The complex number value, using the C :c:type:`Py_complex` representation.
 
-      .. deprecated-removed:: next 3.20
+      .. deprecated-removed:: 3.15 3.20
          Use :c:func:`PyComplex_AsCComplex` and
          :c:func:`PyComplex_FromCComplex` to convert a
          Python complex number to/from the C :c:type:`Py_complex`
diff --git a/Doc/c-api/object.rst b/Doc/c-api/object.rst
index 5685792..8629b76 100644
--- a/Doc/c-api/object.rst
+++ b/Doc/c-api/object.rst
@@ -201,7 +201,7 @@ Object Protocol
    This case can arise from forgetting ``NULL`` checks and would delete the
    attribute.
 
-   .. versionchanged:: next
+   .. versionchanged:: 3.15
       Must not be called with NULL value if an exception is set.
 
 
@@ -226,7 +226,7 @@ Object Protocol
    For more details, see :c:func:`PyUnicode_InternFromString`, which may be
    used internally to create a key object.
 
-   .. versionchanged:: next
+   .. versionchanged:: 3.15
       Must not be called with NULL value if an exception is set.
 
 
diff --git a/Doc/c-api/stable.rst b/Doc/c-api/stable.rst
index 8fed4b6..2901666 100644
--- a/Doc/c-api/stable.rst
+++ b/Doc/c-api/stable.rst
@@ -202,7 +202,7 @@ third-party distributors.
 ABI Checking
 ============
 
-.. versionadded:: next
+.. versionadded:: 3.15
 
 Python includes a rudimentary check for ABI compatibility.
 
@@ -249,7 +249,7 @@ The full API is described below for advanced use cases.
    may lead to crashes.
    In particular, it is not safe to examine the raised exception.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 .. c:macro:: PyABIInfo_VAR(NAME)
 
@@ -266,7 +266,7 @@ The full API is described below for advanced use cases.
           PyABIInfo_DEFAULT_ABI_VERSION
       }
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 .. c:type:: PyABIInfo
 
@@ -352,7 +352,7 @@ The full API is described below for advanced use cases.
          values of macros such as :c:macro:`Py_LIMITED_API`,
          :c:macro:`PY_VERSION_HEX` and :c:macro:`Py_GIL_DISABLED`.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 
 .. _limited-api-list:
diff --git a/Doc/c-api/sys.rst b/Doc/c-api/sys.rst
index 9a5e26d..336e3ef 100644
--- a/Doc/c-api/sys.rst
+++ b/Doc/c-api/sys.rst
@@ -268,7 +268,7 @@ accessible to C code.  They all work with the current interpreter thread's
    If the non-existing object should not be treated as a failure, you can use
    :c:func:`PySys_GetOptionalAttr` instead.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 .. c:function:: PyObject *PySys_GetAttrString(const char *name)
 
@@ -279,7 +279,7 @@ accessible to C code.  They all work with the current interpreter thread's
    If the non-existing object should not be treated as a failure, you can use
    :c:func:`PySys_GetOptionalAttrString` instead.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 .. c:function:: int PySys_GetOptionalAttr(PyObject *name, PyObject **result)
 
@@ -293,7 +293,7 @@ accessible to C code.  They all work with the current interpreter thread's
    * Set an exception, set *\*result* to ``NULL``, and return ``-1``,
      if an error occurred.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 .. c:function:: int PySys_GetOptionalAttrString(const char *name, PyObject **result)
 
@@ -301,7 +301,7 @@ accessible to C code.  They all work with the current interpreter thread's
    specified as a :c:expr:`const char*` UTF-8 encoded bytes string,
    rather than a :c:expr:`PyObject*`.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 .. c:function:: PyObject *PySys_GetObject(const char *name)
 
diff --git a/Doc/c-api/tuple.rst b/Doc/c-api/tuple.rst
index 65f8334..14a7c05 100644
--- a/Doc/c-api/tuple.rst
+++ b/Doc/c-api/tuple.rst
@@ -47,7 +47,7 @@ Tuple Objects
    On success, return a new reference.
    On error, set an exception and return ``NULL``.
 
-   .. versionadded:: next
+   .. versionadded:: 3.15
 
 
 .. c:function:: PyObject* PyTuple_Pack(Py_ssize_t n, ...)