summaryrefslogtreecommitdiff
path: root/doc/build/core
diff options
context:
space:
mode:
authorKarthikeyan Singaravelan <tir.karthi@gmail.com>2020-08-09 10:02:57 +0000
committerKarthikeyan Singaravelan <tir.karthi@gmail.com>2020-08-09 10:02:57 +0000
commit71f14f6de8ee1865fd68d7989f751eed95dde719 (patch)
treeb59ef7821edddcdba1c3782118e7237b6b5e067e /doc/build/core
parentc0685e5f419e203acd5e46f25c90e851e30e6f03 (diff)
downloadsqlalchemy-71f14f6de8ee1865fd68d7989f751eed95dde719.tar.gz
Fix typos
Diffstat (limited to 'doc/build/core')
-rw-r--r--doc/build/core/connections.rst4
-rw-r--r--doc/build/core/tutorial.rst2
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst
index 0e0170d43..6c8e51b7b 100644
--- a/doc/build/core/connections.rst
+++ b/doc/build/core/connections.rst
@@ -248,7 +248,7 @@ and have no effect.
Instead, each statement invoked upon the connection will commit any changes
automatically; it sometimes also means that the connection itself will use
fewer server-side database resources. For this reason and others, "autocommit"
-mode is often desirable for non-tranasctional applications that need to read
+mode is often desirable for non-transactional applications that need to read
individual tables or rows in isolation of a true ACID transaction.
SQLAlchemy dialects can support these isolation levels as well as autocommit to
@@ -271,7 +271,7 @@ certain backend, an error is raised.
For example, to force REPEATABLE READ on a specific connection::
- with engine.connect().execution_options(isolation_level="REPEATBLE READ") as connection:
+ with engine.connect().execution_options(isolation_level="REPEATABLE READ") as connection:
connection.execute(<statement>)
The :paramref:`_engine.Connection.execution_options.isolation_level` option
diff --git a/doc/build/core/tutorial.rst b/doc/build/core/tutorial.rst
index b8faed126..3f4d37d0e 100644
--- a/doc/build/core/tutorial.rst
+++ b/doc/build/core/tutorial.rst
@@ -445,7 +445,7 @@ access:
name: wendy ; fullname: Wendy Williams
To access columns via name using strings, either when the column name is
-progammatically generated, or contains non-ascii characters, the
+programmatically generated, or contains non-ascii characters, the
:attr:`.Row._mapping` view may be used that provides dictionary-like access:
.. sourcecode:: pycon+sql