diff options
| author | Adrian Moennich <adrian@planetcoding.net> | 2016-01-09 20:35:19 +0100 |
|---|---|---|
| committer | Adrian Moennich <adrian@planetcoding.net> | 2016-01-09 20:35:19 +0100 |
| commit | bb294497558f96c92253a4a68129a7c7984d3af9 (patch) | |
| tree | fe729195f8afe1dc9f45eba5b18b51adf2893e1f | |
| parent | c7ae0daf0ed24e2697d6f948db2d9fdc5953c795 (diff) | |
| download | sqlalchemy-bb294497558f96c92253a4a68129a7c7984d3af9.tar.gz | |
Fix typo in session docspr/226
| -rw-r--r-- | doc/build/orm/session_basics.rst | 2 |
1 files changed, 1 insertions, 1 deletions
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 |