diff --git a/reference/oci8/functions/oci-execute.xml b/reference/oci8/functions/oci-execute.xml
index 541eea3312..3881908507 100644
--- a/reference/oci8/functions/oci-execute.xml
+++ b/reference/oci8/functions/oci-execute.xml
@@ -92,11 +92,11 @@
        </table>
       </para>
       <para>
-       When using <constant>OCI_NO_AUTO_COMMIT</constant> mode, you're
-       creating a transaction. Transactions are automatically rolled
-       back when the connection is closed, or when the script ends.
-       Explicitly call <function>oci_commit</function> to commit a
-       transaction, or <function>oci_rollback</function> to abort it.
+       Using <constant>OCI_NO_AUTO_COMMIT</constant> mode starts a
+       transaction. Transactions are automatically rolled back when
+       the connection is closed, or when the script ends.  Explicitly
+       call <function>oci_commit</function> to commit a transaction,
+       or <function>oci_rollback</function> to abort it.
       </para>
       <para>
        When inserting or updating data, using transactions is
@@ -104,15 +104,16 @@
        reasons.
       </para>
       <para>
-       If you use <constant>OCI_NO_AUTO_COMMIT</constant> mode for any
-       statement including queries, and you do not subsequently
-       call <function>oci_commit</function>
-       or <function>oci_rollback</function>, then OCI8 will perform a
-       rollback at the end of the script even if no data was changed.
-       To avoid an unnecessary rollback, many scripts do not
+       If <constant>OCI_NO_AUTO_COMMIT</constant> mode is used for any
+       statement including queries, and 
+        <function>oci_commit</function>
+       or <function>oci_rollback</function> is not subsequently
+       called, then OCI8 will perform a rollback at the end of the
+       script even if no data was changed.  To avoid an unnecessary
+       rollback, many scripts do not
        use <constant>OCI_NO_AUTO_COMMIT</constant> mode for queries or
        PL/SQL.  Be careful to ensure the appropriate transactional
-       consistency for your application when
+       consistency for the application when
        using <function>oci_execute</function> with different modes in
        the same script.
       </para>
@@ -253,10 +254,9 @@ for ($i = 1; $i <= oci_num_fields($stid); ++$i) {
   &reftitle.notes;
   <note>
    <para>
-    Transactions are automatically rolled back when you close the
-    connection, or when the script ends, whichever is soonest. You
-    need to explicitly call <function>oci_commit</function> to commit
-    the transaction.
+    Transactions are automatically rolled back when connections are
+    closed, or when the script ends, whichever is soonest.  Explicitly
+    call <function>oci_commit</function> to commit a transaction.
    </para>
    <para>
     Any call to <function>oci_execute</function> that uses
@@ -280,9 +280,8 @@ for ($i = 1; $i <= oci_num_fields($stid); ++$i) {
   </note>
   <note>
    <para>
-    In PHP versions before 5.0.0 you must
-    use <function>ociexecute</function> instead.
-    &oci.name.compat.note;
+    In PHP versions before 5.0.0 use <function>ociexecute</function>
+    instead.  &oci.name.compat.note;
    </para>
   </note>
  </refsect1>