DOCSP-35701-timeseries-updates (#5954) (#5995)

* DOCSP-35701-timeseries-updates

* DOCSP-35701-timeseries-updates

* DOCSP-35701-timeseries-updates

* DOCSP-35701-timeseries-updates

---------

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/core/timeseries-collections.txt

@@ -98,19 +98,20 @@ store data in time-order. This format provides the following benefits:
 Behavior
 ~~~~~~~~
 
-Time series collections behave like normal collections. You can insert
-and query your data as you normally would.
+Time series collections behave like typical collections. You insert
+and query data as usual.
 
 MongoDB treats time series collections as writable non-materialized
 :ref:`views <views-landing-page>` backed by an internal collection. When
 you insert data, the internal collection automatically organizes time
 series data into an optimized storage format. 
 
-Since MongoDB 6.3, when you create a new time series collection, MongodDB 
-generates a :ref:`compound index <index-create-compound>` on the 
-:ref:`metaField and timeField <time-series-fields>` fields. Queries on time 
-series collections take advantage of this index, as well as the optimized 
-storage format, to improve query performance.
+Starting in MongoDB 6.3: if you create a new time series collection,
+MongoDB also generates a :ref:`compound index <index-create-compound>`
+on the :ref:`metaField and timeField <time-series-fields>` fields. To
+improve query performance, queries on time series collections use the
+new compound index. The compound index also uses the optimized storage
+format.
 
 .. tip::