[postgis-devel] PATCH: Documentation spelling fixes.
Mak Kolybabi
mak_kolybabi at umanitoba.ca
Sat Aug 2 11:41:46 PDT 2008
I just started learning how to use PostGIS for work this week, and while reading
the documentation a few minor spelling mistakes started bugging me. I apologize
if this is not the appropriate way to submit a patch, but I could not find any
instructions on the website for it.
(patch attached)
--
Matthew Anthony Kolybabi (Mak)
<mak_kolybabi at umanitoba.ca>
() ASCII Ribbon Campaign | Against HTML e-mail
/\ www.asciiribbon.org | Against proprietary extensions
-------------- next part --------------
Index: README.postgis
===================================================================
--- README.postgis (revision 2911)
+++ README.postgis (working copy)
@@ -126,14 +126,14 @@
Where [prefix] above is extracted by `pg_config --configure`.
You can change them using ./configure switches.
-See CONFIGURARION section.
+See CONFIGURATION section.
CREATING NEW SPATIAL DATABASES
------------------------------
PostGIS support must be enabled for each database that requires
its usage. This is done by feeding the lwpostgis.sql (the enabler script)
-file to the targed database.
+file to the target database.
The enabler script requires the PL/pgSQL procedural language in order
to operate correctly, you can use the 'createlang' program from the
Index: doc/introduction.xml
===================================================================
--- doc/introduction.xml (revision 2911)
+++ doc/introduction.xml (working copy)
@@ -132,7 +132,7 @@
</listitem>
<listitem>
- <para>More information about Mapserver internet map server is
+ <para>More information about MapServer internet map server is
available at <ulink
url="http://mapserver.gis.umn.edu/">http://mapserver.gis.umn.edu</ulink>.</para>
</listitem>
Index: doc/release_notes.xml
===================================================================
--- doc/release_notes.xml (revision 2911)
+++ doc/release_notes.xml (working copy)
@@ -40,7 +40,7 @@
<para>This release provides performance enhancements to the relational
functions, adds new relational functions and begins the migration of our
- function names to the SQL-MM convension, using the spatial type (SP)
+ function names to the SQL-MM convention, using the spatial type (SP)
prefix.</para>
<simplesect>
@@ -71,7 +71,7 @@
<para>Extended curved geometry support into the geometry accessor and
some processing functions</para>
- <para>Began migration of functions to the SQL-MM naming convension;
+ <para>Began migration of functions to the SQL-MM naming convention;
using a spatial type (ST) prefix.</para>
<para>Added initial support for PostgreSQL 8.3</para>
Index: doc/reference.xml
===================================================================
--- doc/reference.xml (revision 2911)
+++ doc/reference.xml (working copy)
@@ -98,7 +98,7 @@
<para>Refer to
http://lin-ear-th-inking.blogspot.com/2007/06/subtleties-of-ogc-covers-spatial.html
- for an explaination of the need of this function.</para>
+ for an explanation of the need of this function.</para>
</listitem>
</varlistentry>
@@ -366,7 +366,7 @@
<term>ST_GeometryN(geometry,nth integer)</term>
<listitem>
- <para>Return the N'th geometry if the geometry is a
+ <para>Return the Nth geometry if the geometry is a
GEOMETRYCOLLECTION, MULTIPOINT, MULTILINESTRING or MULTIPOLYGON.
Otherwise, return NULL.</para>
@@ -391,7 +391,7 @@
<term>ST_PointN(geometry,nth integer)</term>
<listitem>
- <para>Return the N'th point in the first linestring in the
+ <para>Return the Nth point in the first linestring in the
geometry. Return NULL if there is no linestring in the
geometry.</para>
@@ -460,7 +460,7 @@
<term>ST_InteriorRingN(geometry,nth integer)</term>
<listitem>
- <para>Return the N'th interior ring of the polygon geometry.
+ <para>Return the Nth interior ring of the polygon geometry.
Return NULL if the geometry is not a polygon or the given N is out
of range.</para>
@@ -1080,7 +1080,7 @@
<term>ST_length_spheroid(geometry,spheroid)</term>
<listitem>
- <para>Calculates the length of of a geometry on an ellipsoid. This
+ <para>Calculates the length of a geometry on an ellipsoid. This
is useful if the coordinates of the geometry are in
latitude/longitude and a length is desired without reprojection.
The ellipsoid is a separate database type and can be constructed
@@ -1105,7 +1105,7 @@
<term>ST_length3d_spheroid(geometry,spheroid)</term>
<listitem>
- <para>Calculates the length of of a geometry on an ellipsoid,
+ <para>Calculates the length of a geometry on an ellipsoid,
taking the elevation into account. This is just like
length_spheroid except vertical coordinates (expressed in the same
units as the spheroid axes) are used to calculate the extra
Index: doc/README
===================================================================
--- doc/README (revision 2911)
+++ doc/README (working copy)
@@ -8,7 +8,7 @@
Rules are:
make html # output in html/postgis.html
- make chuncked-html
+ make chunked-html
make postgis.pdf
====================================================
Index: doc/faq.xml
===================================================================
--- doc/faq.xml (revision 2911)
+++ doc/faq.xml (working copy)
@@ -11,7 +11,7 @@
<answer>
<para>You can store point, line, polygon, multipoint, multiline,
multipolygon, and geometrycollections. These are specified in the Open
- GIS Well Known Text Format (with XYZ,XYM,XYZM extentions).</para>
+ GIS Well Known Text Format (with XYZ,XYM,XYZM extensions).</para>
</answer>
</qandaentry>
@@ -185,8 +185,8 @@
suggested that you do use <varname>AddGeometryColumn()</varname> to
create geometry tables.</para>
- <para>Mapserver is one application which makes use of the
- <varname>geometry_columns</varname> meta-data. Specifically, Mapserver
+ <para>MapServer is one application which makes use of the
+ <varname>geometry_columns</varname> meta-data. Specifically, MapServer
can use the SRID of the geometry column to do on-the-fly reprojection
of features into the correct map projection.</para>
</answer>
More information about the postgis-devel
mailing list