[GRASS-SVN] r73696 - in grass/trunk: ps/ps.map vector/v.db.connect

[svn_grass at osgeo.org]

Author: neteler
Date: 2018-11-21 22:43:26 -0800 (Wed, 21 Nov 2018)
New Revision: 73696

Modified:
   grass/trunk/ps/ps.map/ps.map.html
   grass/trunk/vector/v.db.connect/v.db.connect.html
Log:
v.db.connect and ps.map manuals: fix typos; DPI cosmetics

Modified: grass/trunk/ps/ps.map/ps.map.html
===================================================================
--- grass/trunk/ps/ps.map/ps.map.html	2018-11-22 06:39:40 UTC (rev 73695)
+++ grass/trunk/ps/ps.map/ps.map.html	2018-11-22 06:43:26 UTC (rev 73696)
@@ -10,7 +10,7 @@
 
 <h2>NOTES</h2> 
 
-<p>The order of commands is generally unimportant but may affect how some layers
+The order of commands is generally unimportant but may affect how some layers
 are drawn. For example to plot <b>vpoints</b> above <b>vareas</b> list the
 <b>vpoints</b> entry first. Raster maps are always drawn first, and only a
 single raster map (or 3 if part of a RGB group) may be used.
@@ -27,9 +27,9 @@
 <a href="g.region.html">g.region</a> module. The output filesize is largely
 a function of the region resolution, so special care should be taken
 if working with large raster datasets. For example if the desired output is
-US-Letter sized paper at 300dpi, with 1" margins and the raster filling the
-entire page, the usable area on the page will be 6.5" x 9", which at 300
-dots/inch is equivalent to a region of 1950 columns x 2700 rows (see 
+US-Letter sized paper at 600dpi, with 1" margins and the raster filling the
+entire page, the usable area on the page will be 6.5" x 9", which at 600
+dots/inch is equivalent to a region of 3900 columns x 5400 rows (see 
 "<tt>g.region -p</tt>"). Any higher resolution settings will make the
 output file larger, but with a consumer printer you probably won't be able
 to resolve any better detail in the hardcopy.

Modified: grass/trunk/vector/v.db.connect/v.db.connect.html
===================================================================
--- grass/trunk/vector/v.db.connect/v.db.connect.html	2018-11-22 06:39:40 UTC (rev 73695)
+++ grass/trunk/vector/v.db.connect/v.db.connect.html	2018-11-22 06:43:26 UTC (rev 73696)
@@ -116,8 +116,8 @@
 
 <h3>Store geometry in GRASS but attributes in PostgreSQL</h3>
 
-This example illustrated a mixed data storage with possibility
-top update attributes in external PostgreSQL database:
+This example illustrates a mixed data storage with possibility to
+update attributes in an external PostgreSQL database:
 
 <div class="code"><pre>
 # Check current settings for attribute storage: