From 347613241f17f6ab4de17a0c7fc428a20cc76901 Mon Sep 17 00:00:00 2001 From: Isaac To Date: Thu, 6 Feb 2020 10:52:59 -0800 Subject: [PATCH 1/2] This is a typo. --- docs/reqcontext.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reqcontext.rst b/docs/reqcontext.rst index c6f43ce1..f0a6ff84 100644 --- a/docs/reqcontext.rst +++ b/docs/reqcontext.rst @@ -199,7 +199,7 @@ contexts until the ``with`` block exits. print(request.path) # the contexts are popped and teardown functions are called after - # the client with block exists + # the client with block exits Signals ~~~~~~~ From bbba98ce40f0149b8116edcfb719f1155f9c4fd5 Mon Sep 17 00:00:00 2001 From: Isaac To Date: Thu, 6 Feb 2020 12:04:49 -0800 Subject: [PATCH 2/2] A better expression for the intended meaning --- docs/reqcontext.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reqcontext.rst b/docs/reqcontext.rst index f0a6ff84..405bca04 100644 --- a/docs/reqcontext.rst +++ b/docs/reqcontext.rst @@ -251,7 +251,7 @@ point to the unique object bound to each worker behind the scenes as described on this page. Most of the time you don't have to care about that, but there are some -exceptions where it is good to know that this object is an actual proxy: +exceptions where it is good to know that this object is actually a proxy: - The proxy objects cannot fake their type as the actual object types. If you want to perform instance checks, you have to do that on the