summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorFederico Caselli <cfederico87@gmail.com>2020-05-23 00:11:46 +0200
committerFederico Caselli <cfederico87@gmail.com>2020-05-23 00:11:46 +0200
commit2632a8db05d69607260d412852f7cc5c0ac0f368 (patch)
tree6d8dde9fcbdee9e16e876a101bc63883b906e423 /doc
parent3fb0eb5a156ab7dbe19d82717dd197d9d22e64f1 (diff)
downloadsqlalchemy-2632a8db05d69607260d412852f7cc5c0ac0f368.tar.gz
fix typo in reference documentation
Change-Id: I5720635863f0d8a8ebfa4ddc51008bb93c1067b4
Diffstat (limited to 'doc')
-rw-r--r--doc/build/changelog/migration_13.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/changelog/migration_13.rst b/doc/build/changelog/migration_13.rst
index 78ac21fb5..6e2913350 100644
--- a/doc/build/changelog/migration_13.rst
+++ b/doc/build/changelog/migration_13.rst
@@ -1672,7 +1672,7 @@ However, the current situation is that :class:`.Sequence` has been repurposed
on SQL Server specifically in order to affect the "start" and "increment"
parameters for the ``IDENTITY`` specification on a primary key column. In order
to make the transition towards normal sequences being available as well,
-using :class:.`.Sequence` will emit a deprecation warning throughout the
+using :class:`.Sequence` will emit a deprecation warning throughout the
1.3 series. In order to affect "start" and "increment", use the
new ``mssql_identity_start`` and ``mssql_identity_increment`` parameters
on :class:`_schema.Column`::