fix: typos in doc/build/api (#909)

diff --git a/docs/build/api/autogenerate.rst b/docs/build/api/autogenerate.rst
index 9d7214e6225781b4a3c06fa26e2e29d0ca3c254b..7d8043e895cb866483c25d5757e0f70b0ae6c217 100644 (file)
--- 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 1d1181b9a74abf619b5945376afd04c9fe16482c..6dd8111b213c1092a5217abbd1c21f2c2ec02724 100644 (file)
--- 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: