From 68a7b78cd5185cbd9456f42c15ecf872a7c16f44 Mon Sep 17 00:00:00 2001
From: DerSchinken <53398996+DerSchinken@users.noreply.github.com>
Date: Thu, 18 Jan 2024 21:04:40 +0100
Subject: [PATCH] gh-112092: clarify unstable ABI recompilation requirements
 (#112093)

Use different versions in the examples for when extensions do and do not need to be recompiled to make the examples easier to understand.
---
 Doc/c-api/stable.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Doc/c-api/stable.rst b/Doc/c-api/stable.rst
index 63a100a6f26..5b9e43874c7 100644
--- a/Doc/c-api/stable.rst
+++ b/Doc/c-api/stable.rst
@@ -16,7 +16,7 @@ CPython's Application Binary Interface (ABI) is forward- and
 backwards-compatible across a minor release (if these are compiled the same
 way; see :ref:`stable-abi-platform` below).
 So, code compiled for Python 3.10.0 will work on 3.10.8 and vice versa,
-but will need to be compiled separately for 3.9.x and 3.10.x.
+but will need to be compiled separately for 3.9.x and 3.11.x.
 
 There are two tiers of C API with different stability expectations: