add initial spelling wordlist

jmckenna · jmckenna · commit e7eecb9074f5 · 2026-03-28T11:45:24.000-03:00
diff --git a/conf.py b/conf.py
@@ -131,6 +131,20 @@ def __getattr__(cls, name):
 # set filename used by spelling extension
 spelling_word_list_filename='spelling_wordlist.dict'
 
+# spelling extension options
+# --------------------------
+
+# set filename used by spelling extension
+spelling_word_list_filename='spelling_wordlist.dict'
+
+# ignore changelogs and RFCs
+spelling_exclude_patterns = [
+    'development/changelog/*',
+    'development/changelog/mapcache/*',
+    'development/changelog/tinyows/*',
+    'development/rfc/*'    
+]
+
 # Options for HTML output
 # -----------------------
 
diff --git a/en/development/documentation.txt b/en/development/documentation.txt
@@ -8,7 +8,7 @@
 :Contact: hobu.inc at gmail.com
 :Author:  Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
-:Last Updated: 2026-03-23
+:Last Updated: 2026-03-28
 
 .. contents:: Table of Contents
     :depth: 4
@@ -457,7 +457,7 @@ Please for both parameter, keep the alphabetical order to kept them readable.
 
 **Structure of the i18n files in the MapServer-documentation root directory**
 
-The structure you need to make all the transaltion process is like below (an 
+The structure you need to make all the translation process is like below (an 
 excerpt to give you the main required structure)
 
    ::
diff --git a/en/development/tests/autotest.txt b/en/development/tests/autotest.txt
@@ -8,7 +8,7 @@
 :Contact:      warmerdam at pobox.com
 :Author:       Jeff McKenna
 :Contact:      jmckenna at gatewaygeomatics.com
-:Last Updated: 2024-06-20
+:Last Updated: 2026-03-28
 
 .. contents:: Table of Contents
     :depth: 2
@@ -245,7 +245,7 @@ REQUIRES - Handling Build Options
 
 Because MapServer can be built with many possible extensions, such as support
 for OGR, GDAL, and PROJ.4, it is desirable to have the testsuite automatically
-detect which tests should be run based on the configuratio of MapServer. This
+detect which tests should be run based on the configuration of MapServer. This
 is accomplished by capturing the version output of "map2img -v" and using the
 various keys in that to decide which tests can be run. A directory can have a
 file called "all_require.txt" with a "REQUIRES:" line indicating components
diff --git a/en/input/vector/kml.txt b/en/input/vector/kml.txt
@@ -10,7 +10,7 @@
 
 Keyhole Markup Language (KML) is an XML-based language for managing the
 display of 3D geospatial data.  KML is a standard maintained by the Open 
-Geospatial Consoritum (OGC).
+Geospatial Consortium (OGC).
 
 Links to KML-Related Information
 --------------------------------
diff --git a/en/input/vector/oracle.txt b/en/input/vector/oracle.txt
@@ -7,7 +7,7 @@
 :Author: Bart van den Eijnden
 :Author: Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
-:Last Updated: 2021-05-05
+:Last Updated: 2026-03-28
 
 .. contents:: Table of Contents
     :depth: 4
@@ -344,7 +344,7 @@ Syntax for your MAP file:
 
 .. note::
     Make sure you set the wms_extent METADATA for the LAYER, as otherwise the
-    "Getcapabilities" request takes a lot of time.
+    "getCapabilities" request takes a lot of time.
     
 What MapServer Components are related to Oracle Spatial access
 --------------------------------------------------------------
diff --git a/en/installation/oracle.txt b/en/installation/oracle.txt
@@ -207,9 +207,9 @@ Testing & Error handling
 ........................
 
 So you are fine now. Load the mapfile in your application and try it. If
-everything goes well: Great, if not, possibly this ugly error-emssage occurs
-(this one cmae by querying MapServer through the WMS interface as a
-GetMap-request):
+everything goes well: great, if not, possibly this ugly error message occurs
+(this one was made by querying MapServer through the WMS interface as a
+GetMap request):
 
 ::
 
diff --git a/en/installation/win32.txt b/en/installation/win32.txt
@@ -139,7 +139,7 @@ Interim Builds title. The absolute latest copy of the source code can be
 obtained from :ref:`git`; however, the GitHub repository does not contain several 
 important source files (maplexer.c, mapparser.c and
 mapparser.h) normally generated on unix, so if possible, using a nightly
-snaphot is substantially easier than working directly from :ref:`git`.
+snapshot is substantially easier than working directly from :ref:`git`.
 
 **Required Libraries**
 ----------------------
diff --git a/en/mapcache/caches.txt b/en/mapcache/caches.txt
@@ -331,7 +331,7 @@ Blank Tile Detection
 MapCache's SQLite caches support the detection and storage of blank (i.e. uniform
 color) tiles, and will store a quadruplet of the rgba color component in the data
 blob instead of the compressed image data itself. That quadruplet will be
-transformed on-the-fly to a 1-bit palleted PNG before being returned to the client.
+transformed on-the-fly to a 1-bit paletted PNG before being returned to the client.
 
 
 .. code-block:: xml
@@ -589,7 +589,7 @@ You can add multiple <server> entries.
 To limit the memory used by blank tiles inside the memcache instance, you
 may enable blank tile detection, in which case a `#rgba` quadruplet will
 be stored to the cache instead of the actual image data. MapCache will convert
-that on-the-fly to a 1-bit palleted PNG image before returning it to the client.
+that on-the-fly to a 1-bit paletted PNG image before returning it to the client.
 
 
 .. code-block:: xml
diff --git a/en/mapcache/formats.txt b/en/mapcache/formats.txt
@@ -42,7 +42,7 @@ PNG Format
 --------------------------------------------------------------------------------
 
 The PNG format creates PNG images, with optional quantization (reduction of
-the number of colors to create an 8-bit palleted PNG).
+the number of colors to create an 8-bit paletted PNG).
 
 .. code-block:: xml
 
@@ -56,7 +56,7 @@ the number of colors to create an 8-bit palleted PNG).
   zlib compression.
 - *colors*: Number of colors to use for quantization. Omit this key to
   produce 24 or 32 bit RGB/RGBA PNGs, or set to a value between 2 and 256
-  to create an 8-bit palleted PNG. The quantization step is destructive:
+  to create an 8-bit paletted PNG. The quantization step is destructive:
   There is no guarantee that pixels will not have a noticeable shift in color
   in the case when the tile contains many colors.
 
diff --git a/en/mapcache/install.txt b/en/mapcache/install.txt
@@ -69,10 +69,10 @@ functionalities:
   run MapCache as an Apache module
 - **gdal / geos**: *libgdal1-dev* *libgeos-dev*. Needed to enable advanced seeding
   options (for only seeding tiles that intersect a given geographical feature)
-- **sqlite**: *libsqlite3-dev*. For enabling the SQLite backend storages
-- **tiff**: *libtiff4-dev*. For enabling the TIFF backend storages
-- **berkeley db** *libdb4.8-dev* : For enabling the Berkeley DB backend storages
-- **lmdb** *liblmdb-dev* : For enabling the Lightning Memory-Mapped Database backend storages
+- **sqlite**: *libsqlite3-dev*. For enabling the SQLite backend storage
+- **tiff**: *libtiff4-dev*. For enabling the TIFF backend storage
+- **berkeley db** *libdb4.8-dev* : For enabling the Berkeley DB backend storage
+- **lmdb** *liblmdb-dev* : For enabling the Lightning Memory-Mapped Database backend storage
   (available since MapCache 1.14.0 release)
 
 .. note::
@@ -540,7 +540,7 @@ Here is a list of supported options that can be enabled/disabled at build.
 
    When writing TIFF files, MapCache can also optionally add georeferencing
    information if compiled with libtiff support. GeoTiff writing does not
-   produce the full tags needed for defining which preojection the grid is
+   produce the full tags needed for defining which projection the grid is
    in, but will only produce those defining the pixel scale and the tiepoints
    (i.e. the equivalent information found in the accompanying .tfw files).
 
@@ -638,8 +638,8 @@ Optional:
   MapCache as an Apache module
 - **GDAL / GEOS**: Needed to enable advanced seeding options (for only
   seeding tiles that intersect a given geographical feature)
-- **SQLITE**: For enabling the SQLite backend storages
-- **TIFF**: For enabling the TIFF backend storages
+- **SQLITE**: For enabling the SQLite backend storage
+- **TIFF**: For enabling the TIFF backend storage
 
 Configure Your Makefile
 -----------------------
diff --git a/en/ogc/filter_encoding.txt b/en/ogc/filter_encoding.txt
@@ -10,7 +10,7 @@
 :Author:        Jeff McKenna
 :Contact:       jmckenna at gatewaygeomatics.com
 :Author:        Yewondwossen Assefa
-:Last Updated:  2026-03-23
+:Last Updated:  2026-03-28
 
 .. contents:: Table of Contents
     :depth: 2
@@ -547,7 +547,7 @@ Following are some MapServer specific notes on this test suite:
 5.  *Test number 1.3.6.1*:
     
     - The returned feature xml won't validate because the validation is done 
-      against a specific xsd (geomatry.xsd).
+      against a specific xsd (geometry.xsd).
 
     - The data conversion on multipoints and multilayers are not supported within GDAL.
     
diff --git a/en/ogc/sos_server.txt b/en/ogc/sos_server.txt
@@ -9,7 +9,7 @@
 
 :Author: Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
-:Last Updated: 2021-03-27
+:Last Updated: 2026-03-28
 
 .. contents:: Table of Contents
     :depth: 2
@@ -861,12 +861,12 @@ Layer Object Metadata
   The logic for the bounding box returned as part of the offering is
   the following:
   
-  - note that it is a mandatory element that needs an espg code and
+  - note that it is a mandatory element that needs an EPSG code and
     lower/upper corner coordinates
       
-  - looks for the espg parameter in the first layer of the offering
+  - looks for the EPSG parameter in the first layer of the offering
     (this could be an ows/sos_srs or a projection object with the
-    epsg code (mandatory)
+    EPSG code (mandatory)
       
   - looks for sos_offering_extent. If the metadata is not available, 
     the extents of all layers in the offering will be used to compute it.
diff --git a/en/ogc/wms_time.txt b/en/ogc/wms_time.txt
@@ -9,7 +9,7 @@
 
 :Author: Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
-:Last Updated: 2023-01-09
+:Last Updated: 2026-03-28
 
 .. contents:: Table of Contents
     :depth: 2
@@ -95,7 +95,7 @@ metadata (see Annex C.3 in the `WMS 1.1.1 specification`_ document for a full
 description):
 
 1. *value* - a single value.  This is not directly supported in MapServer but 
-   there is an easy workwound by specifying the same value as min and max.
+   there is an easy workaround by specifying the same value as min and max.
 
 2. *value1,value2,value3,...* - a list of multiple values.
 
diff --git a/en/optimization/limit_mapfile_access.txt b/en/optimization/limit_mapfile_access.txt
@@ -11,10 +11,10 @@
 :Contact: sdlime at gmail.com
 :Author: Jeff McKenna
 :Contact: jmckenna at gatewaygeomatics.com
-:Last Updated: 2022-08-16
+:Last Updated: 2026-03-28
 
 The MapServer CGI, by default, will happily attempt to process any mapfile it is 
-asked to. While this might be desireable in a development environment, it is not 
+asked to. While this might be desirable in a development environment, it is not 
 acceptable for public-facing installations. MapServer supports the use of specific
 **environment variables**, set at the web server tier, to limit access. Since 
 the MapServer 7.6.3 release, you are **required** to use (a combination of) 
diff --git a/en/spelling_wordlist.dict b/en/spelling_wordlist.dict
diff --git a/en/tinyows/configfile.txt b/en/tinyows/configfile.txt
