- don't scare off developers with the word "advanced" here

Change-Id: I72a0295634e228bacf6c92088e650183f91e4585
(cherry picked from commit 399988aaed401ea6fc69aa580b9b71c236a30f16)

diff --git a/doc/build/orm/session_basics.rst b/doc/build/orm/session_basics.rst
index de0dd1e3a8fec35ccb2c4f5566d4d451cbd6c5ff..391c6131dcf1f4f86b7eca56e704ac51d87f6400 100644 (file)
--- a/doc/build/orm/session_basics.rst
+++ b/doc/build/orm/session_basics.rst
@@ -362,9 +362,12 @@ Keep the lifecycle of the session (and usually the transaction)
         finally:
             session.close()
 
-The advanced developer will try to keep the details of session, transaction
-and exception management as far as possible from the details of the program
-doing its work.   For example, we can further separate concerns using a `context manager <http://docs.python.org/3/library/contextlib.html#contextlib.contextmanager>`_::
+The most comprehensive approach, recommended for more substantial applications,
+will try to keep the details of session, transaction and exception management
+as far as possible from the details of the program doing its work.   For
+example, we can further separate concerns using a `context manager
+<http://docs.python.org/3/library/co
+ntextlib.html#contextlib.contextmanager>`_::
 
     ### another way (but again *not the only way*) to do it ###