From: Kevin Kirsche Date: Sat, 11 Sep 2021 20:37:23 +0000 (-0400) Subject: fix: typos in doc/build/api (#909) X-Git-Tag: rel_1_7_2~8 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=791beb8cbdeea6b02641ce00b0a637d5283e189f;p=thirdparty%2Fsqlalchemy%2Falembic.git fix: typos in doc/build/api (#909) --- diff --git a/docs/build/api/autogenerate.rst b/docs/build/api/autogenerate.rst index 9d7214e6..7d8043e8 100644 --- a/docs/build/api/autogenerate.rst +++ b/docs/build/api/autogenerate.rst @@ -380,7 +380,7 @@ it runs. The resulting migration structure would look like this:: Given the above, the following guidelines should be considered when the ``env.py`` script calls upon :meth:`.MigrationContext.run_migrations` -mutiple times when running autogenerate: +multiple times when running autogenerate: * If the ``process_revision_directives`` hook aims to **add elements based on inspection of the current database / diff --git a/docs/build/api/config.rst b/docs/build/api/config.rst index 1d1181b9..6dd8111b 100644 --- a/docs/build/api/config.rst +++ b/docs/build/api/config.rst @@ -18,7 +18,7 @@ it is needed for the following use cases: with the actual script files in a migration environment * to create an :class:`.EnvironmentContext`, which allows you to actually run the ``env.py`` module within the migration environment -* to programatically run any of the commands in the :ref:`alembic.command.toplevel` +* to programmatically run any of the commands in the :ref:`alembic.command.toplevel` module. The :class:`.Config` is *not* needed for these cases: