From bb294497558f96c92253a4a68129a7c7984d3af9 Mon Sep 17 00:00:00 2001 From: Adrian Moennich Date: Sat, 9 Jan 2016 20:35:19 +0100 Subject: Fix typo in session docs --- doc/build/orm/session_basics.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/orm/session_basics.rst b/doc/build/orm/session_basics.rst index dd1162216..0f96ba50a 100644 --- a/doc/build/orm/session_basics.rst +++ b/doc/build/orm/session_basics.rst @@ -247,7 +247,7 @@ While there's no one-size-fits-all recommendation for how transaction scope should be determined, there are common patterns. Especially if one is writing a web application, the choice is pretty much established. -A web application is the easiest case because such an appication is already +A web application is the easiest case because such an application is already constructed around a single, consistent scope - this is the **request**, which represents an incoming request from a browser, the processing of that request to formulate a response, and finally the delivery of that -- cgit v1.2.1