diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 6ef1ae4a16a..b7463f0e2d1 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -128,7 +128,5 @@ repos:
           - c
           - c++
           - csv
-          - html
-          - markdown
           - python
           - tex
diff --git a/doc/development/style_guide.md b/doc/development/style_guide.md
index 524decabbcb..1c8b109f827 100644
--- a/doc/development/style_guide.md
+++ b/doc/development/style_guide.md
@@ -414,7 +414,7 @@ See [Changing computational region](#changing-computational-region) for more det
 #### Mapsets
 
 **Output data should be always written to the current mapset**. This is ensured
-by build-in GRASS mechanisms, so there is nothing which needs to be done in the
+by built-in GRASS mechanisms, so there is nothing which needs to be done in the
 tool. If a tool modifies inputs, the input must be in the current mapset.
 
 The tool should accept inputs from any mapset in the current project. The
diff --git a/doc/interfaces_overview.md b/doc/interfaces_overview.md
index cc6c2c173b5..a932fe5edd1 100644
--- a/doc/interfaces_overview.md
+++ b/doc/interfaces_overview.md
@@ -114,7 +114,7 @@ m.d_vect(map="streets", color="black")
 m.show()
 ```
 
-![Elevation map overlayed with streets with gj.Map](jupyter_map.png)
+![Elevation map overlaid with streets with gj.Map](jupyter_map.png)
 
 [Learn more :material-arrow-right-bold:](jupyter_intro.md){ .md-button }
 
diff --git a/doc/jupyter_intro.md b/doc/jupyter_intro.md
index 4db8a8f3440..d1839ab372f 100644
--- a/doc/jupyter_intro.md
+++ b/doc/jupyter_intro.md
@@ -58,7 +58,7 @@ The following examples will use the [North Carolina dataset](https://grass.osgeo
 ## Map
 
 The `gj.Map` class in `grass.jupyter` provides a way to create static maps in Jupyter.
-Here we create a map of elevation overlayed with streets:
+Here we create a map of elevation overlaid with streets:
 
 ```python
 # Create a new map
@@ -74,7 +74,7 @@ m.d_vect(map="streets", color="black")
 m.show()
 ```
 
-![Elevation map overlayed with streets with gj.Map](jupyter_map.png)
+![Elevation map overlaid with streets with gj.Map](jupyter_map.png)
 
 !!! grass-tip "Order Matters"
     <!-- markdownlint-disable-next-line MD046 -->
diff --git a/doc/python_intro.md b/doc/python_intro.md
index cf0ee6c277a..5ae951a05a4 100644
--- a/doc/python_intro.md
+++ b/doc/python_intro.md
@@ -839,7 +839,7 @@ slope_aspect_tool.inputs
 ```
 
 The [grass.pygrass.modules](https://grass.osgeo.org/grass-stable/manuals/libpython/pygrass_modules.html)
-module provides an alterative approach to running GRASS tools.
+module provides an alternative approach to running GRASS tools.
 
 To learn more about the `Module` class, see the Full Documentation:
 
diff --git a/general/g.proj/g.proj.html b/general/g.proj/g.proj.html
index 7591d9fa50e..30dfb764e78 100644
--- a/general/g.proj/g.proj.html
+++ b/general/g.proj/g.proj.html
@@ -47,18 +47,18 @@ <h2>DESCRIPTION</h2>
 
 <dt>epsg=<em>number</em></dt>
 <dd><em>number</em> should correspond to the index number of a valid
-co-ordinate system in the <a href="https://epsg.org/search/by-name">EPSG
+coordinate system in the <a href="https://epsg.org/search/by-name">EPSG
 database</a>. EPSG code support is based upon a local copy of the GDAL CSV
-co-ordinate system and datum information files, stored in the directory
+coordinate system and datum information files, stored in the directory
 <code>$GISBASE/etc/proj/ogr_csv</code>. These can be updated if necessary
 to support future revisions of the EPSG database.</dd>
 </dl>
 
 <p>If datum information is incorrect or missing in the input
-co-ordinate system definition (e.g. PROJ descriptions have very limited
+coordinate system definition (e.g. PROJ descriptions have very limited
 support for specifying datum names), a GRASS datum abbreviation can instead be
 supplied using the <em>datum</em> parameter. This will override any
-datum contained in the input co-ordinate system, and discard
+datum contained in the input coordinate system, and discard
 any datum transformation parameters. Enter datum=<em>list</em> to return a
 list of all the datums supported by GRASS. Since any
 existing datum transformation parameters will have been discarded, the
@@ -80,12 +80,12 @@ <h2>DESCRIPTION</h2>
 
 <p>The final mode of operation of <em>g.proj</em> is to report on the datum
 information and datum transformation parameters associated with the
-co-ordinate system. The <b>-d</b> flag will report a human-readable summary of
+coordinate system. The <b>-d</b> flag will report a human-readable summary of
 this.
 
 <h2>NOTES</h2>
 
-<p>If the input co-ordinate system contains a datum name but no
+<p>If the input coordinate system contains a datum name but no
 transformation parameters, and there is more than one suitable parameter set
 available (according to the files datum.table and datumtransform.table in
 <code>$GISBASE/etc/proj</code>), <em>g.proj</em> will check the value of
@@ -99,17 +99,17 @@ <h2>NOTES</h2>
 (likely non-optimum) parameters for this datum if necessary in the future.</li>
 <li> <strong>Any other number less than or equal to the number of parameter sets
 available for this datum:</strong> Choose this parameter set and add it to the
-co-ordinate system description.</li>
+coordinate system description.</li>
 </ul>
 
 If the <b>-t</b> flag is specified, the module will attempt to change the
 datum transformation parameters using one of the above two methods
 <strong>even if</strong> a valid parameter set is already specified in the
-input co-ordinate system. This can be useful to change the datum information
+input coordinate system. This can be useful to change the datum information
 for an existing project.
 
 <p>Output is simply based on the input CRS information. g.proj does
-<strong>not</strong> attempt to verify that the co-ordinate system thus
+<strong>not</strong> attempt to verify that the coordinate system thus
 described matches a pre-defined existing system in use in the world. In
 particular, this means there may be no authority names and codes in the
 WKT output.
diff --git a/general/g.proj/g.proj.md b/general/g.proj/g.proj.md
index 65fdef6f115..20793dfc789 100644
--- a/general/g.proj/g.proj.md
+++ b/general/g.proj/g.proj.md
@@ -41,18 +41,18 @@ given for *description*, the PROJ description will be read from stdin
 rather than as a directly-supplied command-line parameter.
 
 epsg=*number*  
-*number* should correspond to the index number of a valid co-ordinate
+*number* should correspond to the index number of a valid coordinate
 system in the [EPSG database](https://epsg.org/search/by-name). EPSG
-code support is based upon a local copy of the GDAL CSV co-ordinate
+code support is based upon a local copy of the GDAL CSV coordinate
 system and datum information files, stored in the directory
 `$GISBASE/etc/proj/ogr_csv`. These can be updated if necessary to
 support future revisions of the EPSG database.
 
-If datum information is incorrect or missing in the input co-ordinate
+If datum information is incorrect or missing in the input coordinate
 system definition (e.g. PROJ descriptions have very limited support for
 specifying datum names), a GRASS datum abbreviation can instead be
 supplied using the *datum* parameter. This will override any datum
-contained in the input co-ordinate system, and discard any datum
+contained in the input coordinate system, and discard any datum
 transformation parameters. Enter datum=*list* to return a list of all
 the datums supported by GRASS. Since any existing datum transformation
 parameters will have been discarded, the *datumtrans* parameter should
@@ -72,12 +72,12 @@ be overwritten. The program will **not** warn before doing this.
 
 The final mode of operation of *g.proj* is to report on the datum
 information and datum transformation parameters associated with the
-co-ordinate system. The **-d** flag will report a human-readable summary
+coordinate system. The **-d** flag will report a human-readable summary
 of this.
 
 ## NOTES
 
-If the input co-ordinate system contains a datum name but no
+If the input coordinate system contains a datum name but no
 transformation parameters, and there is more than one suitable parameter
 set available (according to the files datum.table and
 datumtransform.table in `$GISBASE/etc/proj`), *g.proj* will check the
@@ -90,16 +90,16 @@ value of the *datumtrans* option and act according to the following:
   non-optimum) parameters for this datum if necessary in the future.
 - **Any other number less than or equal to the number of parameter sets
   available for this datum:** Choose this parameter set and add it to
-  the co-ordinate system description.
+  the coordinate system description.
 
 If the **-t** flag is specified, the module will attempt to change the
 datum transformation parameters using one of the above two methods
 **even if** a valid parameter set is already specified in the input
-co-ordinate system. This can be useful to change the datum information
+coordinate system. This can be useful to change the datum information
 for an existing project.
 
 Output is simply based on the input CRS information. g.proj does **not**
-attempt to verify that the co-ordinate system thus described matches a
+attempt to verify that the coordinate system thus described matches a
 pre-defined existing system in use in the world. In particular, this
 means there may be no authority names and codes in the WKT output.
 
diff --git a/general/g.setproj/g.setproj.html b/general/g.setproj/g.setproj.html
index 8db06bc6880..0b11611b62e 100644
--- a/general/g.setproj/g.setproj.html
+++ b/general/g.setproj/g.setproj.html
@@ -16,7 +16,7 @@ <h2>NOTES</h2>
 Most projections are supported. The
 <a href="https://proj.org/">PROJ</a> abbreviations for the names are
 used with two exceptions, viz. 'll', for latitude / longitude geographic
-co-ordinates, and 'stp', for the State Plane Co-ordinate system (used in the
+coordinates, and 'stp', for the State Plane Coordinate system (used in the
 USA).
 
 <p>After the projection name, the user will be asked for a geodetic datum. If
diff --git a/general/g.setproj/g.setproj.md b/general/g.setproj/g.setproj.md
index ed0d826c784..6d54da5ef59 100644
--- a/general/g.setproj/g.setproj.md
+++ b/general/g.setproj/g.setproj.md
@@ -14,7 +14,7 @@ can be run.
 The user will be prompted for the projection name. Most projections are
 supported. The [PROJ](https://proj.org/) abbreviations for the names are
 used with two exceptions, viz. 'll', for latitude / longitude geographic
-co-ordinates, and 'stp', for the State Plane Co-ordinate system (used in
+coordinates, and 'stp', for the State Plane Coordinate system (used in
 the USA).
 
 After the projection name, the user will be asked for a geodetic datum.
diff --git a/gui/xml/grass-interface.dtd b/gui/xml/grass-interface.dtd
index 006bb70edb1..e1f81795cbe 100644
--- a/gui/xml/grass-interface.dtd
+++ b/gui/xml/grass-interface.dtd
@@ -71,7 +71,7 @@
 	integer		: a numeric integer parameter.
 	float		: a numeric float parameter.
 	If multiple is "yes", then many values for the
-	parameter may be given in a comma-seperated list
+	parameter may be given in a comma-separated list
 -->
 <!ELEMENT parameter     (description?, keydesc?, gisprompt?, default?, values?, guisection?)>
 <!ATTLIST parameter	name		CDATA #REQUIRED
diff --git a/imagery/i.cluster/i.cluster.html b/imagery/i.cluster/i.cluster.html
index e7cff674606..b2f518ddcbb 100644
--- a/imagery/i.cluster/i.cluster.html
+++ b/imagery/i.cluster/i.cluster.html
@@ -285,7 +285,7 @@ <h2>EXAMPLE</h2>
 <p>
 The signature file obtained in the example above will allow
 to classify the current imagery group only (lsat7_2002).
-If the user would like to re-use the signature file for the
+If the user would like to reuse the signature file for the
 classification of different imagery group(s), they can set
 semantic labels for each group member beforehand, i.e.,
 before generating the signature files.
diff --git a/imagery/i.cluster/i.cluster.md b/imagery/i.cluster/i.cluster.md
index fb673d7ecad..d6e4536cfc3 100644
--- a/imagery/i.cluster/i.cluster.md
+++ b/imagery/i.cluster/i.cluster.md
@@ -205,7 +205,7 @@ used. See example in its manual page.
 
 The signature file obtained in the example above will allow to classify
 the current imagery group only (lsat7_2002). If the user would like to
-re-use the signature file for the classification of different imagery
+reuse the signature file for the classification of different imagery
 group(s), they can set semantic labels for each group member beforehand,
 i.e., before generating the signature files. Semantic labels are set by
 means of *r.support* as shown below:
diff --git a/imagery/i.smap/i.smap.html b/imagery/i.smap/i.smap.html
index fedf0bb3560..b805bf9e7d2 100644
--- a/imagery/i.smap/i.smap.html
+++ b/imagery/i.smap/i.smap.html
@@ -181,7 +181,7 @@ <h2>EXAMPLE</h2>
 <p>
 The signature file obtained in the example above will allow
 to classify the current imagery group only (lsat7_2002).
-If the user would like to re-use the signature file for the
+If the user would like to reuse the signature file for the
 classification of different imagery group(s), they can set
 semantic labels for each group member beforehand, i.e.,
 before generating the signature files.
diff --git a/imagery/i.smap/i.smap.md b/imagery/i.smap/i.smap.md
index 7cbfd6d44af..2a709ee1883 100644
--- a/imagery/i.smap/i.smap.md
+++ b/imagery/i.smap/i.smap.md
@@ -149,7 +149,7 @@ r.kappa -w classification=lsat7_2002_smap_classes reference=training
 
 The signature file obtained in the example above will allow to classify
 the current imagery group only (lsat7_2002). If the user would like to
-re-use the signature file for the classification of different imagery
+reuse the signature file for the classification of different imagery
 group(s), they can set semantic labels for each group member beforehand,
 i.e., before generating the signature files. Semantic labels are set by
 means of *r.support* as shown below:
diff --git a/include/grass/iostream/pqheap.h b/include/grass/iostream/pqheap.h
index 7aa0b6b2b88..dd5120da712 100644
--- a/include/grass/iostream/pqheap.h
+++ b/include/grass/iostream/pqheap.h
@@ -163,7 +163,7 @@ class pqheap_t1 {
     inline void delete_min_and_insert(const T &x);
 
     // this function is a dirty way to allow building faster the heap
-    // in case we build it from a sorted array; in that case we dont need
+    // in case we build it from a sorted array; in that case we don't need
     // to 'insert' and then 'heapify', but it is enough to 'set'
     void set(long i, T &elt);
 
@@ -342,7 +342,7 @@ T pqheap_t1<T>::min()
 
 //************************************************************/
 // this function is a dirty hack to allow building faster the heap
-// in case we build it from a sorted array; in thiat case we dont need
+// in case we build it from a sorted array; in that case we don't need
 // to 'insert' and then 'heapify', but it is enough to 'set'
 template <class T>
 inline void pqheap_t1<T>::set(long i, T &elt)
@@ -472,7 +472,7 @@ inline void pqheap_t1<T>::heapify(unsigned int root)
     unsigned int rc = heap_rchild(root);
 
 #ifdef HEAPSTATUS
-    // already did the root, so dont do it again
+    // already did the root, so don't do it again
     if (lc < cur_elts) {
         heaptouch(lc);
     }
diff --git a/lib/cdhc/doc/goodness.tex b/lib/cdhc/doc/goodness.tex
index 843c223e2ce..671ff7b54f6 100644
--- a/lib/cdhc/doc/goodness.tex
+++ b/lib/cdhc/doc/goodness.tex
@@ -1674,7 +1674,7 @@ \section{Utility Functions}
 \clearpage
 
 \begin{table}
-\caption{Signficant Values of D'Agostino's D Test (\(y\) statistic
+\caption{Significant Values of D'Agostino's D Test (\(y\) statistic
 of eqn.~\protect\ref{eqn:xform-d}).}
 \centerline{Reproduced from D'Agostino~\protect\cite{dagostino86}.}
 \label{tbl:d-test}
diff --git a/misc/m.cogo/m.cogo.html b/misc/m.cogo/m.cogo.html
index 4135ed91ecc..f2623f6e59e 100644
--- a/misc/m.cogo/m.cogo.html
+++ b/misc/m.cogo/m.cogo.html
@@ -47,7 +47,7 @@ <h2>DESCRIPTION</h2>
 <h2>NOTES</h2>
 
 For those unfamiliar with the notation for bearings: Picture yourself in the
-center of a circle.  The first hemispere notation tell you whether you should
+center of a circle.  The first hemisphere notation tell you whether you should
 face north or south.  Then you read the angle and either turn that many
 degrees to the east or west, depending on the second hemisphere notation.
 Finally, you move &lt;distance&gt; units in that direction to get to the
diff --git a/misc/m.cogo/m.cogo.md b/misc/m.cogo/m.cogo.md
index 9f8dc253302..ae771e7c0a2 100644
--- a/misc/m.cogo/m.cogo.md
+++ b/misc/m.cogo/m.cogo.md
@@ -43,7 +43,7 @@ Unless specified with the **coord** option, calculations begin from
 ## NOTES
 
 For those unfamiliar with the notation for bearings: Picture yourself in
-the center of a circle. The first hemispere notation tell you whether
+the center of a circle. The first hemisphere notation tell you whether
 you should face north or south. Then you read the angle and either turn
 that many degrees to the east or west, depending on the second
 hemisphere notation. Finally, you move \<distance\> units in that
diff --git a/mswindows/external/rbatch/README.html b/mswindows/external/rbatch/README.html
index 71335b5915a..bcddc2fadaf 100644
--- a/mswindows/external/rbatch/README.html
+++ b/mswindows/external/rbatch/README.html
@@ -4,6 +4,6 @@ <h1>Batchfiles</h1>
 <p>
 Home Page: <a href="http://batchfiles.googlecode.com">batchfiles home page</a>.
 <p>
-Discuss: <a href="http://groups.google.com/group/sqldf">sqldf dicussion group</a> is being used for discussion of this software too.
+Discuss: <a href="http://groups.google.com/group/sqldf">sqldf discussion group</a> is being used for discussion of this software too.
 <p>
 SVN:  <a href="https://code.google.com/p/batchfiles/source/checkout">source</a>
diff --git a/mswindows/external/rbatch/README.md b/mswindows/external/rbatch/README.md
index ed4d130d82d..7e3af643d2a 100644
--- a/mswindows/external/rbatch/README.md
+++ b/mswindows/external/rbatch/README.md
@@ -2,7 +2,7 @@
 
 Home Page: [batchfiles home page](http://batchfiles.googlecode.com).
 
-Discuss: [sqldf dicussion group](http://groups.google.com/group/sqldf)
+Discuss: [sqldf discussion group](http://groups.google.com/group/sqldf)
 is being used for discussion of this software too.
 
 SVN: [source](https://code.google.com/p/batchfiles/source/checkout)
diff --git a/mswindows/external/rbatch/batchfiles.md b/mswindows/external/rbatch/batchfiles.md
index a41f810fc5a..ef6d5df19ef 100644
--- a/mswindows/external/rbatch/batchfiles.md
+++ b/mswindows/external/rbatch/batchfiles.md
@@ -226,7 +226,7 @@ and then enter the same set command into the new window.  Now any use of R in
 the original window will use the default version whereas in the new `cmd` line
 window it will use the specified version.
 
-One can change the registry entry permanently to refer to a particlar version
+One can change the registry entry permanently to refer to a particular version
 like this:
 
 ```bash
diff --git a/ps/ps.map/README b/ps/ps.map/README
index 4082a4fab34..bdd03f32f03 100644
--- a/ps/ps.map/README
+++ b/ps/ps.map/README
@@ -23,7 +23,7 @@ The manual for ps.map says that fields width and hwidth
 specify the width of the line in pixels, which is not true:
 they were actually interpreted as width in user space PostScript
 coordinates: 1/72 of inch. I made the width double, added width options
-for outline and grid, and also now the width ni is isnterpreted as n inches.
+for outline and grid, and also now the width ni is interpreted as n inches.
 
 STATUS:
     FIXED and coming out with the next update
diff --git a/pyproject.toml b/pyproject.toml
index 1d275ba8afe..c9b8a7bb24a 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -42,6 +42,18 @@ ignore-words-list = [
     "parms",
     "siz",
     "vizual",
+    "ETo",    # Evapotranspiration technical term
+    "Eto",    # Evapotranspiration technical term
+    "eto",    # Evapotranspiration technical term
+    "ist",    # Part of acronyms (IST-SUPSI, etc.)
+    "IHS",    # Color model: Intensity-Hue-Saturation
+    "ihs",    # Color model: Intensity-Hue-Saturation
+    "ALOG",   # Function name
+    "Redner", # Person's name in citation
+    "NED",    # Acronym/proper name
+    "linke",  # Linke turbidity factor parameter
+    "infex",  # Infiltration excess parameter
+    "alle",   # Italian word in references
 ]
 quiet-level = 3
 skip = [
diff --git a/python/grass/docs/README.md b/python/grass/docs/README.md
index 9ce87c5656b..a9995587a6e 100644
--- a/python/grass/docs/README.md
+++ b/python/grass/docs/README.md
@@ -10,7 +10,7 @@ Install the following dependencies from the `requirements.txt` file: in
 * [sphinx (v8.1.3)](https://www.sphinx-doc.org/en/master/changes/8.1.html)
 * [sphinx-material (v0.0.36)](https://bashtage.github.io/sphinx-material/)
 * [sphinx-sitemap (v2.6.0)](https://sphinx-sitemap.readthedocs.io/en/latest/)
-* [sphinx-last-updated-by-git](hhttps://github.com/mgeier/sphinx-last-updated-by-git/)
+* [sphinx-last-updated-by-git](https://github.com/mgeier/sphinx-last-updated-by-git/)
 
 ```bash
 pip install -r python/grass/docs/requirements.txt
diff --git a/python/grass/docs/_templates/header.html b/python/grass/docs/_templates/header.html
index 88f309fc56c..bef2ce6f2d8 100644
--- a/python/grass/docs/_templates/header.html
+++ b/python/grass/docs/_templates/header.html
@@ -1,5 +1,5 @@
-<!-- We need this becasue of the Sphinx variable changed names and Sphinx MkDocs hasn't merge the PR
-Fixing the the problem. See https://github.com/bashtage/sphinx-material/pull/133 -->
+<!-- We need this because of the Sphinx variable changed names and Sphinx MkDocs hasn't merged the PR
+Fixing the problem. See https://github.com/bashtage/sphinx-material/pull/133 -->
 <header class="md-header" data-md-component="header">
     <nav class="md-header-nav md-grid">
         <div class="md-flex navheader">
diff --git a/python/grass/tools/session_tools.py b/python/grass/tools/session_tools.py
index e88f13fe6ee..ab000124708 100644
--- a/python/grass/tools/session_tools.py
+++ b/python/grass/tools/session_tools.py
@@ -604,7 +604,7 @@ def __getattr__(self, name):
         """Get a function representing a GRASS tool.
 
         Attribute should be in the form 'r_example_name'. For example, 'r.slope.aspect'
-        is used trough attribute 'r_slope_aspect'.
+        is used through attribute 'r_slope_aspect'.
         """
         if not self._name_resolver:
             self._name_resolver = ToolFunctionResolver(
diff --git a/raster/r.mapcalc/r.mapcalc.md b/raster/r.mapcalc/r.mapcalc.md
index 6962fe8bf32..964fb3f6cbe 100644
--- a/raster/r.mapcalc/r.mapcalc.md
+++ b/raster/r.mapcalc/r.mapcalc.md
@@ -863,7 +863,7 @@ r.mapcalc is parallelized using OpenMP. The number of threads can be controlled
 with the **nprocs** parameter. Note that more complex expressions can benefit
 from more threads. By default (**nprocs=0**), r.mapcalc uses all available threads.
 Use the **--verbose** flag to display the number of threads in use.
-If you observe reduced performance when using many threads, try lowering ther number.
+If you observe reduced performance when using many threads, try lowering the number.
 
 Note: r.mapcalc may disable parallelization in certain cases, even when requested:
 
diff --git a/raster/r.neighbors/r.neighbors.html b/raster/r.neighbors/r.neighbors.html
index fb4faca576d..3d2c403e266 100644
--- a/raster/r.neighbors/r.neighbors.html
+++ b/raster/r.neighbors/r.neighbors.html
@@ -231,7 +231,7 @@ <h3>OPTIONS</h3>
 text file. For example, to calculate the focal mean with a matrix
 <b>size</b> of 3,
 <div class="code"><pre>
-r.neigbors in=input.map out=output.map size=3 weighting_function=file \
+r.neighbors in=input.map out=output.map size=3 weighting_function=file \
 weight=weights.txt
 </pre></div>
 
diff --git a/raster/r.neighbors/r.neighbors.md b/raster/r.neighbors/r.neighbors.md
index 57ac8b3098c..4455d905130 100644
--- a/raster/r.neighbors/r.neighbors.md
+++ b/raster/r.neighbors/r.neighbors.md
@@ -203,7 +203,7 @@ text file. For example, to calculate the focal mean with a matrix
 **size** of 3,
 
 ```sh
-r.neigbors in=input.map out=output.map size=3 weighting_function=file \
+r.neighbors in=input.map out=output.map size=3 weighting_function=file \
 weight=weights.txt
 ```
 
diff --git a/raster/r.out.gdal/r.out.gdal.md b/raster/r.out.gdal/r.out.gdal.md
index fe21391c9dd..88e328cf70c 100644
--- a/raster/r.out.gdal/r.out.gdal.md
+++ b/raster/r.out.gdal/r.out.gdal.md
@@ -108,7 +108,7 @@ to issue an error message describing the problem and exit without
 exporting. However, depending on the data size, data loss tests may take
 some time. For performance reasons, those tests can therefore be skipped
 if both the **-f** flag, the **nodata** option and the **type**
-option are given. Here the assumtion is that the user has made a
+option are given. Here the assumption is that the user has made a
 deliberate choice about those settings and considered the potential risk
 for data loss when forcing the export with the **-f** flag.
 
diff --git a/raster/r.out.vtk/r.out.vtk.html b/raster/r.out.vtk/r.out.vtk.html
index 51d15eac20a..8921b49c4d1 100644
--- a/raster/r.out.vtk/r.out.vtk.html
+++ b/raster/r.out.vtk/r.out.vtk.html
@@ -34,7 +34,7 @@ <h2>NOTES</h2>
 <ul>
 <li><i>structured points</i> with <i>celldata</i> or <i>pointdata</i> if no elevationfile is given</li>
 
-<li><i>structured grid</i> (not recommendet) with <i>pointdata</i> if an elevationfile is given</li>
+<li><i>structured grid</i> (not recommended) with <i>pointdata</i> if an elevationfile is given</li>
 <li><i>polydataset</i> with <i>pointdata</i> if an elevationfile is given (default)</li>
 </ul>
 and puts this in a simple VTK-ASCII file. Nor XML or
diff --git a/raster/r.out.vtk/r.out.vtk.md b/raster/r.out.vtk/r.out.vtk.md
index c7fc2f2c889..01d892be6b5 100644
--- a/raster/r.out.vtk/r.out.vtk.md
+++ b/raster/r.out.vtk/r.out.vtk.md
@@ -32,7 +32,7 @@ This filter generates:
 
 - *structured points* with *celldata* or *pointdata* if no elevationfile
   is given
-- *structured grid* (not recommendet) with *pointdata* if an
+- *structured grid* (not recommended) with *pointdata* if an
   elevationfile is given
 - *polydataset* with *pointdata* if an elevationfile is given (default)
 
diff --git a/raster/r.proj/r.proj.html b/raster/r.proj/r.proj.html
index 80bf9f8efa3..7a2f9d2879a 100644
--- a/raster/r.proj/r.proj.html
+++ b/raster/r.proj/r.proj.html
@@ -141,7 +141,7 @@ <h3>Design of r.proj</h3>
 methods for the local interpolation step are provided.
 
 <p><em>r.proj</em> supports general datum transformations, making use of
-the <em>PROJ</em> co-ordinate system translation library.
+the <em>PROJ</em> coordinate system translation library.
 
 <h2>NOTES</h2>
 
diff --git a/raster/r.proj/r.proj.md b/raster/r.proj/r.proj.md
index ece211a3902..587232f03f8 100644
--- a/raster/r.proj/r.proj.md
+++ b/raster/r.proj/r.proj.md
@@ -135,7 +135,7 @@ categorical versus numerical data. Note that three methods for the local
 interpolation step are provided.
 
 *r.proj* supports general datum transformations, making use of the
-*PROJ* co-ordinate system translation library.
+*PROJ* coordinate system translation library.
 
 ## NOTES
 
diff --git a/raster/r.smooth.edgepreserve/r.smooth.edgepreserve.md b/raster/r.smooth.edgepreserve/r.smooth.edgepreserve.md
index edce8c07aac..f256947beb1 100644
--- a/raster/r.smooth.edgepreserve/r.smooth.edgepreserve.md
+++ b/raster/r.smooth.edgepreserve/r.smooth.edgepreserve.md
@@ -9,7 +9,7 @@ and works to preserve sharp transitions between different regions.
 
 ![An example of smoothed image](r_smooth_edgepreserve.jpg)  
 *Figure: "A" is the original (unsmoothed) raster and
-"B" is the smoothed version (with quite agressive settings to emphasize
+"B" is the smoothed version (with quite aggressive settings to emphasize
 smoothing effects).*
 
 The module supports three types of diffusivity (conductance) functions:
diff --git a/raster/r.viewshed/r.viewshed.html b/raster/r.viewshed/r.viewshed.html
index 83df7a2e25b..d7e111ba30f 100644
--- a/raster/r.viewshed/r.viewshed.html
+++ b/raster/r.viewshed/r.viewshed.html
@@ -132,7 +132,7 @@ <h3>The algorithm</h3>
 <sup>1/2</sup>)</em> cells that intersect the LOS. If we test every
 single such cell for every point in the grid, this adds up to
 <em>O(n<sup>3/2</sup>)</em> tests. We can do all these tests faster if
-we re-use information from one point to the next (two grid points that
+we reuse information from one point to the next (two grid points that
 are close to each other will be intersected by a lot of the same
 points) and organize the computation differently.
 
diff --git a/raster/r.viewshed/r.viewshed.md b/raster/r.viewshed/r.viewshed.md
index 37091a98155..1ee7fec2ec3 100644
--- a/raster/r.viewshed/r.viewshed.md
+++ b/raster/r.viewshed/r.viewshed.md
@@ -112,7 +112,7 @@ line-of-sight and its intersections with the cells in the terrain. For a
 (square) grid of *n* cells, there can be *O(n^1/2)* cells
 that intersect the LOS. If we test every single such cell for every
 point in the grid, this adds up to *O(n^3/2)* tests. We can do
-all these tests faster if we re-use information from one point to the
+all these tests faster if we reuse information from one point to the
 next (two grid points that are close to each other will be intersected
 by a lot of the same points) and organize the computation differently.
 
diff --git a/raster/r.what/testsuite/test_r_what.py b/raster/r.what/testsuite/test_r_what.py
index 8932699f5b4..072bc462291 100644
--- a/raster/r.what/testsuite/test_r_what.py
+++ b/raster/r.what/testsuite/test_r_what.py
@@ -19,7 +19,7 @@ class TestRasterWhat(TestCase):
     map2 = "landuse96_28m,aspect"
     coordinates = (633614.08, 224125.12, 632972.36, 225382.87)
     points = "comm_colleges"
-    refrence_points = """145096.8591495|154534.264883875||39
+    reference_points = """145096.8591495|154534.264883875||39
 616341.4371495|146049.750883875||51
 410595.7191495|174301.828883875||71
 734153.6871495|169168.437883875||107
@@ -78,10 +78,10 @@ class TestRasterWhat(TestCase):
 511235.1561495|135372.358883875||7
 332533.5941495|242831.139883875||121
 """
-    refrence_coordinates = """633614.08|224125.12||2|209.5939
+    reference_coordinates = """633614.08|224125.12||2|209.5939
 632972.36|225382.87||15|140.7571
 """
-    refrence_cats = """1|145096.8591495|154534.264883875||39
+    reference_cats = """1|145096.8591495|154534.264883875||39
 2|616341.4371495|146049.750883875||51
 3|410595.7191495|174301.828883875||71
 4|734153.6871495|169168.437883875||107
@@ -140,7 +140,7 @@ class TestRasterWhat(TestCase):
 57|511235.1561495|135372.358883875||7
 58|332533.5941495|242831.139883875||121
 """
-    refrence_csv = """easting,northing,site_name,boundary_county_500m
+    reference_csv = """easting,northing,site_name,boundary_county_500m
 145096.8591495,154534.264883875,,39
 616341.4371495,146049.750883875,,51
 410595.7191495,174301.828883875,,71
@@ -200,7 +200,7 @@ class TestRasterWhat(TestCase):
 511235.1561495,135372.358883875,,7
 332533.5941495,242831.139883875,,121"""
 
-    refrence_flag_i = """145096.8591495|154534.264883875||39
+    reference_flag_i = """145096.8591495|154534.264883875||39
 616341.4371495|146049.750883875||51
 410595.7191495|174301.828883875||71
 734153.6871495|169168.437883875||107
@@ -259,7 +259,7 @@ class TestRasterWhat(TestCase):
 511235.1561495|135372.358883875||7
 332533.5941495|242831.139883875||121
 """
-    refrence_flag_f = """145096.8591495|154534.264883875||39|
+    reference_flag_f = """145096.8591495|154534.264883875||39|
 616341.4371495|146049.750883875||51|
 410595.7191495|174301.828883875||71|
 734153.6871495|169168.437883875||107|
@@ -318,7 +318,7 @@ class TestRasterWhat(TestCase):
 511235.1561495|135372.358883875||7|
 332533.5941495|242831.139883875||121|
 """
-    refrence_flag_r = """145096.8591495|154534.264883875||39|006:255:000
+    reference_flag_r = """145096.8591495|154534.264883875||39|006:255:000
 616341.4371495|146049.750883875||51|000:255:071
 410595.7191495|174301.828883875||71|000:255:199
 734153.6871495|169168.437883875||107|000:080:255
@@ -377,7 +377,7 @@ class TestRasterWhat(TestCase):
 511235.1561495|135372.358883875||7|211:255:000
 332533.5941495|242831.139883875||121|010:000:255
 """
-    refrence_cache = """145096.8591495|154534.264883875||39
+    reference_cache = """145096.8591495|154534.264883875||39
 616341.4371495|146049.750883875||51
 410595.7191495|174301.828883875||71
 734153.6871495|169168.437883875||107
@@ -472,7 +472,7 @@ def test_raster_what_points(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_points,
+            reference=self.reference_points,
             msg="test_raster_what_points did't run successfully",
         )
 
@@ -482,7 +482,7 @@ def test_raster_what_coordinates(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_coordinates,
+            reference=self.reference_coordinates,
             msg="test_raster_what_coordinates did't run successfully",
         )
 
@@ -492,7 +492,7 @@ def test_raster_what_cats(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_cats,
+            reference=self.reference_cats,
             msg="test_raster_what_cats did't run successfully",
         )
 
@@ -511,7 +511,7 @@ def test_raster_what_csv(self):
             fileData = result_path.read_text()
             self.assertLooksLike(
                 actual=fileData,
-                reference=self.refrence_csv,
+                reference=self.reference_csv,
                 msg="test_raster_what_csv did't run successfully",
             )
 
@@ -521,7 +521,7 @@ def test_raster_what_points_flag_i(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_flag_i,
+            reference=self.reference_flag_i,
             msg="test_raster_what_cats did't run successfully",
         )
 
@@ -531,7 +531,7 @@ def test_raster_what_points_flag_f(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_flag_f,
+            reference=self.reference_flag_f,
             msg="test_raster_what_cats did't run successfully",
         )
 
@@ -541,7 +541,7 @@ def test_raster_what_points_flag_r(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_flag_r,
+            reference=self.reference_flag_r,
             msg="test_raster_what_cats did't run successfully",
         )
 
@@ -553,13 +553,13 @@ def test_raster_what_cache(self):
         module.run()
         self.assertLooksLike(
             actual=str(module.outputs.stdout),
-            reference=self.refrence_cache,
+            reference=self.reference_cache,
             msg="test_raster_what_cats did't run successfully",
         )
 
     def test_raster_what_json(self):
         """Testing r.what runs successfully with input coordinates given as a vector points map and JSON output"""
-        reference = self.convert_plain_to_json(self.refrence_points)
+        reference = self.convert_plain_to_json(self.reference_points)
         module = SimpleModule(
             "r.what", map=self.map1, points=self.points, format="json"
         )
@@ -572,7 +572,7 @@ def test_raster_what_json(self):
 
     def test_raster_what_points_flag_r_json(self):
         """Testing r.what runs successfully with flag r and json output"""
-        reference = self.convert_plain_to_json(self.refrence_flag_r)
+        reference = self.convert_plain_to_json(self.reference_flag_r)
         module = SimpleModule(
             "r.what", map=self.map1, points=self.points, flags="r", format="json"
         )
diff --git a/scripts/m.proj/m.proj.html b/scripts/m.proj/m.proj.html
index b8015206b28..eb2f6675e41 100644
--- a/scripts/m.proj/m.proj.html
+++ b/scripts/m.proj/m.proj.html
@@ -181,7 +181,7 @@ <h3>Custom projection parameter usage</h3>
 not specified for the input projection. The datum specified for the
 output projection will thus be silently ignored and may be left out;
 all that is achieved a simple conversion from projected to geodetic
-co-ordinates, keeping the same datum (and thus also the same
+coordinates, keeping the same datum (and thus also the same
 ellipsoid).
 
 <p>
diff --git a/scripts/m.proj/m.proj.md b/scripts/m.proj/m.proj.md
index df957247adc..cebbc155291 100644
--- a/scripts/m.proj/m.proj.md
+++ b/scripts/m.proj/m.proj.md
@@ -172,7 +172,7 @@ In this example no datum transformation will take place as a datum was
 not specified for the input projection. The datum specified for the
 output projection will thus be silently ignored and may be left out; all
 that is achieved a simple conversion from projected to geodetic
-co-ordinates, keeping the same datum (and thus also the same ellipsoid).
+coordinates, keeping the same datum (and thus also the same ellipsoid).
 
 For more usage examples, see the documentation for the
 [PROJ](https://proj.org) *cs2cs* program.
diff --git a/scripts/v.dissolve/v.dissolve.html b/scripts/v.dissolve/v.dissolve.html
index f6e3444540a..f572aef4b4e 100644
--- a/scripts/v.dissolve/v.dissolve.html
+++ b/scripts/v.dissolve/v.dissolve.html
@@ -34,7 +34,7 @@ <h3>Attribute aggregation</h3>
 the <b>aggregate_backend</b> parameter) are available, <em>univar</em>
 and <em>sql</em>. The backend is determined automatically based on the
 requested methods. When the function is one of the <em>SQL</em>
-build-in aggregate functions, the <em>sql</em> backend is used.
+built-in aggregate functions, the <em>sql</em> backend is used.
 Otherwise, the <em>univar</em> backend is used.
 
 <p>
diff --git a/scripts/v.dissolve/v.dissolve.md b/scripts/v.dissolve/v.dissolve.md
index 6173f5690cc..78e37100052 100644
--- a/scripts/v.dissolve/v.dissolve.md
+++ b/scripts/v.dissolve/v.dissolve.md
@@ -28,7 +28,7 @@ aggregation methods. The specific methods available depend on the
 backend used for aggregation. Two aggregate backends (specified with the
 **aggregate_backend** parameter) are available, *univar* and *sql*. The
 backend is determined automatically based on the requested methods. When
-the function is one of the *SQL* build-in aggregate functions, the *sql*
+the function is one of the *SQL* built-in aggregate functions, the *sql*
 backend is used. Otherwise, the *univar* backend is used.
 
 The default behavior is intended for interactive use and testing. For
diff --git a/vector/v.generalize/v.generalize.html b/vector/v.generalize/v.generalize.html
index 04ba92c01fe..2a238bfea5e 100644
--- a/vector/v.generalize/v.generalize.html
+++ b/vector/v.generalize/v.generalize.html
@@ -264,7 +264,7 @@ <h3>NETWORK GENERALIZATION</h3>
 that if closeness_thresh=0 then everything is selected.
 </li>
 <li>
-<b>betweeness_thresh</b> - Again, only the lines with a betweeness
+<b>betweeness_thresh</b> - Again, only the lines with a betweenness
 centrality measure at least <b>betweeness_thresh</b> are selected. This
 value is always positive and is larger for large networks. It denotes to
 what extent a line is in between the other lines in the network. This
diff --git a/vector/v.generalize/v.generalize.md b/vector/v.generalize/v.generalize.md
index 074f61366fa..b0be18bf073 100644
--- a/vector/v.generalize/v.generalize.md
+++ b/vector/v.generalize/v.generalize.md
@@ -236,7 +236,7 @@ the following parameters:
   This means that this parameter can be used for selecting the centre(s)
   of a network. Note that if closeness_thresh=0 then everything is
   selected.
-- **betweeness_thresh** - Again, only the lines with a betweeness
+- **betweeness_thresh** - Again, only the lines with a betweenness
   centrality measure at least **betweeness_thresh** are selected. This
   value is always positive and is larger for large networks. It denotes
   to what extent a line is in between the other lines in the network.
diff --git a/vector/v.proj/v.proj.md b/vector/v.proj/v.proj.md
index 0c9d3e676d0..44d9a42ae4e 100644
--- a/vector/v.proj/v.proj.md
+++ b/vector/v.proj/v.proj.md
@@ -23,7 +23,7 @@ If **smax** is set to **0** the automated vertex densification is
 disabled (not recommended).
 
 *v.proj* supports general datum transformations, making use of the
-*PROJ* co-ordinate system translation library.
+*PROJ* coordinate system translation library.
 
 When projecting into a latlon project, east coordinates are wrapped by
 the proj4 library to fit into the range -180,180. This is in most cases
diff --git a/vector/vectorintro.html b/vector/vectorintro.html
index c09aedfbf06..a82506c9d51 100644
--- a/vector/vectorintro.html
+++ b/vector/vectorintro.html
@@ -327,7 +327,7 @@ <h3>Vector network analysis</h3>
      <a href="v.net.alloc.html">v.net.alloc</a></li>
 <li> Iso-distances (from centers): <a href="v.net.iso.html">v.net.iso</a></li>
 <li> Computes bridges and articulation points: <a href="v.net.bridge.html">v.net.bridge</a></li>
-<li> Computes degree, centrality, betweeness, closeness and eigenvector centrality measures: <a href="v.net.centrality.html">v.net.centrality</a></li>
+<li> Computes degree, centrality, betweenness, closeness and eigenvector centrality measures: <a href="v.net.centrality.html">v.net.centrality</a></li>
 <li> Computes strongly and weakly connected components: <a href="v.net.components.html">v.net.components</a></li>
 <li> Computes vertex connectivity between two sets of nodes: <a href="v.net.connectivity.html">v.net.connectivity</a></li>
 <li> Computes shortest distance via the network between the given sets of features: <a href="v.net.distance.html">v.net.distance</a></li>
diff --git a/vector/vectorintro.md b/vector/vectorintro.md
index 3eb22cd856e..cb0f8a2314b 100644
--- a/vector/vectorintro.md
+++ b/vector/vectorintro.md
@@ -284,7 +284,7 @@ algorithms are implemented:
 - Iso-distances (from centers): [v.net.iso](v.net.iso.md)
 - Computes bridges and articulation points:
   [v.net.bridge](v.net.bridge.md)
-- Computes degree, centrality, betweeness, closeness and eigenvector
+- Computes degree, centrality, betweenness, closeness and eigenvector
   centrality measures: [v.net.centrality](v.net.centrality.md)
 - Computes strongly and weakly connected components:
   [v.net.components](v.net.components.md)