fix new geoJSON input format version

aerospike · Sep 5, 2023 · c734749 · c734749
1 parent 9a8c065
commit c734749
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/data-formats.md b/docs/data-formats.md
@@ -13,7 +13,7 @@ will work completely with the Aerospike data model.
 
 **Note**: GeoJSON and ByteArrays can not be nested in CDTs.
 
-In 2.0.1, a GeoJSON map with the keys "type" and "coordinates" will automatically be understood as a GeoJSON type.
+In 2.0.4, a GeoJSON map with the keys "type" and "coordinates" will automatically be understood as a GeoJSON type.
 
 ```javascript
 {
@@ -22,7 +22,7 @@ In 2.0.1, a GeoJSON map with the keys "type" and "coordinates" will automaticall
 }
 ```
 
-In version prior to 2.0.1, a GeoJSON object can be provided by sending a base64 encoded GeoJSON string.
+In version prior to 2.0.4, a GeoJSON object can be provided by sending a base64 encoded GeoJSON string.
 Base64 encoding the following string `{"type": "Point", "coordinates": [1.123, 4.156]}` results
 in `eyJ0eXBlIjogIlBvaW50IiwgImNvb3JkaW5hdGVzIjogWzEuMTIzLCA0LjE1Nl19Cg==`.
 To write the GeoJSON object use