Change documentation to reflect the new docstring adjustments in 3.13

Author: decorator-factory

Doc/library/functions.rst

@@ -340,8 +340,12 @@ are always available.  They are listed here in alphabetical order.
    It is needed to unambiguous :ref:`filter <warning-filter>` syntax warnings
    by module name.
 
-   This function raises :exc:`SyntaxError` if the compiled source is invalid,
-   and :exc:`ValueError` if the source contains null bytes.
+   This function raises the following exceptions:
+
+   - :exc:`SyntaxError` if the compiled source is invalid
+   - :exc:`ValueError` if the source contains null bytes
+   - :exc:`UnicodeDecodeError` if the source code contains docstrings that
+     cannot be encoded as UTF-8 and the optimization level is below ``2``
 
    If you want to parse Python code into its AST representation, see
    :func:`ast.parse`.
@@ -373,6 +377,11 @@ are always available.  They are listed here in alphabetical order.
       Previously, :exc:`TypeError` was raised when null bytes were encountered
       in *source*.
 
+   .. versionchanged:: 3.13
+      :exc:`UnicodeDecodeError` is now raised if any docstring in *source*
+      contains surrogates (like ``\ud800``) and therefore cannot be encoded
+      as UTF-8.
+
    .. versionadded:: 3.8
       ``ast.PyCF_ALLOW_TOP_LEVEL_AWAIT`` can now be passed in flags to enable
       support for top-level ``await``, ``async for``, and ``async with``.

Doc/tutorial/controlflow.rst

@@ -1039,17 +1039,8 @@ blank, visually separating the summary from the rest of the description.  The
 following lines should be one or more paragraphs describing the object's calling
 conventions, its side effects, etc.
 
-The Python parser does not strip indentation from multi-line string literals in
-Python, so tools that process documentation have to strip indentation if
-desired.  This is done using the following convention. The first non-blank line
-*after* the first line of the string determines the amount of indentation for
-the entire documentation string.  (We can't use the first line since it is
-generally adjacent to the string's opening quotes so its indentation is not
-apparent in the string literal.)  Whitespace "equivalent" to this indentation is
-then stripped from the start of all lines of the string.  Lines that are
-indented less should not occur, but if they occur all their leading whitespace
-should be stripped.  Equivalence of whitespace should be tested after expansion
-of tabs (to 8 spaces, normally).
+The Python parser strips indentation from multi-line string literals when they
+serve as module, class, or function docstrings.
 
 Here is an example of a multi-line docstring::