Fix cross-references in changelogs

3 files changed, 15 insertions, 15 deletions

diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst
index 8b72ef288..15c78a3dc 100644
--- a/doc/build/changelog/changelog_08.rst
+++ b/doc/build/changelog/changelog_08.rst
@@ -82,7 +82,7 @@
         errors on MySQL as it is not understood - the same behavior will also
         apply to the ``initially`` keyword.  In 0.8, the keywords will remain
         ignored but a warning is emitted.   Additionally, the ``match`` keyword
-        now raises a :class:`.CompileError` on 0.9 and emits a warning on 0.8;
+        now raises a :exc:`.CompileError` on 0.9 and emits a warning on 0.8;
         this keyword is not only silently ignored by MySQL but also breaks
         the ON UPDATE/ON DELETE options.
 
@@ -259,7 +259,7 @@
         :tags: bug, sql
         :versions: 0.9.0b1
 
-        The :meth:`.Operators.notin_` operator added in 0.8 now properly
+        The :meth:`.ColumnOperators.notin_` operator added in 0.8 now properly
         produces the negation of the expression "IN" returns
         when used against an empty collection.
 
@@ -330,7 +330,7 @@
         since the element relies on dialect-specific compilation constructs,
         notably the ``__getitem__()`` operator as used with a Postgresql
         ``ARRAY`` element.  The fix also adds a new exception class
-        :class:`.UnsupportedCompilationError` which is raised in those cases
+        :exc:`.UnsupportedCompilationError` which is raised in those cases
         where a compiler is asked to compile something it doesn't know
         how to.
 
@@ -406,7 +406,7 @@
         :tickets: 2764
         :versions: 0.9.0b1
 
-        Added :class:`.BIGINT` to the list of type names that can be
+        Added :class:`sqlalchemy.types.BIGINT` to the list of type names that can be
         reflected by the SQLite dialect; courtesy Russell Stuart.
 
     .. change::
@@ -1416,7 +1416,7 @@
     .. change::
         :tags: postgresql, bug
 
-      Fixed bug in :func:`.postgresql.array` construct whereby using it
+      Fixed bug in :class:`~sqlalchemy.dialects.postgresql.array()` construct whereby using it
       inside of an :func:`.expression.insert` construct would produce an
       error regarding a parameter issue in the ``self_group()`` method.
 
@@ -1568,7 +1568,7 @@
         :tags: sql, bug
         :tickets: 2618
 
-      The :class:`.DECIMAL` type now honors the "precision" and
+      The :class:`~sqlalchemy.types.DECIMAL` type now honors the "precision" and
       "scale" arguments when rendering DDL.
 
     .. change::
@@ -1684,7 +1684,7 @@
     .. change::
         :tags: engine
 
-      The "reflect=True" argument to :class:`MetaData` is deprecated.
+      The "reflect=True" argument to :class:`~sqlalchemy.schema.MetaData` is deprecated.
       Please use the :meth:`.MetaData.reflect` method.
 
     .. change::
@@ -1821,7 +1821,7 @@
         :tickets: 2595
 
       The auto-correlation feature of :func:`.select`, and
-      by proxy that of :class:`.orm.Query`, will not
+      by proxy that of :class:`.Query`, will not
       take effect for a SELECT statement that is being
       rendered directly in the FROM list of the enclosing
       SELECT.  Correlation in SQL only applies to column
diff --git a/doc/build/changelog/changelog_09.rst b/doc/build/changelog/changelog_09.rst
index 89d8e14f3..8c098ddce 100644
--- a/doc/build/changelog/changelog_09.rst
+++ b/doc/build/changelog/changelog_09.rst
@@ -311,7 +311,7 @@
         :tags: feature, core
         :tickets: 2793
 
-        Added a new variant to :meth:`.ValuesBase.returning` called
+        Added a new variant to :meth:`.UpdateBase.returning` called
         :meth:`.ValuesBase.return_defaults`; this allows arbitrary columns
         to be added to the RETURNING clause of the statement without interfering
         with the compilers usual "implicit returning" feature, which is used to
@@ -557,7 +557,7 @@
         :tags: feature, sql
         :tickets: 1068
 
-        A :class:`.Label` construct will now render as its name alone
+        A :func:`~sqlalchemy.sql.expression.label` construct will now render as its name alone
         in an ``ORDER BY`` clause, if that label is also referred to
         in the columns clause of the select, instead of rewriting the
         full expression.  This gives the database a better chance to
@@ -595,13 +595,13 @@
         :tags: bug, orm
         :tickets: 2736
 
-        The "auto-aliasing" behavior of the :class:`.Query.select_from`
+        The "auto-aliasing" behavior of the :meth:`.Query.select_from`
         method has been turned off.  The specific behavior is now
-        availble via a new method :class:`.Query.select_entity_from`.
+        availble via a new method :meth:`.Query.select_entity_from`.
         The auto-aliasing behavior here was never well documented and
-        is generally not what's desired, as :class:`.Query.select_from`
+        is generally not what's desired, as :meth:`.Query.select_from`
         has become more oriented towards controlling how a JOIN is
-        rendered.  :class:`.Query.select_entity_from` will also be made
+        rendered.  :meth:`.Query.select_entity_from` will also be made
         available in 0.8 so that applications which rely on the auto-aliasing
         can shift their applications to use this method.
 
diff --git a/doc/build/changelog/migration_08.rst b/doc/build/changelog/migration_08.rst
index 971dd2f51..dcff0365f 100644
--- a/doc/build/changelog/migration_08.rst
+++ b/doc/build/changelog/migration_08.rst
@@ -522,7 +522,7 @@ accepted as a FROM clause within the core::
     stmt = select([User]).where(User.id == 5)
 
 Above, the mapped ``User`` class will expand into
-:class:`.Table` to which :class:`.User` is mapped.
+the :class:`.Table` to which ``User`` is mapped.
 
 :ticket:`2245`