spelling: Postgis -> PostGIS

diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst
index ba5e64e8c6649fc6aa1c5104c1ff41d387c2e5ec..6eb58306abcb814184024ab7c22ed85ad2a4c227 100644 (file)
--- a/doc/build/changelog/changelog_08.rst
+++ b/doc/build/changelog/changelog_08.rst
@@ -3189,7 +3189,7 @@
       to augment bind- and result- behavior at the
       SQL level, as opposed to in the Python level.
       Allows for schemes like transparent encryption/
-      decryption, usage of Postgis functions, etc.
+      decryption, usage of PostGIS functions, etc.
 
     .. change::
         :tags: feature, sql

diff --git a/doc/build/core/custom_types.rst b/doc/build/core/custom_types.rst
index cbcc8c226d6380387ebdd5d3b1f330a5de5fbeff..f47640c92707238e885d4200f0be3560e19f49ed 100644 (file)
--- a/doc/build/core/custom_types.rst
+++ b/doc/build/core/custom_types.rst
@@ -338,7 +338,7 @@ possible to define SQL-level transformations as well.  The rationale here is whe
 only the relational database contains a particular series of functions that are necessary
 to coerce incoming and outgoing data between an application and persistence format.
 Examples include using database-defined encryption/decryption functions, as well
-as stored procedures that handle geographic data.  The Postgis extension to PostgreSQL
+as stored procedures that handle geographic data.  The PostGIS extension to PostgreSQL
 includes an extensive array of SQL functions that are necessary for coercing
 data into particular formats.
 
@@ -348,7 +348,7 @@ can include implementations of
 when defined to return a non-``None`` value should return a :class:`.ColumnElement`
 expression to be injected into the SQL statement, either surrounding
 bound parameters or a column expression.  For example, to build a ``Geometry``
-type which will apply the Postgis function ``ST_GeomFromText`` to all outgoing
+type which will apply the PostGIS function ``ST_GeomFromText`` to all outgoing
 values and the function ``ST_AsText`` to all incoming data, we can create
 our own subclass of :class:`.UserDefinedType` which provides these methods
 in conjunction with :data:`~.sqlalchemy.sql.expression.func`::

diff --git a/examples/postgis/postgis.py b/examples/postgis/postgis.py
index 01671c5c41ef79adc1daedce392f3dfc36f5bf49..ffea3d0189ff5d908e2f2b732c656a36ea07f09f 100644 (file)
--- a/examples/postgis/postgis.py
+++ b/examples/postgis/postgis.py
@@ -130,8 +130,8 @@ class LineString(Curve):
 
 
 # DDL integration
-# Postgis historically has required AddGeometryColumn/DropGeometryColumn
-# and other management methods in order to create Postgis columns.  Newer
+# PostGIS historically has required AddGeometryColumn/DropGeometryColumn
+# and other management methods in order to create PostGIS columns.  Newer
 # versions don't appear to require these special steps anymore.  However,
 # here we illustrate how to set up these features in any case.