Fix internal links

admin.rst

@@ -79,7 +79,7 @@ PostgREST outputs basic request logging to stdout. When running it in an SSH ses
 
   # another option is to pipe the output into "logger -t postgrest"
 
-(Avoid :code:`nohup postgrest` because the HUP signal is used for manual `Schema Reloading`_.)
+(Avoid :code:`nohup postgrest` because the HUP signal is used for manual :ref:`schema_reloading`.)
 
 Hardening PostgREST
 ===================
@@ -113,6 +113,8 @@ The first step is to create an Nginx configuration file that proxies requests to
     }
   }
 
+.. _block_fulltable:
+
 Block Full-Table Operations
 ---------------------------
 
@@ -135,7 +137,7 @@ This does not protect against malicious actions, since someone can add a url par
 Count-Header DoS
 ----------------
 
-For convenience to client-side pagination controls PostgREST supports counting and reporting total table size in its response. As described in `Limits and Pagination`_, responses ordinarily include a range but leave the total unspecified like
+For convenience to client-side pagination controls PostgREST supports counting and reporting total table size in its response. As described in :ref:`limits`, responses ordinarily include a range but leave the total unspecified like
 
 .. code-block:: http
 
@@ -227,10 +229,12 @@ Once you've verified that requests are as you expect, you can get more informati
 
 Restart the database and watch the log file in real-time to understand how HTTP requests are being translated into SQL commands.
 
+.. _schema_reloading:
+
 Schema Reloading
 ----------------
 
-Users are often confused by PostgREST's database schema cache. It is present because detecting foreign key relationships between tables (including how those relationships pass through views) is necessary, but costly. API requests consult the schema cache as part of :ref:`Resource Embedding`_. However if the schema changes while the server is running it results in a stale cache and leads to errors claiming that no relations are detected between tables.
+Users are often confused by PostgREST's database schema cache. It is present because detecting foreign key relationships between tables (including how those relationships pass through views) is necessary, but costly. API requests consult the schema cache as part of :ref:`resource_embedding`. However if the schema changes while the server is running it results in a stale cache and leads to errors claiming that no relations are detected between tables.
 
 To refresh the cache without restarting the PostgREST server, send the server process a SIGHUP signal:
 

api.rst

@@ -14,7 +14,9 @@ There are no deeply/nested/routes. Each route provides OPTIONS, GET, POST, PATCH
 
 .. note::
 
-  Why not provide nested routes? Many APIs allow nesting to retrieve related information, such as :code:`/films/1/director`. We offer a more flexible mechanism (inspired by GraphQL) to embed related information. It can handle one-to-many and many-to-many relationships. This is covered in the section about `Resource Embedding`_.
+  Why not provide nested routes? Many APIs allow nesting to retrieve related information, such as :code:`/films/1/director`. We offer a more flexible mechanism (inspired by GraphQL) to embed related information. It can handle one-to-many and many-to-many relationships. This is covered in the section about :ref:`resource_embedding`.
+
+.. _h_filter:
 
 Horizontal Filtering (Rows)
 ---------------------------
@@ -57,6 +59,8 @@ To negate any operator, prefix it with :code:`not` like :code:`?a=not.eq.2`.
 
 For more complicated filters (such as those involving condition 1 OR condition 2) you will have to create a new view in the database.
 
+.. _v_filter:
+
 Vertical Filtering (Columns)
 ----------------------------
 
@@ -66,7 +70,7 @@ When certain columns are wide (such as those holding binary data), it is more ef
 
   GET /people?select=fname,age HTTP/1.1
 
-The default is :sql:`*`, meaning all columns. This value will become more important below in :ref:`Resource Embedding`_.
+The default is :sql:`*`, meaning all columns. This value will become more important below in :ref:`resource_embedding`.
 
 .. _computed_cols:
 
@@ -129,6 +133,8 @@ If you care where nulls are sorted, add nullsfirst or nullslast:
 
 You can also use :ref:`computed_cols` to order the results, even though the computed columns will not appear in the output.
 
+.. _limits:
+
 Limits and Pagination
 ---------------------
 
@@ -246,7 +252,9 @@ You can use a tool like `Swagger UI <http://swagger.io/swagger-ui/>`_ to create
 
 .. note::
 
-  The OpenAPI information can go out of date as the schema changes under a running server. To learn how to refresh the cache see :ref:`Schema Reloading`_.
+  The OpenAPI information can go out of date as the schema changes under a running server. To learn how to refresh the cache see :ref:`schema_reloading`.
+
+.. _resource_embedding:
 
 Resource Embedding
 ==================
@@ -303,7 +311,7 @@ PostgREST can also detect relations going through join tables. Thus you can requ
 
 .. note::
 
-  Whenever foreign key relations change in the database schema you must refresh PostgREST's schema cache to allow resource embedding to work properly. See the section :ref:`Schema Reloading`_.
+  Whenever foreign key relations change in the database schema you must refresh PostgREST's schema cache to allow resource embedding to work properly. See the section :ref:`schema_reloading`.
 
 Embedded Filters and Order
 --------------------------
@@ -405,7 +413,7 @@ To create a row in a database table post a JSON object whose keys are the names
 
 The response will include a :code:`Location` header describing where to find the new object. If the table is write-only then constructing the Location header will cause a permissions error. To successfully insert an item to a write-only table you will need to suppress the Location response header by including the request header :code:`Prefer: return=minimal`.
 
-On the other end of the spectrum you can get the full created object back in the response to your request by including the header :code:`Prefer: return=representation`. That way you won't have to make another HTTP call to discover properties that may have been filled in on the server side. You can also apply the standard `Vertical Filtering (Columns)`_ to these results.
+On the other end of the spectrum you can get the full created object back in the response to your request by including the header :code:`Prefer: return=representation`. That way you won't have to make another HTTP call to discover properties that may have been filled in on the server side. You can also apply the standard :ref:`v_filter` to these results.
 
 .. note::
 
@@ -419,21 +427,21 @@ On the other end of the spectrum you can get the full created object back in the
     No
     "{ \"a\": 1, \"b\": 2 }"
 
-  Some javascript libraries will post the data incorrectly if you're not careful. For best results try one of the :ref:`Client-Side Libraries`_ built for PostgREST.
+  Some javascript libraries will post the data incorrectly if you're not careful. For best results try one of the :ref:`clientside_libraries` built for PostgREST.
 
-To update a row or rows in a table, use the PATCH verb. Use :ref:`Horizontal Filtering (Rows)`_ to specify which record(s) to update. Here is an exmaple query setting the :code:`category` column to child for all people below a certain age.
+To update a row or rows in a table, use the PATCH verb. Use :ref:`h_filter` to specify which record(s) to update. Here is an exmaple query setting the :code:`category` column to child for all people below a certain age.
 
 .. code:: HTTP
 
   PATCH /people?age=lt.13 HTTP/1.1
 
   { "category": "child" }
 
-Updates also support :code:`Prefer: return=representation` plus `Vertical Filtering (Columns)`_.
+Updates also support :code:`Prefer: return=representation` plus :ref:`v_filter`.
 
 .. note::
 
-  Beware of accidentally updating every row in a table. To learn to prevent that see :ref:`Block Full-Table Operations`_.
+  Beware of accidentally updating every row in a table. To learn to prevent that see :ref:`block_fulltable`.
 
 Bulk Insert
 -----------
@@ -468,12 +476,12 @@ To bulk insert JSON post an array of objects having all-matching keys
 Deletions
 =========
 
-To delete rows in a table, use the DELETE verb plus :ref:`Horizontal Filtering (Rows)`_. For instance deleting inactive users:
+To delete rows in a table, use the DELETE verb plus :ref:`h_filter`. For instance deleting inactive users:
 
 .. code-block:: HTTP
 
   DELETE /user?active=is.false HTTP/1.1
 
 .. note::
 
-  Beware of accidentally delting all rows in a table. To learn to prevent that see :ref:`Block Full-Table Operations`_.
+  Beware of accidentally delting all rows in a table. To learn to prevent that see :ref:`block_fulltable`.

intro.rst

@@ -35,6 +35,8 @@ Ecosystem
 
 PostgREST has a growing ecosystem of examples, and libraries, experiments, and users. Here is a selection.
 
+.. _clientside_libraries:
+
 Client-Side Libraries
 ---------------------