chore(2.0): revisions to release notes (#6921)

Minor revisions to release note.

## Checklist

- [x] Change(s) are motivated and described in the PR description.
- [x] Testing strategy is described if automated tests are not included
in the PR.
- [x] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist

- [x] Title is accurate.
- [x] No unnecessary changes are introduced.
- [x] Description motivates each change.
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [x] Testing strategy adequately addresses listed risk(s).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] Release note makes sense to a user of the library.
- [x] Reviewer has explicitly acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment.
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
- [x] If this PR touches code that signs or publishes builds or
packages, or handles credentials of any kind, I've requested a review
from `@DataDog/security-design-and-guidance`.
- [x] This PR doesn't touch any of that.

Author: majorgreys

docs/spelling_wordlist.txt

@@ -29,6 +29,7 @@ aredis
 args
 ascii
 asgi
+asm
 async
 asyncio
 asyncpg

releasenotes/notes/add-312-73857cf79c64c924.yaml

@@ -10,18 +10,18 @@ issues:
   - |
     aiobotocore: Python 3.12 is not supported.
   - |
-    flask-caching: Python 3.12 is not supported.
+    asm: IAST for Python 3.12 is not supported.
   - |
-    opentelemetry-api: Python 3.12 is not supported.
+    flask-caching: Python 3.12 is not supported.
   - |
     openai/langchain: Python 3.12 is not supported.
   - |
-    opentracing: Python 3.12 is not supported.
+    opentelemetry-api: Python 3.12 is not supported.
   - |
-    pynamodb: Python 3.12 is not supported.
+    opentracing: Python 3.12 is not supported.
   - |
     pyramid: Python 3.12 is not supported.
   - |
-    redis/redis-py-cluster: Python 3.12 is not supported.
+    pynamodb: Python 3.12 is not supported.
   - |
-    ASM: IAST for Python 3.12 is not supported.
+    redis/redis-py-cluster: Python 3.12 is not supported.

releasenotes/notes/release-2.0-3af0045e2261bd02.yaml

@@ -1,19 +1,20 @@
 ---
 prelude: >
   The Datadog APM Python team is happy to announce the release of v2.0.0 of ddtrace.
-  This release introduces a formal :ref:`versioning support policy<versioning_support_levels>` for the major
-  versions of the ddtrace library, drops support for Python 2.7, 3.5, and 3.6, and adds support for Python 3.12.
+  This release drops support for Python 2.7, 3.5, and 3.6. This release adds
+  support for Python 3.12.
 
 
   .. important::
-    ddtrace v2.0.0 drops support for Python 2.7, 3.5, and 3.6. Users running these unsupported
-    Python versions should consider upgrading their Python version or continue using ddtrace v1
-    of the ddtrace library, which is now in maintenance mode and will only receive bug fixes. 
 
-    Before upgrading to v2.0.0, we recommend users install
-    ``ddtrace>=1.18.0,<2.0.0`` and enable deprecation warnings. All removals to
-    the library interface and environment variables were deprecated on the 1.x
-    branch.
+    If you are on version of Python not supported by v2, we will continue to
+    maintain the ddtrace v1 with bug fixes.
+
+
+  .. note::
+    Before upgrading to v2.0.0, we recommend users install ``ddtrace~=1.18.0``
+    and enable deprecation warnings. All removals to the library interface and
+    environment variables in v2 were deprecated in the 1.x release line.
 
 
   .. note::
@@ -35,13 +36,15 @@ prelude: >
   has been removed and the ddtrace logger will log to stdout by default, or a log file
   as specified using ``DD_TRACE_LOG_FILE``.
 
-  Setting the environment variable ``DD_TRACE_PROPAGATION_STYLE='b3'`` has been removed.
-  Please use `DD_TRACE_PROPAGATION_STYLE='b3multi'`` instead.
+
+  Setting the environment variable ``DD_TRACE_PROPAGATION_STYLE='b3'`` to enable
+  B3 propagation has been removed. Please use
+  ``DD_TRACE_PROPAGATION_STYLE='b3multi'`` instead.
 
 
-  Removed legacy environment variables
+  Removed deprecated environment variables
 
-  ************************************
+  ****************************************
 
   These environment variables have been removed. In all cases the same
   functionality is provided by other environment variables and replacements are
@@ -75,9 +78,9 @@ prelude: >
   .. _removed-2.0-tracing-interfaces:
 
 
-  Removed legacy tracing interfaces
+  Removed deprecated library interfaces
 
-  *********************************
+  *************************************
 
   These methods and module attributes have been removed. Where the same
   functionality is provided by a different public method or module attribute, a