Skip to content

Commit 0bc4c4d

Browse files
committed
Update source/release-notes/2.4.txt
fixed typos in s2d and changed polygon example to be correct (needs extra [])
1 parent 5395dd0 commit 0bc4c4d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/release-notes/2.4.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -218,7 +218,7 @@ In the first example you create a spherical geospatial index on the
218218
field named ``geo``, in the second example, you create a compound
219219
index where the first field is a normal index, and the index of the
220220
second field is a spherical geospatial index. Unlike ``2d`` indexes,
221-
fields indexed using the ``s2d`` type can do not have to be the first
221+
fields indexed using the ``s2d`` type do not have to be the first
222222
field in a compound index.
223223

224224
You must store data in the fields indexed using the ``s2d`` index
@@ -245,7 +245,7 @@ the following GeoJSON shapes:
245245

246246
{
247247
"type": "Polygon",
248-
"coordinates": [ [ 40, 5 ], [ 40, 6 ], [ 41, 6 ], [ 41, 5 ], [ 40, 5 ] ]
248+
"coordinates": [ [ [ 40, 5 ], [ 40, 6 ], [ 41, 6 ], [ 41, 5 ], [ 40, 5 ] ] ]
249249
}
250250

251251
To query ``s2d`` indexes, all current geospatial :ref:`query operators
@@ -259,7 +259,7 @@ for ``s2d`` indexes as ``2d`` indexes.
259259
.. operator:: $intersect
260260

261261
The :operator:`$intersect` selects all indexed points that
262-
intersect with provided geometry. (i.e. ``Point``, ``LineString``,
262+
intersect with the provided geometry. (i.e. ``Point``, ``LineString``,
263263
and ``Polygon``.) You must pass :operator:`$intersect` a document
264264
in GeoJSON format.
265265

0 commit comments

Comments
 (0)