From: Bertrand Janin Date: Tue, 4 Apr 2017 13:11:25 +0000 (-0400) Subject: Fix typo. X-Git-Tag: rel_1_2_0b1~117 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6524838950dca5721a7f7e9db3118d9245c64659;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Fix typo. --- 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