add info about ordered:false (#5712)

* add info about ordered:false

* adjust heading title

* add keywords metadata

Author: MongoCaleb

source/core/timeseries/timeseries-best-practices.txt

@@ -4,6 +4,9 @@ Best Practices for Time Series Collections
 
 .. default-domain:: mongodb
 
+.. meta::
+   :keywords: Time series, Best practices
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -21,25 +24,27 @@ Optimize Inserts
 To optimize insert performance for time series collections, perform the
 following actions.
 
-Batch Documents by Metadata
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Batch Document Writes
+~~~~~~~~~~~~~~~~~~~~~
 
 When inserting multiple documents:
 
 - To avoid network roundtrips, use a single
   :method:`~db.collection.insertMany()` statement as opposed to
   multiple :method:`~db.collection.insertOne()` statements.
 
-- If possible, order or construct batches to contain multiple
-  measurements per series (as defined by metadata).
+- If possible, construct batches to contain multiple measurements per series 
+  (as defined by metadata).
+ 
+- To improve performance, set the ``ordered`` parameter to ``false``.
 
 For example, if you have two sensors, ``sensor A`` and ``sensor B``, a
 batch containing multiple measurements from a single sensor incurs the
 cost of one insert, rather than one insert per measurement.
 
 The following operation inserts six documents, but only incurs the cost
 of two inserts (one per batch), because the documents are ordered by
-sensor:
+sensor. The ``ordered`` parameter is set to ``false`` to improve performance:
 
 .. code-block:: javascript
 
@@ -86,7 +91,9 @@ sensor:
          "timestamp": ISODate("2021-05-20T00:00:00.000Z"),
          "temperature": 26
       }
-   ] )
+   ], {
+      "ordered": false
+   })
 
 Use Consistent Field Order in Documents
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~