Wording tweaks

Author: ncoghlan

Doc/howto/argparse.rst

@@ -15,7 +15,7 @@ recommended command-line parsing module in the Python standard library.
 
    There are two other modules that fulfill the same task, namely
    :mod:`getopt` (an equivalent for ``getopt()`` from the C
-   language) and the deprecated :mod:`optparse`.
+   language) and the lower level :mod:`optparse` module.
    Note also that :mod:`argparse` is based on :mod:`optparse`,
    and therefore very similar in terms of usage.
 

Doc/library/argparse.rst

@@ -16,7 +16,7 @@
    While :mod:`argparse` is the recommended standard library module for
    *implementing* command line applications, authors of third party
    command line argument processing libraries may find that the
-   simpler :mod:`optparse` module serves as a better foundation for
+   lower level :mod:`optparse` module serves as a better foundation for
    that use case.
 
 --------------

Doc/whatsnew/3.13.rst

@@ -1655,8 +1655,8 @@ optparse
   While :mod:`argparse` remains preferred for new projects that
   aren't using a third party command line argument processing
   library, there are aspects of the way ``argparse`` works that
-  means ``optparse`` may provide a better foundation for *writing*
-  argument processing libraries.
+  means the lower level ``optparse`` module may provide a better
+  foundation for *writing* argument processing libraries.
   (Contributed by Alyssa Coghlan in :gh:`126225`.)
 
 

Misc/NEWS.d/next/Library/2024-10-31-14-31-36.gh-issue-126225.vTxGXm.rst

@@ -3,4 +3,4 @@ There are legitimate reasons to use one of these modules in preference to
 :mod:`argparse`, and none of these modules are at risk of being removed
 from the standard library. Of the three, ``argparse`` remains the
 recommended default choice, *unless* one of the concerns noted at the top of
-the module documentation applies.
+the ``optparse`` module documentation applies.