diff options
author | Daniel Fortunov <asqui@users.noreply.github.com> | 2020-09-06 12:50:13 +0100 |
---|---|---|
committer | Daniele Varrazzo <daniele.varrazzo@gmail.com> | 2020-09-06 17:23:37 +0100 |
commit | 171371da5a2cfab5cbd1455c0858212191d0d065 (patch) | |
tree | c540aa7f6036b8558b891bb0ffa94a1d38f91598 /doc/src | |
parent | b203be11a69789a50da828a0a5e4c15d2dcf99d4 (diff) | |
download | psycopg2-171371da5a2cfab5cbd1455c0858212191d0d065.tar.gz |
Minor spelling and grammar corrections for 195b254
Diffstat (limited to 'doc/src')
-rw-r--r-- | doc/src/usage.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/usage.rst b/doc/src/usage.rst index 5239518..0677a5b 100644 --- a/doc/src/usage.rst +++ b/doc/src/usage.rst @@ -750,10 +750,10 @@ until a call to the `~connection.rollback()` method. The connection is responsible for terminating its transaction, calling either the `~connection.commit()` or `~connection.rollback()` method. Committed -changes are immediately made persistent into the database. If he connection +changes are immediately made persistent in the database. If the connection is closed (using the `~connection.close()` method) or destroyed (using `!del` -or letting it falling out of scope) while a transaction is in progress, the -server will discard the transaction. However doing so is not adviceable: +or by letting it fall out of scope) while a transaction is in progress, the +server will discard the transaction. However doing so is not advisable: middleware such as PgBouncer_ may see the connection closed uncleanly and dispose of it. |