Emphasize that we are talking about source compatibility

1 files changed, 8 insertions, 7 deletions

diff --git a/doc/neps/nep-0029-deprecation_policy.rst b/doc/neps/nep-0029-deprecation_policy.rst
index 5fc3a0b0c..93ac7f2ed 100644
--- a/doc/neps/nep-0029-deprecation_policy.rst
+++ b/doc/neps/nep-0029-deprecation_policy.rst
@@ -84,13 +84,14 @@ to drop any given minor version of Python.  This, in turn, could save
 months of unnecessary maintenance burden.
 
 If a project releases immediately after a minor version of Python
-drops out of the support window (or a new version enters), there will
-inevitably be some mismatch in supported versions—but this situation
-should only last until other projects in the ecosystem make releases.
-
-Otherwise, once a project does a minor or major release, it is guaranteed that
-there will be a stable release of all other projects that support the
-same set of Python versions supported by the new release.
+drops out of the support window, there will inevitably be some
+mismatch in supported versions—but this situation should only last
+until other projects in the ecosystem make releases.
+
+Otherwise, once a project does a minor or major release, it is
+guaranteed that there will be a stable release of all other projects
+that, at the source level, support the same set of Python versions
+supported by the new release.
 
 If there is a Python 4 or a NumPy 2 this policy will have to be
 reviewed in light of the community's and projects' best interests.