DOC-527 | Re-organize geospatial data representation and interpretation (#384)

* Re-organize geo representation

* Fix links

* Remove anchor link that can't work in Swagger

* Fix another link

* Add check for same page anchor links

* Apply to 3.10 and 3.11

* Adjust link label

* Fix internal links to anchors

* Avoid generating empty previous link

* Fix more links

* Check internal links to anchors on other pages

Need to exclude pages that generate headlines from data or Hugo fails, so this kind of check is incomplete

Author: Simran-B

site/content/3.10/about-arangodb/features/community-edition.md

@@ -141,7 +141,7 @@ see [arangodb.com/community-server/](https://www.arangodb.com/community-server/)
   Flexible data field pre-processing with custom queries and the ability to
   chain built-in and custom Analyzers. Language-agnostic tokenization of text.
 
-- [**GeoJSON Support**](../../index-and-search/indexing/working-with-indexes/geo-spatial-indexes.md#geojson):
+- [**GeoJSON Support**](../../aql/functions/geo.md#geojson):
   Geographic data encoded in the popular GeoJSON format can be stored and used
   for geo-spatial queries.
 

site/content/3.10/aql/functions/arangosearch.md

@@ -1073,7 +1073,7 @@ be used in conjunction with ArangoSearch.
 
 `GEO_CONTAINS(geoJsonA, geoJsonB) → bool`
 
-Checks whether the [GeoJSON object](../../index-and-search/indexing/working-with-indexes/geo-spatial-indexes.md#geojson) `geoJsonA`
+Checks whether the [GeoJSON object](geo.md#geojson) `geoJsonA`
 fully contains `geoJsonB` (every point in B is also in A).
 
 - **geoJsonA** (object\|array): first GeoJSON object or coordinate array
@@ -1089,7 +1089,7 @@ fully contains `geoJsonB` (every point in B is also in A).
 
 `GEO_DISTANCE(geoJsonA, geoJsonB) → distance`
 
-Return the distance between two [GeoJSON objects](../../index-and-search/indexing/working-with-indexes/geo-spatial-indexes.md#geojson),
+Return the distance between two [GeoJSON objects](geo.md#geojson),
 measured from the `centroid` of each shape.
 
 - **geoJsonA** (object\|array): first GeoJSON object or coordinate array
@@ -1105,7 +1105,7 @@ measured from the `centroid` of each shape.
 
 `GEO_IN_RANGE(geoJsonA, geoJsonB, low, high, includeLow, includeHigh) → bool`
 
-Checks whether the distance between two [GeoJSON objects](../../index-and-search/indexing/working-with-indexes/geo-spatial-indexes.md#geojson)
+Checks whether the distance between two [GeoJSON objects](geo.md#geojson)
 lies within a given interval. The distance is measured from the `centroid` of
 each shape.
 
@@ -1129,7 +1129,7 @@ each shape.
 
 `GEO_INTERSECTS(geoJsonA, geoJsonB) → bool`
 
-Checks whether the [GeoJSON object](../../index-and-search/indexing/working-with-indexes/geo-spatial-indexes.md#geojson) `geoJsonA`
+Checks whether the [GeoJSON object](geo.md#geojson) `geoJsonA`
 intersects with `geoJsonB` (i.e. at least one point of B is in A or vice versa).
 
 - **geoJsonA** (object\|array): first GeoJSON object or coordinate array

site/content/3.10/aql/functions/date.md

@@ -7,6 +7,8 @@ description: >-
   ISO 8601 date time strings
 archetype: default
 ---
+## Date and time representations
+
 AQL offers functionality to work with dates, but it does not have a special data type
 for dates (neither does JSON, which is usually used as format to ship data into and
 out of ArangoDB). Instead, dates in AQL are represented by either numbers or strings.