docs: Fix spelling mistakes

docs/references/api/aggregate_functions.rst

@@ -82,7 +82,7 @@ This would return a row for each unique value in the ``order_date`` column, with
     }
   ]
 
-When ``count()`` is used with an associated column, its behaviour is slightly different: It will return the count of all values that are not ``NULL``. This is due to how PostgreSQL itself implements the ``count()`` function.
+When ``count()`` is used with an associated column, its behavior is slightly different: It will return the count of all values that are not ``NULL``. This is due to how PostgreSQL itself implements the ``count()`` function.
 
 Renaming and Casting
 ====================

docs/references/api/preferences.rst

@@ -63,7 +63,7 @@ The server ignores unrecognized or unfulfillable preferences by default. You can
 Timezone
 ========
 
-The ``timezone`` preference allows you to change the `PostgreSQL timezone <https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE>`_. It accepts all timezones in `pg_timezone_names <https://www.postgresql.org/docs/current/view-pg-timezone-names.html>`_.
+The ``timezone`` preference allows you to change the `PostgreSQL timezone <https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-TIMEZONE>`_. It accepts all time zones in `pg_timezone_names <https://www.postgresql.org/docs/current/view-pg-timezone-names.html>`_.
 
 
 .. code-block:: bash
@@ -85,7 +85,7 @@ The ``timezone`` preference allows you to change the `PostgreSQL timezone <https
     {"t":"2023-10-18T09:37:59.611-07:00"}
   ]
 
-For an invalid timezone, PostgREST returns values with the default timezone (configured on ``postgresql.conf`` or as a setting on the :ref:`authenticator <roles>`).
+For an invalid time zone, PostgREST returns values with the default time zone (configured on ``postgresql.conf`` or as a setting on the :ref:`authenticator <roles>`).
 
 .. code-block:: bash
 
@@ -107,7 +107,7 @@ For an invalid timezone, PostgREST returns values with the default timezone (con
 
 Note that there's no ``Preference-Applied`` in the response.
 
-However, with ``handling=strict``, an invalid timezone preference will throw an :ref:`error <pgrst122>`.
+However, with ``handling=strict``, an invalid time zone preference will throw an :ref:`error <pgrst122>`.
 
 .. code-block:: bash
 

docs/references/api/resource_representation.rst

@@ -108,7 +108,7 @@ By default PostgREST returns all JSON null values. For example, requesting ``/pr
     { "id": 13, "name": "Y",        "client_id": null, "another_col": null }
   ]
 
-On large result sets, the unused keys with ``null`` values can waste bandwith unnecessarily. To remove them, specify ``nulls=stripped`` as a parameter of ``application/vnd.pgrst.array``:
+On large result sets, the unused keys with ``null`` values can waste bandwidth unnecessarily. To remove them, specify ``nulls=stripped`` as a parameter of ``application/vnd.pgrst.array``:
 
 .. code-block:: bash