Fixed #32964 -- Corrected 'setup'/'set up' usage in docs.

docs/ref/contrib/gis/forms-api.txt

@@ -33,7 +33,7 @@ GeoDjango form fields take the following optional arguments.
 .. attribute:: Field.geom_type
 
     You generally shouldn't have to set or change that attribute which should
-    be setup depending on the field class. It matches the OpenGIS standard
+    be set up depending on the field class. It matches the OpenGIS standard
     geometry name.
 
 Form field classes

docs/ref/contrib/postgres/fields.txt

@@ -261,7 +261,7 @@ transform do not change. For example::
     Read about `the performance considerations`_ prior to using it.
 
     To use ``citext``, use the :class:`.CITextExtension` operation to
-    :ref:`setup the citext extension <create-postgresql-extensions>` in
+    :ref:`set up the citext extension <create-postgresql-extensions>` in
     PostgreSQL before the first ``CreateModel`` migration operation.
 
     If you're using an :class:`~django.contrib.postgres.fields.ArrayField`
@@ -307,7 +307,7 @@ transform do not change. For example::
     To use this field, you'll need to:
 
     #. Add ``'django.contrib.postgres'`` in your :setting:`INSTALLED_APPS`.
-    #. :ref:`Setup the hstore extension <create-postgresql-extensions>` in
+    #. :ref:`Set up the hstore extension <create-postgresql-extensions>` in
        PostgreSQL.
 
     You'll see an error like ``can't adapt type 'dict'`` if you skip the first

docs/ref/forms/widgets.txt

@@ -454,7 +454,7 @@ foundation for custom widgets.
                 return '{}-{}-{}'.format(year, month, day)
 
     The constructor creates several :class:`Select` widgets in a list. The
-    ``super()`` method uses this list to setup the widget.
+    ``super()`` method uses this list to set up the widget.
 
     The required method :meth:`~MultiWidget.decompress` breaks up a
     ``datetime.date`` value into the day, month, and year values corresponding