geomentry -> geometry

Thanks Andreas Schild via
https://www.transifex.com/postgis/postgis/translate/#de/using_postgis_datamanxmlpot/19191543/

git-svn-id: http://svn.osgeo.org/postgis/trunk@15427 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml
index fc73d61c0cab823b992e91a283245c0da6afc44e..bebdd7e745a0e4a99710a9b84ee467c56e997212 100644 (file)
--- a/doc/using_postgis_dataman.xml
+++ b/doc/using_postgis_dataman.xml
@@ -805,7 +805,7 @@ SELECT populate_geometry_columns('myschema.my_special_pois'::regclass);
 -- set new optional  use_typmod argument to false
 SELECT populate_geometry_columns('myschema.my_special_pois'::regclass, false); </programlisting>
 
-<para>Although the old-constraint based method is still supported, a constraint-based geomentry column used directly
+<para>Although the old-constraint based method is still supported, a constraint-based geometry column used directly
 in a view, will not register correctly in geometry_columns, as will a typmod one.
 In this example we define a column using typmod and another using constraints.</para>
 <programlisting>CREATE TABLE pois_ny(gid SERIAL PRIMARY KEY