[3.14] gh-100305: Deemphasize that `ast.literal_eval` is safe in `eval` documentation...

(cherry picked from commit b3b0cef0c2aacdc616fa48674552ab1e34553835)

Co-authored-by: Ram Vikram Singh <ramvikrams243@gmail.com>
Co-authored-by: Éric <merwok@netwok.org>

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 96b88b38039fa3c453c63a288b372103706ee91a..4b849770c1936ac0dc0a90bfb4fd72025d127001 100644 (file)
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -635,7 +635,7 @@ are always available.  They are listed here in alphabetical order.
    If the given source is a string, then leading and trailing spaces and tabs
    are stripped.
 
-   See :func:`ast.literal_eval` for a function that can safely evaluate strings
+   See :func:`ast.literal_eval` for a function to evaluate strings
    with expressions containing only literals.
 
    .. audit-event:: exec code_object eval