File tree Expand file tree Collapse file tree 2 files changed +5
-5
lines changed Expand file tree Collapse file tree 2 files changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -46,9 +46,9 @@ advance or are arbitrary. Wildcard indexes are *not* designed to replace
46
46
workload-based index planning.
47
47
48
48
To learn more about designing your data model and choosing
49
- indexes, see the :manual:`Data Modeling and Indexes
50
- </core/data-model-operations/#indexes>` guide in the {+mdb-server+}
51
- manual.
49
+ indexes, see the :manual:`Indexes
50
+ </core/data-model-operations/#indexes>` section of the Operational
51
+ Factors and Data Models guide in the {+mdb-server+} manual.
52
52
53
53
Sample Data
54
54
~~~~~~~~~~~
@@ -116,7 +116,7 @@ The following example removes the ``'_title_'`` index from the
116
116
Delete All Indexes
117
117
~~~~~~~~~~~~~~~~~~
118
118
119
- You can drop all indexes by calling the
119
+ You can delete all indexes by calling the
120
120
``MongoDB\Collection::dropIndexes()`` method on a collection:
121
121
122
122
.. literalinclude:: /includes/indexes/indexes.php
Original file line number Diff line number Diff line change @@ -22,7 +22,7 @@ Overview
22
22
23
23
Single field indexes are indexes with a reference to a single field of a
24
24
document in a collection. These indexes improve single field query and
25
- sort performance, and support :manual:`TTL Indexes </core/index-ttl>`
25
+ sort performance. They also support :manual:`TTL Indexes </core/index-ttl>`
26
26
that automatically remove documents from a collection after a certain
27
27
amount of time or at a specified clock time.
28
28
You can’t perform that action at this time.
0 commit comments