From 3e5df79ec659b30d4517f28f8d16457f72bf329c Mon Sep 17 00:00:00 2001
From: Mark Amery <markamery@btinternet.com>
Date: Sun, 7 Jan 2018 12:13:15 +0000
Subject: [PATCH] Change (broken) declarative base link into (working) ref

(cherry picked from commit 7dfa693afdba75dfe5094cf39b2c74958ef3153e)
---
 docs/build/autogenerate.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/build/autogenerate.rst b/docs/build/autogenerate.rst
index a5bd5d1c..a15a7f9c 100644
--- a/docs/build/autogenerate.rst
+++ b/docs/build/autogenerate.rst
@@ -9,7 +9,7 @@ review and modify these by hand as needed, then proceed normally.
 
 To use autogenerate, we first need to modify our ``env.py`` so that it gets access
 to a table metadata object that contains the target.  Suppose our application
-has a `declarative base <http://www.sqlalchemy.org/docs/orm/extensions/declarative.html#synopsis>`_
+has a :ref:`declarative base <sqla:declarative_toplevel>`
 in ``myapp.mymodel``.  This base contains a :class:`~sqlalchemy.schema.MetaData` object which
 contains :class:`~sqlalchemy.schema.Table` objects defining our database.  We make sure this
 is loaded in ``env.py`` and then passed to :meth:`.EnvironmentContext.configure` via the
-- 
2.47.2