remove ancient engine.execute() reference from main engine doc

Change-Id: I51a30c2e53ad7da3e1209b5623388dd2aea7589c
(cherry picked from commit c16ed9dd24a091dbaba4683ae2f04a3f199416bf)

diff --git a/doc/build/core/engines.rst b/doc/build/core/engines.rst
index b0dc2a3cf59d25f483ab55ade960b78781ee6e9b..d52ad6b13c137ca0564fced460b246d43651d6b4 100644 (file)
--- a/doc/build/core/engines.rst
+++ b/doc/build/core/engines.rst
@@ -26,13 +26,16 @@ Creating an engine is just a matter of issuing a single call,
     engine = create_engine("postgresql://scott:tiger@localhost:5432/mydatabase")
 
 The above engine creates a :class:`.Dialect` object tailored towards
-PostgreSQL, as well as a :class:`_pool.Pool` object which will establish a DBAPI
-connection at ``localhost:5432`` when a connection request is first received.
-Note that the :class:`_engine.Engine` and its underlying :class:`_pool.Pool` do **not**
-establish the first actual DBAPI connection until the :meth:`_engine.Engine.connect`
-method is called, or an operation which is dependent on this method such as
-:meth:`_engine.Engine.execute` is invoked. In this way, :class:`_engine.Engine` and
-:class:`_pool.Pool` can be said to have a *lazy initialization* behavior.
+PostgreSQL, as well as a :class:`_pool.Pool` object which will establish a
+DBAPI connection at ``localhost:5432`` when a connection request is first
+received. Note that the :class:`_engine.Engine` and its underlying
+:class:`_pool.Pool` do **not** establish the first actual DBAPI connection
+until the :meth:`_engine.Engine.connect` or :meth:`_engine.Engine.begin`
+methods are called.  Either of these methods may also be invoked by other
+SQLAlchemy :class:`_engine.Engine` dependent objects such as the ORM
+:class:`_orm.Session` object when they first require database connectivity.
+In this way, :class:`_engine.Engine` and :class:`_pool.Pool` can be said to
+have a *lazy initialization* behavior.
 
 The :class:`_engine.Engine`, once created, can either be used directly to interact with the database,
 or can be passed to a :class:`.Session` object to work with the ORM.   This section