rename section BUGS to KNOWN ISSUES in manuals

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

raster/r.carve/r.carve.html

@@ -25,7 +25,7 @@ g.region raster=elevation -p
 r.carve rast=elevation vect=streams out=carve_dem width=20 depth=5
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 <!-- Is this still the case as of Jan 11, 2008? - EP -->
 The module does not operate yet in latitude-longitude locations.  It
 has not been thoroughly tested, so not all options may work properly -

raster/r.drain/r.drain.html

@@ -183,7 +183,7 @@ The directions are recorded as degrees CCW from East:
 </pre></div>
 
 <p>
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 <p>Sometimes, when the differences among integer cell category values in the
 <em><a href="r.cost.html">r.cost</a></em> cumulative cost surface output are 

raster/r.in.lidar/r.in.lidar.html

@@ -257,7 +257,7 @@ needed to test for matching projections.
      <!-- Bob Covill has supplied patches for MBIO interface already -->
 </ul>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 <ul>
 <li> <em>n</em> map <tt>percent=100</tt> and <tt>percent=xx</tt> maps

raster/r.in.mat/r.in.mat.html

@@ -108,7 +108,7 @@ if they exist.
 Option to import a version 5 MAT-File, with map and support information 
 stored in a single structured array.
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 If you encounter any problems, please contact the GRASS Development Team.
 

raster/r.in.xyz/r.in.xyz.html

@@ -257,7 +257,7 @@ r.colors lidar_min.rst_scaled rule=bcyr -n -e
 </ul>
 
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 <ul>
 <li> <em>n</em> map sum can be ever-so-slightly more than `<tt>wc -l</tt>`

raster/r.mapcalc/r3.mapcalc.html

@@ -540,7 +540,7 @@ X (map) values supplied and y (newmap) values returned:
 </pre></div>
 
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 Continuation lines must end with a \ and have NO trailing white space
 (blanks or tabs).  If the user does leave white space at the end of
 continuation lines, the error messages produced by <em>r3.mapcalc</em> will

raster/r.out.mpeg/r.out.mpeg.html

@@ -57,7 +57,7 @@ view.  Use of this option also overrides any size defaults, using
 the <b>CURRENTLY DEFINED GRASS REGION for the output size</b>. So be
 careful to set region to a reasonable size prior to encoding.
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 MPEG images must be 16-pixel aligned for successful compression, so if
 the rows &amp; columns of the calculated image size (scaled, with

raster/r.random/r.random.html

@@ -95,7 +95,7 @@ cat|value|covervalue
 ...
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 It's not possible to use the <b>-i</b> flag and not also specify the <b>n</b> 
 parameter.

raster/r.surf.idw/r.surf.idw.html

@@ -78,7 +78,7 @@ the input raster map to analyze the distribution of interpolation error.
 This procedure may be helpful in choosing the number of nearest neighbors
 considered for surface generation.
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 Module <em>r.surf.idw</em> works only for integer (CELL) raster maps.
 
 <h2>SEE ALSO</h2>

raster/r.texture/r.texture.html

@@ -118,7 +118,7 @@ d.shade color=ortho_texture_ASM_0 shade=ortho_2001_t792_1m
 This calculates four maps (requested texture at four orientations):
 ortho_texture_ASM_0, ortho_texture_ASM_45, ortho_texture_ASM_90, ortho_texture_ASM_135.
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 The program can run incredibly slow for large raster maps.
 
 <h2>REFERENCES</h2>

raster/r.timestamp/r.timestamp.html

@@ -118,7 +118,7 @@ Removes the timestamp for the "soils" raster map.
     r.timestamp map=soils date=none
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 Spaces in the timestamp value are required.
 
 <h2>SEE ALSO</h2>

raster/r.to.vect/r.to.vect.html

@@ -102,7 +102,7 @@ r.to.vect -s input=landclass96 output=my_landclass96 type=area
 v.colors my_landclass96 color=random
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 For type=line the input raster map MUST be thinned by
 <em><a href="r.thin.html">r.thin</a></em>;

raster3d/r3.timestamp/r3.timestamp.html

@@ -82,7 +82,7 @@ date(s). See EXAMPLES below.
 	     3 years 10 days
 </tt>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 Spaces in the timestamp value are required.
 
 <h2>AUTHOR</h2>

scripts/r.tileset/r.tileset.html

@@ -87,7 +87,7 @@ work in a unix style shell:
 r.tileset sourceproj="`g.proj -j location=IrishGrid`" maxrows=400 maxcols=300 overlap=3 -g
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 <ul>
 <li><em>r.tileset</em> does not know about meridians that

scripts/r3.in.xyz/r3.in.xyz.html

@@ -66,7 +66,7 @@ into voxels in instead of the z-value:
 </pre></div>
 
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 <em>r.to.rast3</em> always creates a <tt>double</tt> output map
 regardless of input.

vector/v.net.visibility/v.net.visibility.html

@@ -122,7 +122,7 @@ d.vect graph
 d.vect archsites col=red
 </pre></div>
 
-<h2>KNOWN BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 In some cases when 3 points or nodes are collinear, some wrong edges 
 are added. This happens only really rarly and shouldn't be a big 
 problem. When two points have the exact same x coordinate and are 

vector/v.parallel/v.parallel.html

@@ -6,7 +6,7 @@ can be used as half-buffers.
 <h2>NOTES</h2>
 Usage of <b>-b</b> flag will overrule the <b>side</b> parameter.
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 There is a problem with side-offset parallel line generation for inside corners.
 To avoid this problem, the <b>-b</b> flag might be used.
 <!-- in Vect_line_parallel(), v.segment is also affected -->

vector/v.qcount/v.qcount.html

@@ -61,7 +61,7 @@ bacterial populations.
 Biology</em>, 2:215-235, 1959.</li>
 </ul>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 Timestamp not working for header part of counts output. (2000-10-28)
 

vector/v.reclass/v.reclass.html

@@ -76,7 +76,7 @@ cat|I_vs_P
 </pre></div>
 
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 No table is created for reclassed layer if <b>rules</b> option is used.
 

vector/v.segment/v.segment.html

@@ -158,7 +158,7 @@ A series of points, spaced every 10% of the line's length along the
 tracks from the end of the line up to the middle point, offset 500m to the right
 </center>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 There is a problem with side-offset parallel line generation for inside corners.
 <!-- in Vect_line_parallel(), v.parallel is also affected -->
 

vector/v.surf.bspline/v.surf.bspline.html

@@ -143,7 +143,7 @@ v.surf.bspline input=elev_lid792_bepts raster=elev_lid792_rast \
 </pre></div>
 
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 
 Known issues:
 

vector/v.timestamp/v.timestamp.html

@@ -118,7 +118,7 @@ Removes the timestamp for the "lidar" vector map.
     v.timestamp map=lidar date=none
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 Spaces in the timestamp value are required.
 
 <h2>SEE ALSO</h2>

vector/v.vol.rst/v.vol.rst.html

@@ -222,7 +222,7 @@ r3.out.vtk -s input=soilrange top=elevation.10m bottom=bottom dp=2 output=volume
 paraview --data=volume.vtk
 </pre></div>
 
-<h2>BUGS</h2>
+<h2>KNOWN ISSUES</h2>
 <b>deviations</b> file is written as 2D and deviations are not written as attributes.
 
 <h2>REFERENCES</h2>