Spelling errors and consistent verbiage

doc/faq.xml

@@ -431,7 +431,7 @@ WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);</programlisting>
         Inevitably, small inaccuracies occur, which cause results of different operations to be slightly inconsistent.
             </para>
 
-        <para>Furthermore, PostGIS operations contain error-prevention code which may peturb
+        <para>Furthermore, PostGIS operations contain error-prevention code which may perturb
         input geometries by tiny amounts in order to prevent robustness errors from occurring.
         These minor alterations also may produce computed results which are not fully consistent.
             </para>

doc/installation.xml

@@ -9,7 +9,7 @@
   <sect1 id="install_short_version">
 	<title>Short Version</title>
 	<para>To compile assuming you have all the dependencies in your search path:</para>
-	<programlisting>tar xvfz postgis-&last_release_version;.tar.gz
+	<programlisting>tar -xvfz postgis-&last_release_version;.tar.gz
 cd postgis-&last_release_version;
 ./configure
 make
@@ -1796,7 +1796,7 @@ If present the <xref linkend="Geocode" /> function can use it if a boundary filt
 The <xref linkend="Reverse_Geocode" /> function uses it if the returned address is missing a zip, which often happens with highway reverse geocoding.</para></listitem>
 			<listitem><para>Create a folder called <filename>gisdata</filename> on root of server or your local pc if you have a fast network connection to the server. This folder is
 where the tiger files will be downloaded to and processed.  If you are not happy with having the folder on the root of the server, or simply want to change to a different folder for staging, then edit the field <varname>staging_fold</varname> in the <varname>tiger.loader_variables</varname> table.</para></listitem>
-            <listitem><para>Create a folder called temp in the <filename>gisdata</filename> folder or whereever you designated the <varname>staging_fold</varname> to be.  This will be
+            <listitem><para>Create a folder called temp in the <filename>gisdata</filename> folder or wherever you designated the <varname>staging_fold</varname> to be.  This will be
 the folder where the loader extracts the downloaded tiger data.</para></listitem>
 			<listitem><para>Then run the  <xref linkend="Loader_Generate_Nation_Script" />  SQL function make sure to use the name of your custom profile and copy the script to a .sh or .bat file.  So for example to build  the nation load:</para>
 					<programlisting>psql -c "SELECT Loader_Generate_Nation_Script('debbie')" -d geocoder -tA > /gisdata/nation_script_load.sh</programlisting>

doc/performance_tips.xml

@@ -34,7 +34,7 @@
 
       <para>To see whether your suffer from this issue, use the "EXPLAIN
       ANALYZE" postgresql command. For more information and the technical
-      details, you can read the thread on the postgres performance mailing
+      details, you can read the thread on the PostgreSQL performance mailing
       list:
       <ulink url="http://archives.postgresql.org/pgsql-performance/2005-02/msg00030.php">http://archives.postgresql.org/pgsql-performance/2005-02/msg00030.php</ulink></para>
 

doc/reference_accessor.xml

@@ -1986,7 +1986,7 @@ FROM (SELECT 'LINESTRING(0 0, 0 1, 1 0, 1 1, 0 0)'::geometry AS geom) AS foo;
 		<title>Description</title>
 
 		<para>Returns true if this Geometry has no anomalous geometric
-				points, such as self intersection or self tangency. For more
+				points, such as self-intersection or self-tangency. For more
 			information on the OGC's definition of geometry simplicity and validity, refer
 			to <link linkend="OGC_Validity">"Ensuring OpenGIS compliancy of geometries"</link></para>
 
@@ -2470,8 +2470,8 @@ GROUP BY gid, field1,field2;
 		<title>Description</title>
 
 		<para>Return the number of points in an ST_LineString or
-		  ST_CircularString value. Prior to 1.4 only works with Linestrings as the specs state.  From 1.4 forward this is an alias for ST_NPoints which returns number of vertexes for
-		  not just line strings.
+		  ST_CircularString value. Prior to 1.4 only works with linestrings as the specs state.  From 1.4 forward this is an alias for ST_NPoints which returns number of vertexes for
+		  not just linestrings.
 		  Consider using ST_NPoints instead which is multi-purpose
 		  and works with many geometry types.</para>
 

doc/reference_bbox.xml

@@ -343,7 +343,7 @@ SELECT ST_Expand(CAST('BOX3D(778783 2951741 1,794875 2970042.61545891 10)' As bo
 		<para>ST_Extent is similar in concept to Oracle Spatial/Locator's SDO_AGGR_MBR</para>
 		<note>
 		  <para>Since ST_Extent returns a bounding box, the SRID meta-data is lost.  Use ST_SetSRID to force it back into
-			a geometry with SRID meta data.  The coordinates are in the units of the spatial ref of the orginal geometries.</para>
+			a geometry with SRID meta data.  The coordinates are in the units of the spatial ref of the original geometries.</para>
 		</note>
 
 		<note>
@@ -424,7 +424,7 @@ SELECT ST_SetSRID(ST_Extent(geom),2249) as bextent FROM sometable;
 
 		<note>
 		  <para>Since ST_3DExtent returns a bounding box, the SRID meta-data is lost.  Use ST_SetSRID to force it back into
-			a geometry with SRID meta data.  The coordinates are in the units of the spatial ref of the orginal geometries.</para>
+			a geometry with SRID meta data.  The coordinates are in the units of the spatial ref of the original geometries.</para>
 		</note>
 
 		<para>Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced.</para>
@@ -612,7 +612,7 @@ SELECT ST_XMax(CAST('BOX(-3 2, 3 4)' As box2d));
 st_xmax
 -------
 3
---Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D
+--Observe THIS DOES NOT WORK because it will try to auto-cast the string representation to a BOX3D
 SELECT ST_XMax('LINESTRING(1 3, 5 6)');
 
 --ERROR:  BOX3D parser - doesn't start with BOX3D(
@@ -680,7 +680,7 @@ SELECT ST_XMin(CAST('BOX(-3 2, 3 4)' As box2d));
 st_xmin
 -------
 -3
---Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D
+--Observe THIS DOES NOT WORK because it will try to auto-cast the string representation to a BOX3D
 SELECT ST_XMin('LINESTRING(1 3, 5 6)');
 
 --ERROR:  BOX3D parser - doesn't start with BOX3D(
@@ -748,7 +748,7 @@ SELECT ST_YMax(CAST('BOX(-3 2, 3 4)' As box2d));
 st_ymax
 -------
 4
---Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D
+--Observe THIS DOES NOT WORK because it will try to auto-cast the string representation to a BOX3D
 SELECT ST_YMax('LINESTRING(1 3, 5 6)');
 
 --ERROR:  BOX3D parser - doesn't start with BOX3D(
@@ -816,7 +816,7 @@ SELECT ST_YMin(CAST('BOX(-3 2, 3 4)' As box2d));
 st_ymin
 -------
 2
---Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D
+--Observe THIS DOES NOT WORK because it will try to auto-cast the string representation to a BOX3D
 SELECT ST_YMin('LINESTRING(1 3, 5 6)');
 
 --ERROR:  BOX3D parser - doesn't start with BOX3D(
@@ -884,7 +884,7 @@ SELECT ST_ZMax('BOX3D(-3 2 1, 3 4 1)' );
 st_zmax
 -------
 1
---Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D
+--Observe THIS DOES NOT WORK because it will try to auto-cast the string representation to a BOX3D
 SELECT ST_ZMax('LINESTRING(1 3 4, 5 6 7)');
 
 --ERROR:  BOX3D parser - doesn't start with BOX3D(
@@ -952,7 +952,7 @@ SELECT ST_ZMin('BOX3D(-3 2 1, 3 4 1)' );
 st_zmin
 -------
 1
---Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D
+--Observe THIS DOES NOT WORK because it will try to auto-cast the string representation to a BOX3D
 SELECT ST_ZMin('LINESTRING(1 3 4, 5 6 7)');
 
 --ERROR:  BOX3D parser - doesn't start with BOX3D(

doc/reference_constructor.xml

@@ -224,7 +224,7 @@ POLYGON((10 10, 10 11, 11 11, 11 10, 10 10))
 		<refnamediv>
 		<refname>ST_MakeLine</refname>
 
-		<refpurpose>Creates a Linestring from Point, MultiPoint, or LineString geometries.</refpurpose>
+		<refpurpose>Creates a LineString from Point, MultiPoint, or LineString geometries.</refpurpose>
 		</refnamediv>
 
 		<refsynopsisdiv>
@@ -267,8 +267,8 @@ POLYGON((10 10, 10 11, 11 11, 11 10, 10 10))
 
 		<para>&Z_support;</para>
 
-		<para>Availability: 2.3.0 -  Support for multipoint input elements was introduced</para>
-		<para>Availability: 2.0.0 -  Support for linestring input elements was introduced</para>
+		<para>Availability: 2.3.0 -  Support for MultiPoint input elements was introduced</para>
+		<para>Availability: 2.0.0 -  Support for LineString input elements was introduced</para>
 		<para>Availability: 1.4.0 -  ST_MakeLine(geomarray) was introduced. ST_MakeLine aggregate functions was enhanced to handle more points faster.</para>
 
 		</refsection>
@@ -329,7 +329,7 @@ LINESTRING(1 2 3,3 4 5,6 6 6)
 		and creates one record for each track.
 		The result geometries are LineStrings composed of the GPS track points in the order of travel.</para>
 
-<para>Using aggregate <varname>ORDER BY</varname> provides a correctly-ordered linestring.</para>
+<para>Using aggregate <varname>ORDER BY</varname> provides a correctly-ordered LineString.</para>
 		<programlisting>
 SELECT gps.track_id, ST_MakeLine(gps.geom ORDER BY gps_time) As geom
 	FROM gps_points As gps
@@ -593,7 +593,7 @@ FROM (SELECT ST_ExteriorRing(
     As required by <code>ST_MakePolygon</code>,
     the boundary is forced to be a single LineString by using <xref linkend="ST_LineMerge" />.
     (However, note that if a province has more than one region or has islands
-    this will produce an invallid polygon.)
+    this will produce an invalid polygon.)
     Using a LEFT JOIN ensures all provinces are included even if they have no lakes.
     </para>
 
@@ -673,22 +673,19 @@ FROM provinces p;
 		<note><para>For geodetic coordinates, <varname>X</varname> is longitude and <varname>Y</varname> is latitude</para></note>
 
 		<para>&sqlmm_compliant; SQL-MM 3: 6.1.2</para>
-        <para>Enhanced: 3.2.0 now allows for a 3rd argument that is the srid</para>
 
 	  </refsection>
 
 
 	  <refsection>
 		<title>Examples: Geometry</title>
 
-        <programlisting>SELECT ST_Point( -71.104, 42.315, 4326)</programlisting>
-		<programlisting>SELECT ST_Point( -71.104, 42.315)</programlisting>
+		<programlisting>SELECT ST_SetSRID( ST_Point( -71.104, 42.315), 4326)</programlisting>
 	  </refsection>
 
 	  <refsection>
 		<title>Examples: Geography</title>
 
-		<programlisting>SELECT CAST(ST_Point(-71.104, 42.315, 4326) AS geography);</programlisting>
 		<programlisting>SELECT CAST(ST_SetSRID( ST_Point( -71.104, 42.315), 4326) AS geography);</programlisting>
 
 		<para>PostgreSQL also provides the <varname>::</varname> short-hand for casting</para>
@@ -733,7 +730,6 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
       <refsection>
         <title>Description</title>
         <para>Returns an Point with the given X, Y and Z coordinate values, and optionally an SRID number.</para>
-        <para>Availability: 3.2.0</para>
       </refsection>
 
       <refsection>
@@ -770,7 +766,6 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
       <refsection>
         <title>Description</title>
         <para>Returns an Point with the given X, Y and M coordinate values, and optionally an SRID number.</para>
-        <para>Availability: 3.2.0</para>
       </refsection>
 
       <refsection>
@@ -809,7 +804,6 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
       <refsection>
         <title>Description</title>
         <para>Returns an Point with the given X, Y, Z and M coordinate values, and optionally an SRID number.</para>
-        <para>Availability: 3.2.0</para>
       </refsection>
 
       <refsection>

doc/reference_editor.xml

@@ -131,7 +131,7 @@ Given a geometry collection, returns a multi-geometry containing only elements o
 			<para>Availability: 1.5.0</para>
 
 			<note><para>
-            Prior to 1.5.3 this function returned atomic inputs unchaanged, no matter type.
+            Prior to 1.5.3 this function returned atomic inputs unchanged, no matter type.
             In 1.5.3 non-matching single geometries returned a NULL result.
             In 2.0.0 non-matching single geometries return an EMPTY result of the requested type.
 			</para></note>
@@ -1318,7 +1318,7 @@ SELECT ST_AsText(ST_Normalize(ST_GeomFromText(
 				compressible storage type</ulink>. The function allows
 				specification of a different number of digits after the decimal
 				point in each dimension; unspecified dimensions are assumed to have
-				the precsion of the <code>x</code> dimension. Negative digits are
+				the precision of the <code>x</code> dimension. Negative digits are
 				interpreted to refer digits to the left of the decimal point, (i.e.,
 				<code>prec_x=-2</code> will preserve coordinate values to the
 				nearest 100.
@@ -1773,7 +1773,7 @@ LINESTRING(241.42 38.38,241.8 38.45)
 This function splits the input geometries and then moves every resulting
 component falling on the right (for negative 'move') or on the left (for
 positive 'move') of given 'wrap' line in the direction specified by the
-'move' parameter, finally re-unioning the pieces togheter.
+'move' parameter, finally re-unioning the pieces together.
     </para>
 
         <note><para>

doc/reference_input.xml

@@ -1283,7 +1283,7 @@ SELECT
 
 		<para>Return a BOX2D from a GeoHash string.</para>
 
-		<para>If no <varname>precision</varname> is specficified ST_Box2dFromGeoHash returns a BOX2D based on full precision of the input GeoHash string.</para>
+		<para>If no <varname>precision</varname> is specified ST_Box2dFromGeoHash returns a BOX2D based on full precision of the input GeoHash string.</para>
 
 		<para>If <varname>precision</varname> is specified ST_Box2dFromGeoHash will use that many characters from the GeoHash to create the BOX2D. Lower precision values results in larger BOX2Ds and larger values increase the precision.</para>
 

doc/reference_lrs.xml

@@ -58,7 +58,7 @@
 				<imageobject>
 				  <imagedata fileref="images/st_line_interpolate_point01.png" />
 				</imageobject>
-				<caption><para>A linestring with the interpolated point at 20% position (0.20) </para></caption>
+				<caption><para>A LineString with the interpolated point at 20% position (0.20) </para></caption>
 			  </mediaobject>
 			</informalfigure>
 			<programlisting>-- The point 20% along a line
@@ -223,7 +223,7 @@ SELECT ST_AsText(
 				<imageobject>
 				  <imagedata fileref="images/st_line_interpolate_points01.png" />
 				</imageobject>
-				<caption><para>A linestring with the interpolated points every 20% </para></caption>
+				<caption><para>A LineString with the interpolated points every 20% </para></caption>
 			  </mediaobject>
 			</informalfigure>
 			<programlisting>--Return points each 20% along a 2D line
@@ -382,7 +382,7 @@ FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As foo;
 				<imageobject>
 				  <imagedata fileref="images/st_line_substring01.png" />
 				</imageobject>
-				<caption><para>A linestring seen with 1/3 midrange overlaid (0.333, 0.666) </para></caption>
+				<caption><para>A LineString seen with 1/3 midrange overlaid (0.333, 0.666) </para></caption>
 			  </mediaobject>
 			</informalfigure>
 	<programlisting>