replace <tt>...</tt> with <code>...</code>

db/db.connect/db.connect.html

@@ -9,7 +9,7 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-Values are stored in the mapset's <tt>VAR</tt> file;
+Values are stored in the mapset's <code>VAR</code> file;
 the connection is not tested for validity.
 <p>The <b>-p</b> flag will display the current connection parameters.
 <p>The <b>-c</b> flag will silently check if the connection parameters have

db/db.execute/db.execute.html

@@ -76,7 +76,7 @@ <h2>EXAMPLES</h2>
 </pre></div>
 
 Update attribute with multiple SQL instructions in file
-(e.g., <tt>file.sql</tt>, instruction line must end with a semicolon):
+(e.g., <code>file.sql</code>, instruction line must end with a semicolon):
 <div class="code"><pre>
 UPDATE roads SET travelcost=5 WHERE cat=1;
 UPDATE roads SET travelcost=2 WHERE cat=2;

db/db.login/db.login.html

@@ -15,8 +15,8 @@ <h2>NOTE</h2>
 file in the user account, specifically
 
 <ul>
-<li> in the 'home' directory, i.e. <tt>$HOME/.grass8/dblogin</tt> (Unix-like systems)</li>
-<li> <tt>%APPDATA%\Roaming\GRASS8\dblogin</tt> (MS-Windows)</li>
+<li> in the 'home' directory, i.e. <code>$HOME/.grass8/dblogin</code> (Unix-like systems)</li>
+<li> <code>%APPDATA%\Roaming\GRASS8\dblogin</code> (MS-Windows)</li>
 </ul>
 
 Only the file owner can access this file.

db/drivers/postgres/grass-pg.html

@@ -5,7 +5,7 @@
 
 <h2>Creating a PostgreSQL database</h2>
 
-A new database is created with <tt>createdb</tt>, see
+A new database is created with <code>createdb</code>, see
 the <a href="https://www.postgresql.org/docs/manuals/">PostgreSQL
 manual</a> for details.
 
@@ -115,14 +115,14 @@ <h3>Example: Import from PostGIS</h3>
 <h4>Geometry Converters</h4>
 <ul>
 <li><a href="https://postgis.net/workshops/postgis-intro/loading_data.html#loading-with-shp2pgsql">PostGIS with shp2pgsql</a>:<br>
- <tt>shp2pgsql -D lakespy2 lakespy2 test &gt; lakespy2.sql</tt>
+ <code>shp2pgsql -D lakespy2 lakespy2 test &gt; lakespy2.sql</code>
 </li>
 <li><a href="https://e00pg.sourceforge.net/">e00pg</a>: E00 to PostGIS filter,
 see also <em><a href="v.in.e00.html">v.in.e00</a></em>.
 </li>
 <li>GDAL/OGR <a href="https://gdal.org/">ogrinfo and ogr2ogr</a>:
 GIS vector format converter and library, e.g. ArcInfo or SHAPE to PostGIS.<br>
-  <tt>ogr2ogr -f "PostgreSQL" shapefile ??</tt>
+  <code>ogr2ogr -f "PostgreSQL" shapefile ??</code>
 </li>
 </ul>
 

display/d.graph/d.graph.html

@@ -132,10 +132,10 @@ <h2>COMMANDS</h2>
 <dt><a name="symbol"></a><b>symbol</b> <em>type size xper yper [line_color [fill_color]]</em></dt>
 <dd>A symbol is drawn at the given size on the display monitor. The
 <em>xper</em> and <em>yper</em> options define the center of the icon and
-are given as a percentage of the display frame (<tt>0,0</tt> is lower left).
-The symbol can be any of those stored in <tt>$GISBASE/etc/symbol/</tt>
+are given as a percentage of the display frame (<code>0,0</code> is lower left).
+The symbol can be any of those stored in <code>$GISBASE/etc/symbol/</code>
 (e.g. <i>basic/circle</i>) or stored in the user's mapset directory in the
-form <tt>$MAPSET/symbol/</tt><em>type/name</em>.
+form <code>$MAPSET/symbol/</code><em>type/name</em>.
 The colors may be either a standard color name, an R:G:B triplet,
 or "none". If using an R:G:B triplet, each color value can range from 0-255.
 If not specified the default <em>line_color</em> is black and the default

display/d.grid/d.grid.html

@@ -9,7 +9,7 @@ <h2>DESCRIPTION</h2>
 If the user provides a <b>-g</b> flag a geographic (projected) grid
 will be drawn. With the <b>-g</b> flag the <b>size</b>
 argument accepts both decimal degrees and colon separated
-ddd:mm:ss coordinates (eg. <tt>00:30:00</tt> for half of a degree).
+ddd:mm:ss coordinates (eg. <code>00:30:00</code> for half of a degree).
 A geographic grid cannot be drawn for a <em>latitude/longitude</em>
 or <em>XY</em> projection.
 

display/d.labels/d.labels.html

@@ -7,7 +7,7 @@ <h2>DESCRIPTION</h2>
 the <em><a href="v.label.html">v.label</a></em> program or simply created
 by the user as an ASCII file (using a text editor) and placed in the
 appropriate directory under the user's current mapset and project
-(i.e. <tt>$MAPSET/paint/labels/</tt>).
+(i.e. <code>$MAPSET/paint/labels/</code>).
 
 <h2>NOTES</h2>
 

display/d.linegraph/d.linegraph.html

@@ -24,7 +24,7 @@ <h3>File inputs</h3>
 should) be only relative paths to these files. While this is not recommended
 for scripting, it can be advantageous when typing the paths
 manually. For example when all files are stored in the directory
-<tt>/home/john/data</tt>, the user can provide the following in the command
+<code>/home/john/data</code>, the user can provide the following in the command
 line:
 
 <div class="code"><pre>
@@ -145,7 +145,7 @@ <h2>EXAMPLE</h2>
 -->
 
 <p>
-The next command sequence creates a file <tt>plot.png</tt> in the current
+The next command sequence creates a file <code>plot.png</code> in the current
 directory which is the drawing made by <em>d.linegraph</em>.
 
 <div class="code"><pre>

display/d.mon/d.mon.html

@@ -52,8 +52,8 @@ <h3>Releasing (unselecting) a monitor</h3>
 <h2>NOTES</h2>
 
 <em>d.mon</em> is designed for interactive use. If non-interactive use
-is needed (e.g., in a script) set <tt>GRASS_RENDER_IMMEDIATE=png</tt>
-(or <tt>=cairo</tt>) and use the related environment
+is needed (e.g., in a script) set <code>GRASS_RENDER_IMMEDIATE=png</code>
+(or <code>=cairo</code>) and use the related environment
 <a href="variables.html">variables</a> to control output size etc.
 
 <h2>EXAMPLES</h2>
@@ -73,7 +73,7 @@ <h3>wx0 monitor</h3>
 <i>Figure: The initialization of display monitor wx0</i>
 </div>
 
-All subsequently displayed data will be rendered on monitor <tt>wx0</tt>.
+All subsequently displayed data will be rendered on monitor <code>wx0</code>.
 
 <div class="code"><pre>
 g.region raster=elevation -p
@@ -95,7 +95,7 @@ <h3>CAIRO file renderer monitor</h3>
 </pre></div>
 
 From this moment on all displayed data will be rendered into
-file <tt>output.pdf</tt>.
+file <code>output.pdf</code>.
 
 <h3>List running monitors</h3>
 

display/d.path/d.path.html

@@ -10,7 +10,7 @@ <h2>NOTE</h2>
 
 <!-- TODO: apparently d.path does not render into wxGUI? -->
 The user needs to display a vector map before using d.path. If no graphics monitor
-is open, a file <tt>map.png</tt> is generated in the current directory.
+is open, a file <code>map.png</code> is generated in the current directory.
 
 <p>
 The 'from' and 'to' points are entered by mouse into the map displayed in the GRASS monitor,

display/d.rast.arrow/d.rast.arrow.html

@@ -17,7 +17,7 @@ <h2>DESCRIPTION</h2>
 of that category.
 Cells containing null data will be marked with an "X".
 You can disable drawing of null data and unknown aspect values by
-setting its color to "<tt>none</tt>".
+setting its color to "<code>none</code>".
 
 <p>When specifying the <em>magnitude_map</em> option, arrow lengths
 denoting magnitude will be extracted from the cell values of the specified
@@ -35,7 +35,7 @@ <h2>DESCRIPTION</h2>
 the raster map is relatively close in scale. You can use the <em>skip</em>
 option to draw arrows every n-th cell in both directions if you are working
 with relatively high resolutions. It may be useful to disable the grid in
-this case, which is accomplished by setting its color to "<tt>none</tt>".
+this case, which is accomplished by setting its color to "<code>none</code>".
 <p>For GRASS and Compass type aspect maps, the cell values of the aspect map
 will determine the corresponding direction in 360 degrees. ANSWERS type aspect
 maps will be plotted in multiples of 15 degrees counterclockwise from east, and

display/d.vect.thematic/d.vect.thematic.html

@@ -40,8 +40,8 @@ <h3>Thematic map with classes</h3>
 
 <h3>Thematic map with calculated class breaks</h3>
 
-The following example uses a calculated attribute (<tt>density =
-pop/area</tt>) and the standard deviation algorithm to calculate class
+The following example uses a calculated attribute (<code>density =
+pop/area</code>) and the standard deviation algorithm to calculate class
 breaks for 5 classes:
 
 <div class="code"><pre>

display/d.vect/d.vect.html

@@ -5,14 +5,14 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-<em>d.vect</em> can simply be used typing <tt>d.vect
-map=vector_map</tt>. There are a large variety of optional parameters
+<em>d.vect</em> can simply be used typing <code>d.vect
+map=vector_map</code>. There are a large variety of optional parameters
 which allow the user to specify vector type, colors, data fields, SQL
 queries, label size and justification, etc.
 
 <p>When <em>d.vect</em> is used with <b>where</b> parameter on MS Windows
-Command Prompt, it is important to use <tt>&#710;</tt>
-carret symbol for escaping special characters <tt>&lt; &gt; ( ) &amp; &#124; , ; &quot;</tt>.
+Command Prompt, it is important to use <code>&#710;</code>
+carret symbol for escaping special characters <code>&lt; &gt; ( ) &amp; &#124; , ; &quot;</code>.
 <div class="code"><pre>
 d.vect map=vector_map where="cat &#710;&gt; 10 AND cat &#710;&lt; 20"
 </pre></div>
@@ -32,7 +32,7 @@ <h2>NOTES</h2>
 
 <p>Feature colors may be specified
 by <em><a href="v.colors.html">v.colors</a></em> in a form of color
-table or in an attribute table column containing <tt>RRR:GGG:BBB</tt>
+table or in an attribute table column containing <code>RRR:GGG:BBB</code>
 values.
 
 <p>A table for a vector map might look like this:

display/displaydrivers.html

@@ -3,7 +3,7 @@
 
 The current command line rendering mechanism is direct rendering into
 a file. The driver is selected by setting
-the <tt>GRASS_RENDER_IMMEDIATE</tt> variable or by
+the <code>GRASS_RENDER_IMMEDIATE</code> variable or by
 running <em><a href="d.mon.html">d.mon</a></em> module.
 
 <p>

general/g.filename/g.filename.html

@@ -6,7 +6,7 @@ <h2>DESCRIPTION</h2>
 <p>The list of element names to search for is not fixed; any subdirectory of the
 mapset directory is a valid element name.
 <p>However, the user can find the list of standard GRASS GIS element names in
-the file <tt>$GISBASE/etc/element_list</tt>. This is the file which
+the file <code>$GISBASE/etc/element_list</code>. This is the file which
 g.remove/g.rename/g.copy use to determine which files need to be
 deleted/renamed/copied for a given entity type.
 

general/g.findfile/g.findfile.html

@@ -7,7 +7,7 @@ <h2>DESCRIPTION</h2>
 <p>The list of <b>element</b> names to search for is not fixed; any
 subdirectory of the mapset directory is a valid <b>element</b> name.
 <p>However, the user can find the list of standard GRASS <b>element</b>
-names in the file <tt>$GISBASE/etc/element_list</tt>. This is the file
+names in the file <code>$GISBASE/etc/element_list</code>. This is the file
 which <em><a href="g.remove.html">g.remove</a></em>, <em><a href="g.rename.html">g.rename</a></em>
 and <em><a href="g.copy.html">g.copy</a></em> use to determine which files
 need to be deleted/renamed/copied for a given entity type.

general/g.gisenv/g.gisenv.html

@@ -49,7 +49,7 @@ <h2>OPTIONS</h2>
 &quot;project&quot; directory itself contains subdirectories called
 &quot;mapsets&quot;; each &quot;mapset&quot; stores &quot;data base
 elements&quot; - the directories (e.g.,
-the <tt>cell</tt>, <tt>cellhd</tt>, <tt>vector</tt>, etc., directories)
+the <code>cell</code>, <code>cellhd</code>, <code>vector</code>, etc., directories)
 in which GRASS data files are actually stored.
 
 <dt><em>LOCATION_NAME</em>
@@ -121,7 +121,7 @@ <h2>OPTIONS</h2>
 The full path to the current mapset is determined
 from <em>GISDBASE</em>, <em>LOCATION_NAME</em>, <em>MAPSET</em>
 variables, in the example
-above: <tt>/opt/grassdata/spearfish/PERMANENT</tt>. The full path can
+above: <code>/opt/grassdata/spearfish/PERMANENT</code>. The full path can
 be printed using <em>g.gisenv</em> by providing multiple variables:
 
 <div class="code"><pre>
@@ -149,7 +149,7 @@ <h2>NOTES</h2>
 By default the GRASS variables are stored in <em>gisrc</em> file
 (defined by environmental
 variable <em>GISRC</em>). If <b>store=mapset</b> is given then the
-variables are stored in <tt>&lt;gisdbase&gt;/&lt;project&gt;/&lt;mapset&gt;/VAR</tt>
+variables are stored in <code>&lt;gisdbase&gt;/&lt;project&gt;/&lt;mapset&gt;/VAR</code>
 after the current GRASS session is closed.
 
 <h2>EXAMPLES</h2>

general/g.gui/g.gui.html

@@ -11,18 +11,18 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-If the <b>-d</b> update flag is given or the <tt>GRASS_GUI</tt>
+If the <b>-d</b> update flag is given or the <code>GRASS_GUI</code>
 environmental <a href="variables.html">variable</a> is unset, then
-the GRASS internal variable <tt>GUI</tt> is permanently changed and
+the GRASS internal variable <code>GUI</code> is permanently changed and
 the selected <b>ui</b> will be used as the default UI from then on.
 
 <p>
 All GRASS internal variables (see <em><a href="g.gisenv.html">g.gisenv</a></em>)
 are stored in the user's home directory in a hidden file called
-<tt>$HOME/.grass8/rc</tt> on Unix-based operating systems
-and <tt>%APPDATA%\GRASS8\rc</tt> on MS Windows. Note that these GRASS
+<code>$HOME/.grass8/rc</code> on Unix-based operating systems
+and <code>%APPDATA%\GRASS8\rc</code> on MS Windows. Note that these GRASS
 internal variables are not the shell environment variables and the
-<tt>rc</tt> file is not a classic UNIX run command file, it just
+<code>rc</code> file is not a classic UNIX run command file, it just
 contains persistent GRASS variables.
 
 <h2>EXAMPLES</h2>

general/g.list/g.list.html

@@ -42,7 +42,7 @@ <h3>Mapset search path</h3>
 If <b>mapset</b> is not specified, then <em>g.list</em> searches for
 data files in the mapsets that are included in the search path
 (defined by <em><a href="g.mapsets.html">g.mapsets</a></em>).
-See <tt>g.mapsets -p</tt>.
+See <code>g.mapsets -p</code>.
 
 <div class="code"><pre>
 g.list rast -p
@@ -66,7 +66,7 @@ <h3>Mapset search path</h3>
 <!-- better quote * as "*"? -->
 Similarly, <b>mapset</b>=* (one asterisk) prints data files from all
 available mapsets also including those that are not listed in the
-current search path (see <tt>g.mapsets -l</tt>).
+current search path (see <code>g.mapsets -l</code>).
 
 <div class="code"><pre>
 g.list rast mapset=* -p
@@ -177,7 +177,7 @@ <h3>Maps whose region overlaps with a saved region</h3>
 g.list type=rast,vect region=*
 </pre></div>
 
-Note that, without <tt>region=*</tt>, <tt>g.list type=rast,vect</tt> simply
+Note that, without <code>region=*</code>, <code>g.list type=rast,vect</code> simply
 lists all available raster and vector maps from the current search path
 regardless of their region.
 

general/g.mapset/g.mapset.html

@@ -4,7 +4,7 @@ <h2>DESCRIPTION</h2>
 as location), or GISDBASE (directory with one or more projects).
 
 <p>
-With <em>g.mapset</em>, the shell history (i.e. <tt>.bash_history</tt> file
+With <em>g.mapset</em>, the shell history (i.e. <code>.bash_history</code> file
 of the initial project will be used to record the command history.
 
 <h2>NOTES</h2>

general/g.mapsets/g.mapsets.html

@@ -26,7 +26,7 @@ <h2>DESCRIPTION</h2>
 their <em>current mapset</em>. Although the user can
 also <em>access</em> (i.e., use) data that are stored under
 <em>other</em> mapsets in the same GRASS project using the
-<tt>mapname@mapsetname</tt> notation or mapset search path, the user
+<code>mapname@mapsetname</code> notation or mapset search path, the user
 can only make permanent changes (create or modify data)
 located in the <em>current mapset</em>.  The user's
 <em>mapset search path</em> lists the order in which other mapsets in
@@ -36,7 +36,7 @@ <h2>DESCRIPTION</h2>
 using the <em>g.mapsets</em> command. This program allows the user to
 use other's relevant map data without altering the original data
 layer, and without taking up disk space with a copy of the original
-map. The <tt>mapname@mapsetname</tt> notation may be used irrespective
+map. The <code>mapname@mapsetname</code> notation may be used irrespective
 of the mapset search path, i.e., any map found in another mapset with
 sufficient <em><a href="g.access.html">g.access</a></em> privileges
 may be called in such a manner.
@@ -63,8 +63,8 @@ <h2>DESCRIPTION</h2>
 g.copy raster=soils@PERMANENT,my_soils
 </pre></div>
 
-ensures that a new file named <tt>my_soils</tt> is to be a copy of
-the file <tt>soils</tt> from the mapset PERMANENT.
+ensures that a new file named <code>my_soils</code> is to be a copy of
+the file <code>soils</code> from the mapset PERMANENT.
 
 <p>
 In each project there is the special mapset <b>PERMANENT</b> included