v.in.ogr: update manual (cnames->columns) (merge https://trac.osgeo.org/grass/changeset/71428 from trunk)

git-svn-id: https://svn.osgeo.org/grass/grass/branches/releasebranch_7_0@71430 15284696-431f-4ddb-bdfa-cd5b030d7da7

vector/v.in.ogr/v.in.ogr.html

@@ -118,7 +118,7 @@ character, not a number.
 import. The <b>-w</b> flag changes capital column names to
 lowercase characters as a convenience for SQL usage (lowercase column
 names avoid the need to quote them if the attribute table is stored in
-a SQL DBMS such as PostgreSQL). The <b>cnames</b> parameter is used
+a SQL DBMS such as PostgreSQL). The <b>columns</b> parameter is used
 to define new column names during import.
 
 <p>
@@ -128,7 +128,7 @@ column/field names, they will be truncated. If this results in
 multiple columns with the same name then <em>v.in.ogr</em> will
 produce an error.  In this case you will either have to modify the
 input data or use
-<em>v.in.ogr</em>'s <b>cnames</b> parameter to rename columns to something
+<em>v.in.ogr</em>'s <b>columns</b> parameter to rename columns to something
 unique. (hint: copy and modify the list given with the error message).
 Alternatively, change the local DB with
 <em><a href="db.connect.html">db.connect</a></em>.
@@ -336,7 +336,7 @@ contains topological errors. The message suggests a value for the
 <dt>DBMI-DBF driver error: SQL parser error: syntax error,
 unexpected DESC, expecting NAME processing 'DESC'</dt>
 <dd>indicates that a column name corresponds to a reserved SQL word (here: 'DESC').
-A different column name should be used. The <b>cnames</b> parameter can be used
+A different column name should be used. The <b>columns</b> parameter can be used
 to assign different column names on the fly.</dd>
 <dt>Projection of dataset does not appear to match the current location.</dt>
 <dd>You need to create a location whose projection matches the data