Fix naming of 'spatial datatypes' anchor.

Author: jtibshirani

docs/reference/mapping/types.asciidoc

@@ -22,7 +22,7 @@ string::         <<text,`text`>>, <<keyword,`keyword`>> and <<wildcard,`wildcard
 <<nested>>::    `nested` for arrays of JSON objects
 
 [float]
-[[_spatial_datatypes]]
+[[spatial_datatypes]]
 === Spatial data types
 
 <<geo-point>>::     `geo_point` for lat/lon points

docs/reference/search/search-fields.asciidoc

@@ -89,7 +89,7 @@ POST twitter/_search
 <2> Using object notation, you can pass a `format` parameter to apply a custom
     format for the field's values. The date fields
     <<date,`date`>> and <<date_nanos, `date_nanos`>> accept a
-    <<mapping-date-format,date format>>. <<_spatial_datatypes, Spatial fields>>
+    <<mapping-date-format,date format>>. <<spatial_datatypes, Spatial fields>>
     accept either `geojson` for http://www.geojson.org[GeoJSON] (the default)
     or `wkt` for
     https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry[Well Known Text].

x-pack/plugin/spatial/src/main/java/org/elasticsearch/xpack/spatial/index/mapper/PointFieldMapper.java

@@ -137,7 +137,7 @@ public String typeName() {
             return CONTENT_TYPE;
         }
     }
-    
+
     // Eclipse requires the AbstractPointGeometryFieldMapper prefix or it can't find ParsedPoint
     // See https://bugs.eclipse.org/bugs/show_bug.cgi?id=565255
     protected static class ParsedCartesianPoint extends CartesianPoint implements AbstractPointGeometryFieldMapper.ParsedPoint {