point to vector optimization

Author: jmckenna

en/mapfile/layer.txt

@@ -380,12 +380,18 @@ ENCODING [string]
 .. index::
    pair: LAYER; EXTENT
    :name: mapfile-layer-extent
+   
+.. _layer-extent:
 
 EXTENT [minx] [miny] [maxx] [maxy]
     The spatial extent of the data. In most cases you will not need
     to specify this, but it can be used to avoid the speed cost of having
     MapServer compute the extents of the data.  An application can also
     possibly use this value to override the extents of the map.
+    
+    .. TIP::
+       Setting EXTENT at the layer-level is a common optimization step
+       for database connections (see :ref:`Vector Data Management & Optimization <vector-database-optimization>`)       
 
 .. index::
    pair: LAYER; FEATURE

en/optimization/vector.txt

@@ -10,7 +10,7 @@
 :Author: Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
 :Original Author: HostGIS
-:Last Updated: 2022-08-12
+:Last Updated: 2025-07-29
 
 .. contents:: Table of Contents
     :depth: 3
@@ -426,6 +426,8 @@ The following steps will help you examine the issue (using a WFS case) :
 
 .. index::
    pair: Optimization; Databases
+   
+.. _vector-database-optimization:
 
 Databases in General (PostGIS, Oracle, SpatiaLite, GeoPackage, Microsoft SQL Server, MySQL)
 -------------------------------------------------------------------------------------------
@@ -453,7 +455,7 @@ Set EXTENT at the LAYER level of mapfile
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Also for performance, each of your LAYERs with a database connection should 
-have EXTENT set at the layer level (as well as *ows_extent* metadata if you
+have :ref:`EXTENT <layer-extent>` set at the layer level (as well as *ows_extent* metadata if you
 are serving through OGC services), such as:
 
    .. code-block:: mapfile