From: Bborie Park <bkpark at ucdavis.edu>
Date: Thu, 31 May 2012 05:45:52 +0000 (+0000)
Subject: Correct spelling mistakes
X-Git-Tag: 2.1.0beta2~956
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c6f8df34297273229074d1196da546d65174ccea;p=postgis

Correct spelling mistakes

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

diff --git a/doc/using_raster_dataman.xml b/doc/using_raster_dataman.xml
index e2aae2bfd..9ade99035 100644
--- a/doc/using_raster_dataman.xml
+++ b/doc/using_raster_dataman.xml
@@ -387,7 +387,7 @@ Available GDAL raster formats:
     		<listitem><para>Once you are done populating your table initially, you'll want to create a spatial index on the raster column with something like:</para>
     			<programlisting>CREATE INDEX myrasters_rast_st_convexhull_idx ON myrasters USING gist( ST_ConvexHull(rast) );</programlisting>
     			<para>Note the use of <xref linkend="RT_ST_ConvexHull" /> since most raster operators are based on the convex hull of the rasters.</para>
-    			<note><para>Pre-2.0 versions of PostGIS raster were based on the envelop rather than the convex hull.  For teh spatial idnexes to work properly you'll need to drop those and replace with convex hull based index.</para></note></listitem>
+    			<note><para>Pre-2.0 versions of PostGIS raster were based on the envelop rather than the convex hull.  For the spatial indexes to work properly you'll need to drop those and replace with convex hull based index.</para></note></listitem>
     		<listitem><para>Apply raster constraints using <xref linkend="RT_AddRasterConstraints" /></para></listitem>
     	</orderedlist>
     </sect2>