summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2014-11-20 18:40:46 -0500
committerMike Bayer <mike_mp@zzzcomputing.com>2014-11-20 18:40:46 -0500
commit41f4fbbe350008aac67532641e8eba6b7dc16cd0 (patch)
tree5b612ca8a076bd5d78ecb58c07daf4fc8ef962ed
parent1b7ffaa175775bb7d24b95fb39f7c3c052c23127 (diff)
downloadalembic-41f4fbbe350008aac67532641e8eba6b7dc16cd0.tar.gz
- typo
-rw-r--r--docs/build/tutorial.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/build/tutorial.rst b/docs/build/tutorial.rst
index 84297f1..7b7f256 100644
--- a/docs/build/tutorial.rst
+++ b/docs/build/tutorial.rst
@@ -1405,9 +1405,9 @@ Consider if we merged into our source repository another code branch which conta
a revision for another table called ``shopping_cart``. This revision was made
against our first Alembic revision, the one that generated ``account``. After
loading the second source tree in, a new file
-``27c6a30d7c24_add_accont_table.py`` exists within our ``versions`` directory.
+``27c6a30d7c24_add_shopping_cart_table.py`` exists within our ``versions`` directory.
Both it, as well as ``ae1027a6acf_add_a_column.py``, reference
-``1975ea83b712`` as the "downgrade" revision. To illustrate::
+``1975ea83b712_add_account_table.py`` as the "downgrade" revision. To illustrate::
# main source tree:
1975ea83b712 (add account table) -> ae1027a6acf (add a column)