Correct for the INSERT statement, typos

Change-Id: I036f3eb9b5e591515920678bc9a76f707fda142c
(cherry picked from commit c85378d9841177b067a93c564edb1787703c6595)

diff --git a/doc/build/orm/persistence_techniques.rst b/doc/build/orm/persistence_techniques.rst
index 541f3e8fe1f9d7b760e03eabc9243c3655083131..28f327c8e167c0f40368d91797506bd55793aa01 100644 (file)
--- a/doc/build/orm/persistence_techniques.rst
+++ b/doc/build/orm/persistence_techniques.rst
@@ -239,10 +239,11 @@ columns should be fetched immediately upon INSERT and sometimes UPDATE::
 
         __mapper_args__ = {"eager_defaults": True}
 
-Above, an INSERT statement will render "NOW()" as the value of "timestamp",
-and the statement will also include the "timestamp" and "special_identifier"
-columns within the RETURNING clause so they are available immediately.
-On the PostgreSQL database, an INSERT for the above table will look like:
+Above, an INSERT statement that does not specify explicit values for
+"timestamp" or "special_identifier" from the client side will include the
+"timestamp" and "special_identifier" columns within the RETURNING clause so
+they are available immediately. On the PostgreSQL database, an INSERT for the
+above table will look like:
 
 .. sourcecode:: sql
 
@@ -272,7 +273,7 @@ they are marked as "expired".
 If the :paramref:`.orm.mapper.eager_defaults` is still used, and the backend
 database does not support RETURNING or an equivalent, the ORM will emit this
 SELECT statement immediately following the INSERT statement.   This is often
-undesireable as it adds additional SELECT statements to the flush process that
+undesirable as it adds additional SELECT statements to the flush process that
 may not be needed.  Using the above mapping with the
 :paramref:`.orm.mapper.eager_defaults` flag set to True against MySQL results
 in SQL like this upon flush (minus the comment, which is for clarification only):