1.1 --- a/README.html	Sun Aug 21 17:43:52 2016 +0200
     1.2 +++ b/README.html	Sun Aug 21 20:13:05 2016 +0200
     1.3 @@ -8,9 +8,9 @@
     1.4  <p>While many other spatial databases still use imprecise bounding boxes for many
     1.5  operations, pgLatLon supports more precise geometric calculations for all
     1.6  implemented operators. Efficient indexing of geometric objects is provided
     1.7 -using fractal indices. Optimizations on bit level (including logarithmic
     1.8 -compression) allow for a highly memory-efficient non-overlapping index suitable
     1.9 -for huge datasets.</p>
    1.10 +using space-filling fractal curves. Optimizations on bit level (including
    1.11 +logarithmic compression) allow for a highly memory-efficient non-overlapping
    1.12 +index suitable for huge datasets.</p>
    1.13  
    1.14  <p>Unlike competing spatial extensions for PostgreSQL, pgLatLon is available under
    1.15  the permissive MIT/X11 license to avoid problems with viral licenses like the

     2.1 --- a/README.mkd	Sun Aug 21 17:43:52 2016 +0200
     2.2 +++ b/README.mkd	Sun Aug 21 20:13:05 2016 +0200
     2.3 @@ -8,9 +8,9 @@
     2.4  While many other spatial databases still use imprecise bounding boxes for many
     2.5  operations, pgLatLon supports more precise geometric calculations for all
     2.6  implemented operators. Efficient indexing of geometric objects is provided
     2.7 -using fractal indices. Optimizations on bit level (including logarithmic
     2.8 -compression) allow for a highly memory-efficient non-overlapping index suitable
     2.9 -for huge datasets.
    2.10 +using space-filling fractal curves. Optimizations on bit level (including
    2.11 +logarithmic compression) allow for a highly memory-efficient non-overlapping
    2.12 +index suitable for huge datasets.
    2.13  
    2.14  Unlike competing spatial extensions for PostgreSQL, pgLatLon is available under
    2.15  the permissive MIT/X11 license to avoid problems with viral licenses like the