From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Wed, 28 Sep 2022 17:42:28 +0000 (-0700)
Subject: fixup policy docs (GH-97618)
X-Git-Tag: v3.11.0~60
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f0cbc6c18ea5c072b629df4aa300cfb0c862b111;p=thirdparty%2FPython%2Fcpython.git

fixup policy docs (GH-97618)

(cherry picked from commit 9a404b173e57ce171a867cfc3776cdf88d6c553f)

Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
---

diff --git a/Doc/library/asyncio-policy.rst b/Doc/library/asyncio-policy.rst
index ef6a0588506b..d528db72fb82 100644
--- a/Doc/library/asyncio-policy.rst
+++ b/Doc/library/asyncio-policy.rst
@@ -7,9 +7,14 @@
 Policies
 ========
 
-An event loop policy is a global per-process object that controls
-the management of the event loop. Each event loop has a default
-policy, which can be changed and customized using the policy API.
+An event loop policy is a global object
+used to get and set the current :ref:`event loop <asyncio-event-loop>`,
+as well as create new event loops.
+The default policy can be :ref:`replaced <asyncio-policy-get-set>` with
+:ref:`built-in alternatives <asyncio-policy-builtin>`
+to use different event loop implementations,
+or substituted by a :ref:`custom policy <asyncio-custom-policies>`
+that can override these behaviors.
 
 A policy defines the notion of *context* and manages a
 separate event loop per context. The default policy