Fix spelling errors (https://trac.osgeo.org/grass/ticket/872)

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@40454 15284696-431f-4ddb-bdfa-cd5b030d7da7

display/d.nviz/d.nviz.html

@@ -75,7 +75,7 @@ animation in sections. For example the user may wish to start at frame
 number 2000.
 
 <DT><B>route</B>
-<DD>The comma seperated geographic coordinates for keyframe locations.
+<DD>The comma separated geographic coordinates for keyframe locations.
 <DD>The interactive flag (<EM>-i</EM>) overrides this option.
 
 </DL>
@@ -102,7 +102,7 @@ The user must select at least four key-frame locations (points)
 <p>
 If the GRASS region is changed the <EM>d.nviz</EM> command must be re-run.
 <p>
-The current GRASS region and the user supplied paramters are included
+The current GRASS region and the user supplied parameters are included
 as a comment at the top of the output script. This information can be
 used to easily re-create the animation.
 <p>

lib/htmldriver/htmldriver.html

@@ -92,7 +92,7 @@ of HTMLMAP.
   </LI>
   <LI><B>GRASS_HTMLMAXPOINTS=n</B><BR>specifies the maximum number of
   vertices included in a polygon's clickable area.
-  The default is <tt>99</tt>.  Some browsers can only accomodate polygons of
+  The default is <tt>99</tt>.  Some browsers can only accommodate polygons of
   100 vertices or less.  The HTMLMAP driver automatically ensures that a
   polygon is closed by making the last point the same as the first
   point.</LI>

lib/init/variables.html

@@ -435,7 +435,7 @@ detailed list of the variables.
     This variable is automatically created
     by <em><a href="g.parser.html">g.parser</a></em> so that the
     <tt>--overwrite</tt> option will
-    be inherited by dependant modules as the script runs. Setting either the
+    be inherited by dependent modules as the script runs. Setting either the
     GRASS_OVERWRITE environment variable or the OVERWRITE gisenv variable detailed
     below will cause maps with identical names to be overwritten.</dd>
   
@@ -450,7 +450,7 @@ detailed list of the variables.
     </ul>
     This variable is automatically created by <em><a href="g.parser.html">g.parser</a></em>
     so that the <tt>--verbose</tt> or <tt>--quiet</tt> flags will be inherited
-    by dependant modules as the script runs.</dd>
+    by dependent modules as the script runs.</dd>
   
   <dt>GRASS_REGION</dt>
   <dd>[libgis]<br>
@@ -523,7 +523,7 @@ detailed list of the variables.
     This variable is automatically created
     by <em><a href="g.parser.html">g.parser</a></em> so that the
     <tt>--overwrite</tt> option will
-    be inherited by dependant modules as the script runs. Setting either the
+    be inherited by dependent modules as the script runs. Setting either the
     GRASS_OVERWRITE environment variable or the OVERWRITE gisenv variable detailed
     below will cause maps with identical names to be overwritten.</dd>
 </dl>

raster/r.in.gdal/r.in.gdal.html

@@ -117,7 +117,7 @@ Planned improvements to <em>r.in.gdal</em> in the future include support for
 reporting everything known about a dataset if the <b>output</b> parameter is not set.
 
 <p>
-The <em>r.in.gdal</em> comand does support the following features, as long as 
+The <em>r.in.gdal</em> command does support the following features, as long as 
 the underlying format driver supports it:
 
 <p>

raster/r.out.vtk/r.out.vtk.html

@@ -44,9 +44,9 @@ You can visualize this file with the
 <em><a href="http://mayavi.sourceforge.net">MayaVi</a></em> which are based on VTK.
 If you have a raster map with partly no data, use the threshold filter in paraview to 
 visualize the valid data. Just filter all data which is greater/lesser than the 
-choosen null value in the VTK-ASCII file.
+chosen null value in the VTK-ASCII file.
 <br>
-If elevation map is choosen, a polygonal grid is created with <i>quads</i>, 
+If elevation map is chosen, a polygonal grid is created with <i>quads</i>, 
 but the user can choose also <i>triangle strips</i> or <i>vertices</i>. 
 These dataformats a documented at <em><a href="http://www.vtk.org">VTK Toolkit</a></em>.
 <br>

raster/r.profile/r.profile.html

@@ -87,7 +87,7 @@ cat saved.points | r.profile input=elev.rast output=profile.pts
 The advantage of this method is that the same profile points can be piped into
 different GRASS rasters by changing the input parameter. 
 <p>
-With this method the coordinates must be given as space or tab seperated easting
+With this method the coordinates must be given as space or tab separated easting
 and northing. Labels after these values are ignored.
 <p>
 Another example using d.where:

raster/r.sun/r.sun.html

@@ -52,7 +52,7 @@ steepness raster map <i>slopin,</i> given the day <i>day</i> and local time
 and defined projection/coordinate system (check it with the <a href="g.proj.html">
 g.proj</a>
  command). If you have undefined projection, (x,y) system, etc. then the latitude
-can be defined explicitely for large areas by input raster map <i>latin</i>
+can be defined explicitly for large areas by input raster map <i>latin</i>
  with interpolated latitude values. All input raster maps must
 be floating point (FCELL) raster maps. Null data in maps are excluded from
 the computation (and also speeding-up the computation), so each output raster

raster3d/r3.out.vtk/r3.out.vtk.html

@@ -20,7 +20,7 @@ to be written in the VTK-ASCII file. Each <I>celldata</I> is named as the
 <EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM> which are based on VTK.
 If you have a 3D raster map with partly no data, use the threshold filter in paraview to 
 visualize the valid data. Just filter all data which is greater/lesser than the 
-choosen null value in the VTK-ASCII file.
+chosen null value in the VTK-ASCII file.
 
 <BR><BR>
 The top and bottom region settings are expected in meters. 

scripts/r.tileset/r.tileset.html

@@ -26,7 +26,7 @@ constraints on cell aspect ratio.
 
 <h2>OUTPUT FORMAT</h2>
 
-Each tile is listed on a seperate line in the output. The lines are
+Each tile is listed on a separate line in the output. The lines are
 formatted as follows:
 
 <dl>
@@ -37,8 +37,8 @@ formatted as follows:
 
 <dd>This is the default output format. It is the tile's minimum x
 coordinate, minimum y coordinate, maximum x coordinate, maximum y
-coordinate, width in cells, and height in cells seperated by the "|"
-character. The fields can be seperated by a different character by
+coordinate, width in cells, and height in cells separated by the "|"
+character. The fields can be separated by a different character by
 changing the fs option.
 
 <dt>
@@ -68,7 +68,7 @@ r.tileset sourceproj=+init=epsg:4326 maxrows=1024 maxcols=2048
 
 <dd>Generates tiles in latitude longitude that cover the current
 region, each tile will be less than 1024 cells high and 2048 cells
-across. The bounds and sizes of tiles in the output are seperated by |
+across. The bounds and sizes of tiles in the output are separated by |
 
 <dt>
 <span class="code"><tt>

vector/v.surf.idw/v.surf.idw.html

@@ -48,7 +48,7 @@ achieve a similar result.</p>
 <p>
 If more than <EM>count</EM> points fall into one target raster cell, 
 the mean of all the site values will determine the cell value (unless
-the -n flag is specifed, in which case only the <EM>count</EM> 
+the -n flag is specified, in which case only the <EM>count</EM> 
 points closest to the centre of the cell will be interpolated).</p>
 
 <P>

vector/v.to.points/v.to.points.html

@@ -36,7 +36,7 @@ along the boundary perimeter according to <em>dmax</em>. If two
 adjoining polygons share a topological boundary, the boundary only
 gets converted to points once.</li>
 <li>
-If the <em>type</em> paramter is set to <em>area</em>, the boundary of
+If the <em>type</em> parameter is set to <em>area</em>, the boundary of
 each area is converted to points <i>regardless</i> of whether or not
 there is a topological boundary between adjacent areas. In other
 words, the common boundary of two adjoining areas, for example, gets