From 803a52436f2e9547a2ca7729302d3fba20c3e544 Mon Sep 17 00:00:00 2001 From: Bertrand Janin Date: Tue, 4 Apr 2017 09:11:25 -0400 Subject: [PATCH] Fix typo. (cherry picked from commit 6524838950dca5721a7f7e9db3118d9245c64659) --- doc/build/orm/contextual.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/orm/contextual.rst b/doc/build/orm/contextual.rst index fe5e305717..cadfe8e050 100644 --- a/doc/build/orm/contextual.rst +++ b/doc/build/orm/contextual.rst @@ -113,7 +113,7 @@ object is entirely designed to be used in a **non-concurrent** fashion, which in terms of multithreading means "only in one thread at a time". So our above example of :class:`.scoped_session` usage, where the same :class:`.Session` object is maintained across multiple calls, suggests that some process needs -to be in place such that mutltiple calls across many threads don't actually get +to be in place such that multiple calls across many threads don't actually get a handle to the same session. We call this notion **thread local storage**, which means, a special object is used that will maintain a distinct object per each application thread. Python provides this via the -- 2.47.3