Typo

diff --git a/doc/build/content/session.txt b/doc/build/content/session.txt
index 6f7016deeb6616f1150eb656d9829b15379c3587..7f8d06f90672773dead966bd77c04992bad3c568 100644 (file)
--- a/doc/build/content/session.txt
+++ b/doc/build/content/session.txt
@@ -238,7 +238,7 @@ The solution is to use proper cascading:
 
 When the `Session` is used with its default configuration, the flush step is nearly always done transparently.  Specifically, the flush occurs before any individual `Query` is issued, as well as within the `commit()` call before the transaction is committed.  It also occurs before a SAVEPOINT is issued when `begin_nested()` is used.  The "flush-on-Query" aspect of the behavior can be disabled by constructing `sessionmaker()` with the flag `autoflush=False`.
 
-Regardless of the autoflush setting, a flush can always be forced by issing `flush()`:
+Regardless of the autoflush setting, a flush can always be forced by issuing `flush()`:
     
     {python}
     session.flush()