Change CompileException references to ConpileError

2 files changed, 3 insertions, 3 deletions

diff --git a/doc/build/changelog/changelog_07.rst b/doc/build/changelog/changelog_07.rst
index a102573e9..68e03a2e2 100644
--- a/doc/build/changelog/changelog_07.rst
+++ b/doc/build/changelog/changelog_07.rst
@@ -1444,10 +1444,10 @@
         :tickets: 2361
 
       Dialect-specific compilers now raise
-      CompileException for all type/statement compilation
+      CompileError for all type/statement compilation
       issues, instead of InvalidRequestError or ArgumentError.
       The DDL for CREATE TABLE will re-raise
-      CompileExceptions to include table/column information
+      CompileError to include table/column information
       for the problematic column.
 
     .. change::
diff --git a/lib/sqlalchemy/sql/sqltypes.py b/lib/sqlalchemy/sql/sqltypes.py
index 82ab3d556..8f22ae81c 100644
--- a/lib/sqlalchemy/sql/sqltypes.py
+++ b/lib/sqlalchemy/sql/sqltypes.py
@@ -1512,7 +1512,7 @@ class NullType(TypeEngine):
     The :class:`.NullType` can be used within SQL expression invocation
     without issue, it just has no behavior either at the expression construction
     level or at the bind-parameter/result processing level.  :class:`.NullType`
-    will result in a :class:`.CompileException` if the compiler is asked to render
+    will result in a :exc:`.CompileError` if the compiler is asked to render
     the type itself, such as if it is used in a :func:`.cast` operation
     or within a schema creation operation such as that invoked by
     :meth:`.MetaData.create_all` or the :class:`.CreateTable` construct.