fix typos in docs

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

diff --git a/doc/introduction.xml b/doc/introduction.xml
index 5c5f6455b3e127018b2b5a5eb23c08bd17733d41..39b639da05875fd376f51cf7b6929c3533616def 100644 (file)
--- a/doc/introduction.xml
+++ b/doc/introduction.xml
@@ -251,6 +251,7 @@ Avencia,
 Azavea,
 Cadcorp,
 CampToCamp,
+CartoDB,
 City of Boston (DND),
 Clever Elephant Solutions,
 Cooperativa Alveo,
@@ -278,7 +279,6 @@ Stadt Uster,
 UC Davis Center for Vectorborne Diseases,
 University of Laval,
 U.S Department of State (HIU),
-CartoDB,
 Zonar Systems</para>
                </listitem>
          </varlistentry>

diff --git a/doc/reference_constructor.xml b/doc/reference_constructor.xml
index 5f113c1b79dde3d3ff4d94aa1c5a80db67d2400d..b9225c4805e712ba8df2fba3fe2169d18551a315 100644 (file)
--- a/doc/reference_constructor.xml
+++ b/doc/reference_constructor.xml
@@ -575,7 +575,7 @@ SELECT ST_GeomFromEWKT('POLYHEDRALSURFACE(
 
                <para>Return a geometry from a GeoHash string. The geometry will be a polygon representing the GeoHash bounds.</para>
 
-               <para>If no <varname>precision</varname> is specficified ST_GeomFromGeoHash returns a polygon based on full precision of the input GeoHash string.</para>
+               <para>If no <varname>precision</varname> is specified ST_GeomFromGeoHash returns a polygon based on full precision of the input GeoHash string.</para>
 
                <para>If <varname>precision</varname> is specified ST_GeomFromGeoHash will use that many characters from the GeoHash to create the polygon.</para>
 
@@ -2121,7 +2121,7 @@ SELECT ST_Transform(ST_SetSRID(ST_Point(3637510, 3014852),2273),4326)::geography
 
                <para>Return a point from a GeoHash string. The point represents the center point of the GeoHash.</para>
 
-               <para>If no <varname>precision</varname> is specficified ST_PointFromGeoHash returns a point based on full precision of the input GeoHash string.</para>
+               <para>If no <varname>precision</varname> is specified ST_PointFromGeoHash returns a point based on full precision of the input GeoHash string.</para>
 
                <para>If <varname>precision</varname> is specified ST_PointFromGeoHash will use that many characters from the GeoHash to create the point.</para>
 

diff --git a/doc/reference_editor.xml b/doc/reference_editor.xml
index c00060e44e37273213c79345eee1630751b290a9..6af835b8f223c82c3b3b09d8fdbf16804807ef9a 100644 (file)
--- a/doc/reference_editor.xml
+++ b/doc/reference_editor.xml
@@ -1280,7 +1280,7 @@ FROM (SELECT ST_LineToCurve(ST_Buffer(ST_GeomFromText('POINT(234 567)'), 3)) As
 The version taking a geometry as the <varname>factor</varname> parameter
 allows passing a 2d, 3dm, 3dz or 4d point to set scaling factor for all
 supported dimensions. Missing dimensions in the <varname>factor</varname>
-point are equivalant to no scaling the corresponding dimension.
+point are equivalent to no scaling the corresponding dimension.
     </para>
 
                <note><para>Prior to 1.3.4, this function crashes if used with geometries that contain CURVES.  This is fixed in 1.3.4+</para></note>

diff --git a/doc/reference_measure.xml b/doc/reference_measure.xml
index f3232538d4a9a70af426727c43c41aa8db7e5f52..94c299453a358f8fa49a2f3b4ac6ebeef5f4f482 100644 (file)
--- a/doc/reference_measure.xml
+++ b/doc/reference_measure.xml
@@ -1530,7 +1530,7 @@ FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 2)'), 10) As smallc,
          returns <varname>TRUE</varname> if their intersection "spatially cross", that is, the
          geometries have some, but not all interior points in common. The
          intersection of the interiors of the geometries must not be the empty
-         set and must have a dimensionality less than the the maximum dimension
+         set and must have a dimensionality less than the maximum dimension
          of the two input geometries. Additionally, the intersection of the two
          geometries must not equal either of the source geometries. Otherwise, it
          returns <varname>FALSE</varname>.</para>

diff --git a/doc/reference_output.xml b/doc/reference_output.xml
index 96b116a2c0015f344f6987e7a3ab7107690f36f5..c477a2e4ddefa56884a711a944be62c80a85caa4 100644 (file)
--- a/doc/reference_output.xml
+++ b/doc/reference_output.xml
@@ -798,7 +798,7 @@ SELECT ST_AsGML(3, ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0
             </listitem>
         
             <listitem>
-              <para>2: Output coordinates in GeoSpatial GeoCoordinates.  This option will throw an error if geometries are not in WGS 84 long lat (srid: 4326). This is currenlty the only GeoCoordinate type supported.  <ulink url="http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference">Refer to X3D specs specifying a spatial reference system.</ulink>. Default output will be <code>GeoCoordinate geoSystem='"GD" "WE" "longitude_first"'</code>.  If
+              <para>2: Output coordinates in GeoSpatial GeoCoordinates.  This option will throw an error if geometries are not in WGS 84 long lat (srid: 4326). This is currently the only GeoCoordinate type supported.  <ulink url="http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference">Refer to X3D specs specifying a spatial reference system.</ulink>. Default output will be <code>GeoCoordinate geoSystem='"GD" "WE" "longitude_first"'</code>.  If
               you prefer the X3D default of  <code>GeoCoordinate geoSystem='"GD" "WE" "latitude_first"'</code> use <code>(2 + 1)</code> = <code>3</code> </para>
             </listitem>
         </itemizedlist>
@@ -973,7 +973,7 @@ x3dfrag
 
                <para>Return a GeoHash representation (<ulink url="http://en.wikipedia.org/wiki/Geohash">http://en.wikipedia.org/wiki/Geohash</ulink>) of the geometry. A GeoHash encodes a point into a text form that is sortable and searchable based on prefixing.  A shorter GeoHash is a less precise representation of a point.  It can also be thought of as a box, that contains the actual point.</para>
 
-               <para>If no <varname>maxchars</varname> is specficified ST_GeoHash returns a GeoHash based on full precision of the input geometry type. Points return a GeoHash with 20 characters of precision (about enough to hold the full double precision of the input). Other types return a GeoHash with a variable amount of precision, based on the size of the feature. Larger features are represented with less precision, smaller features with more precision. The idea is that the box implied by the GeoHash will always contain the input feature.</para>
+               <para>If no <varname>maxchars</varname> is specified ST_GeoHash returns a GeoHash based on full precision of the input geometry type. Points return a GeoHash with 20 characters of precision (about enough to hold the full double precision of the input). Other types return a GeoHash with a variable amount of precision, based on the size of the feature. Larger features are represented with less precision, smaller features with more precision. The idea is that the box implied by the GeoHash will always contain the input feature.</para>
 
                <para>If <varname>maxchars</varname> is specified ST_GeoHash returns a GeoHash with at most that many characters so a possibly lower precision representation of the input geometry. For non-points, the starting point of the calculation is the center of the bounding box of the geometry.</para>
 

diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml
index d4ff50dc795124430e3ffee99ef9ab8df2a6d79a..8c61c74ce2ecb25f78cabd7a11579daf882febd3 100644 (file)
--- a/doc/reference_raster.xml
+++ b/doc/reference_raster.xml
@@ -2083,7 +2083,7 @@ FROM (SELECT rid, ST_MetaData(rast) As md
                                </para>
 
                                <para>
-                                       If <varname>padwithnodata</varname> = FALSE, edge tiles on the right and bottom sides of the raster may have different dimensions than the rest of the tiles. If <varname>padwithnodata</varname> = TRUE, all tiles will have the same dimensions with the possibilty that edge tiles being padded with NODATA values.  If raster band(s) do not have NODATA value(s) specified, one can be specified by setting <varname>nodataval</varname>.
+                                       If <varname>padwithnodata</varname> = FALSE, edge tiles on the right and bottom sides of the raster may have different dimensions than the rest of the tiles. If <varname>padwithnodata</varname> = TRUE, all tiles will have the same dimensions with the possibility that edge tiles being padded with NODATA values.  If raster band(s) do not have NODATA value(s) specified, one can be specified by setting <varname>nodataval</varname>.
                                </para>
 
                                <note>
@@ -2267,7 +2267,7 @@ raster coverage (<varname>tab</varname>, <varname>col</varname>).
                                </para>
 
                                <para>
-                                       If <varname>srid</varname> is NULL, the function will try to autmatically assign the SRID from the GDAL raster. If <varname>srid</varname> is provided, the value provided will override any automatically assigned SRID.
+                                       If <varname>srid</varname> is NULL, the function will try to automatically assign the SRID from the GDAL raster. If <varname>srid</varname> is provided, the value provided will override any automatically assigned SRID.
                                </para>
 
                                <para>Availability: 2.1.0</para>