Add entry for OPTIONS on views

* Also clarify the schema cache page

releases/upcoming.rst

@@ -37,6 +37,9 @@ Added
 * Allow ``Bearer`` with and without capitalization as authentication schema. See :ref:`client_auth`.
   |br| -- `@wolfgangwalther <https://github.com/wolfgangwalther>`_
 
+* Allow OPTIONS to generate HTTP methods based on views triggers. See :ref:`OPTIONS requests <options_requests>`.
+  |br| -- `@laurenceisla <https://github.com/laurenceisla>`_
+
 * Show timestamps for server diagnostic information. See :ref:`pgrst_logging`.
   |br| -- `@steve-chavez <https://github.com/steve-chavez>`_
 
@@ -54,8 +57,7 @@ Added
 
 * Documentation improvements
 
-  + Added the :ref:`OPTIONS requests <options_requests>` section.
+  + Added the :ref:`schema_cache` page.
-  + Added the :ref:`schema_cache` section.
   + Moved the :ref:`schema_reloading` reference from :ref:`admin` to :ref:`schema_cache`
 
 Fixed

schema_cache.rst

@@ -3,7 +3,10 @@
 Schema Cache
 ============
 
-PostgREST caches metadata from the database schema to avoid repeating expensive queries. This metadata is not required by all of the PostgREST features, only the following:
+Certain PostgREST features require metadata from the database schema. Getting this metadata requires executing expensive queries, so
+in order to avoid repeating this work, PostgREST uses a schema cache.
+
+The following features are the ones that require metadata from the schema cache.
 
 +--------------------------------------------+-------------------------------------------------------------------------------+
 | Feature                                    | Required Metadata                                                             |