@@ -218,7 +218,7 @@ In the first example you create a spherical geospatial index on the
218
218
field named ``geo``, in the second example, you create a compound
219
219
index where the first field is a normal index, and the index of the
220
220
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
222
222
field in a compound index.
223
223
224
224
You must store data in the fields indexed using the ``s2d`` index
@@ -245,7 +245,7 @@ the following GeoJSON shapes:
245
245
246
246
{
247
247
"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 ] ] ]
249
249
}
250
250
251
251
To query ``s2d`` indexes, all current geospatial :ref:`query operators
@@ -259,7 +259,7 @@ for ``s2d`` indexes as ``2d`` indexes.
259
259
.. operator:: $intersect
260
260
261
261
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``,
263
263
and ``Polygon``.) You must pass :operator:`$intersect` a document
264
264
in GeoJSON format.
265
265
0 commit comments