# HG changeset patch
# User jbe
# Date 1471789701 -7200
# Node ID 6bc81898fd3ba263b9ff05bfe42fc87a3f5fe29c
# Parent  96ee2db56beccdc30bdc096e8b72552d978a2f9a
Fixed typo in documentation and comments: "indicies" -> "indices"; Marked make-doc.sh as executable

diff -r 96ee2db56bec -r 6bc81898fd3b pgLatLon/README.html
--- a/pgLatLon/README.html	Thu Aug 18 20:19:58 2016 +0200
+++ b/pgLatLon/README.html	Sun Aug 21 16:28:21 2016 +0200
@@ -8,7 +8,7 @@
 <p>While many other spatial databases still use imprecise bounding boxes for many
 operations, pgLatLon supports more precise geometric calculations for all
 implemented operators. Efficient indexing of geometric objects is provided
-using fractal indicies. Optimizations on bit level (including logarithmic
+using fractal indices. Optimizations on bit level (including logarithmic
 compression) allow for a highly memory-efficient non-overlapping index suitable
 for huge datasets.</p>
 
@@ -161,13 +161,13 @@
 
 <p>Two kinds of indices are supported: B-tree and GiST indices.</p>
 
-<h4>B-tree indicies</h4>
+<h4>B-tree indices</h4>
 
 <p>A B-tree index can be used for simple equality searches and is supported by the
 <code>epoint</code>, <code>ebox</code>, and <code>ecircle</code> data types. B-tree indices can not be used for
 geographic searches.</p>
 
-<h4>GiST indicies</h4>
+<h4>GiST indices</h4>
 
 <p>For geographic searches, GiST indices must be used. The <code>epoint</code>, <code>ecircle</code>,
 and <code>ecluster</code> data types support GiST indexing. A GiST index for geographic
@@ -180,10 +180,10 @@
 CREATE INDEX name_of_index ON tbl USING gist (loc);
 </code></pre>
 
-<p>GiST indicies also support nearest neighbor searches when using the distance
+<p>GiST indices also support nearest neighbor searches when using the distance
 operator (<code>&lt;-&gt;</code>) in the ORDER BY clause.</p>
 
-<h4>Indicies on other data types (e.g. GeoJSON)</h4>
+<h4>Indices on other data types (e.g. GeoJSON)</h4>
 
 <p>Note that further types can be indexed by using an index on an expression with
 a conversion function. One conversion function provided by pgLatLon is the
diff -r 96ee2db56bec -r 6bc81898fd3b pgLatLon/README.mkd
--- a/pgLatLon/README.mkd	Thu Aug 18 20:19:58 2016 +0200
+++ b/pgLatLon/README.mkd	Sun Aug 21 16:28:21 2016 +0200
@@ -8,7 +8,7 @@
 While many other spatial databases still use imprecise bounding boxes for many
 operations, pgLatLon supports more precise geometric calculations for all
 implemented operators. Efficient indexing of geometric objects is provided
-using fractal indicies. Optimizations on bit level (including logarithmic
+using fractal indices. Optimizations on bit level (including logarithmic
 compression) allow for a highly memory-efficient non-overlapping index suitable
 for huge datasets.
 
@@ -158,13 +158,13 @@
 
 Two kinds of indices are supported: B-tree and GiST indices.
 
-#### B-tree indicies
+#### B-tree indices
 
 A B-tree index can be used for simple equality searches and is supported by the
 `epoint`, `ebox`, and `ecircle` data types. B-tree indices can not be used for
 geographic searches.
 
-#### GiST indicies
+#### GiST indices
 
 For geographic searches, GiST indices must be used. The `epoint`, `ecircle`,
 and `ecluster` data types support GiST indexing. A GiST index for geographic
@@ -176,10 +176,10 @@
 
     CREATE INDEX name_of_index ON tbl USING gist (loc);
 
-GiST indicies also support nearest neighbor searches when using the distance
+GiST indices also support nearest neighbor searches when using the distance
 operator (`<->`) in the ORDER BY clause.
 
-#### Indicies on other data types (e.g. GeoJSON)
+#### Indices on other data types (e.g. GeoJSON)
 
 Note that further types can be indexed by using an index on an expression with
 a conversion function. One conversion function provided by pgLatLon is the
diff -r 96ee2db56bec -r 6bc81898fd3b pgLatLon/latlon-v0001.c
--- a/pgLatLon/latlon-v0001.c	Thu Aug 18 20:19:58 2016 +0200
+++ b/pgLatLon/latlon-v0001.c	Sun Aug 21 16:28:21 2016 +0200
@@ -2384,7 +2384,7 @@
   PG_RETURN_POINTER(out);
 }
 
-/* GiST "compress" support function for indicies on points */
+/* GiST "compress" support function for indicis on points */
 PG_FUNCTION_INFO_V1(pgl_gist_compress_epoint);
 Datum pgl_gist_compress_epoint(PG_FUNCTION_ARGS) {
   GISTENTRY *entry = (GISTENTRY *) PG_GETARG_POINTER(0);
@@ -2411,7 +2411,7 @@
   PG_RETURN_POINTER(retval);
 }
 
-/* GiST "compress" support function for indicies on circles */
+/* GiST "compress" support function for indicis on circles */
 PG_FUNCTION_INFO_V1(pgl_gist_compress_ecircle);
 Datum pgl_gist_compress_ecircle(PG_FUNCTION_ARGS) {
   GISTENTRY *entry = (GISTENTRY *) PG_GETARG_POINTER(0);
@@ -2438,7 +2438,7 @@
   PG_RETURN_POINTER(retval);
 }
 
-/* GiST "compress" support function for indicies on clusters */
+/* GiST "compress" support function for indices on clusters */
 PG_FUNCTION_INFO_V1(pgl_gist_compress_ecluster);
 Datum pgl_gist_compress_ecluster(PG_FUNCTION_ARGS) {
   GISTENTRY *entry = (GISTENTRY *) PG_GETARG_POINTER(0);
@@ -2467,7 +2467,7 @@
   PG_RETURN_POINTER(retval);
 }
 
-/* GiST "decompress" support function for indicies */
+/* GiST "decompress" support function for indices */
 PG_FUNCTION_INFO_V1(pgl_gist_decompress);
 Datum pgl_gist_decompress(PG_FUNCTION_ARGS) {
   /* return passed pointer without transformation */
diff -r 96ee2db56bec -r 6bc81898fd3b pgLatLon/make-doc.sh