From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 15 Feb 2021 16:21:41 +0000 (-0500)
Subject: fix repeated footnote
X-Git-Tag: rel_1_4_0b3~6
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0698992bfd5eaa5d2fe99e279589c3f5819dc7d7;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

fix repeated footnote

Change-Id: Ibd8239907c3cf747d0d9a0fb670e37c9913871f8
---

diff --git a/doc/build/tutorial/data.rst b/doc/build/tutorial/data.rst
index 5da8b8667b..d006a9f852 100644
--- a/doc/build/tutorial/data.rst
+++ b/doc/build/tutorial/data.rst
@@ -1870,7 +1870,7 @@ Parameter Ordered Updates
 Another MySQL-only behavior is that the order of parameters in the SET clause
 of an UPDATE actually impacts the evaluation of each expression.   For this use
 case, the :meth:`_sql.Update.ordered_values` method accepts a sequence of
-tuples so that this order may be controlled [1]_::
+tuples so that this order may be controlled [2]_::
 
   >>> update_stmt = (
   ...     update(some_table).
@@ -1883,7 +1883,7 @@ tuples so that this order may be controlled [1]_::
   {opensql}UPDATE some_table SET y=:y, x=(some_table.y + :y_1)
 
 
-.. [1] While Python dictionaries are
+.. [2] While Python dictionaries are
    `guaranteed to be insert ordered
    <https://mail.python.org/pipermail/python-dev/2017-December/151283.html>`_
    as of Python 3.7, the