DOCSP-25986 improve style of limitations page (#2047)

* DOCSP-25986 timeseries limitations restyling

* DOCSP-25986 timeseries limitations restyling

* Review Feedback

* Staging fixes

* Merge feedback

Author: Dave Cuthbert

source/core/timeseries/timeseries-limitations.txt

@@ -16,33 +16,33 @@ Time Series Collection Limitations
    :description: Time Series, IOT
    :keywords: Time Series, IOT
 
-This page describes limitations of time series collections.
+This page describes limitations on using :ref:`time series collections
+<manual-timeseries-collection>`.
 
 Unsupported Features
 ~~~~~~~~~~~~~~~~~~~~~
 
-The following features are not supported for 
-:ref:`time series collections <manual-timeseries-collection>`.
+The following features are not supported for time series collections:
 
 * :atlas:`Atlas Search </atlas-search>`
-* :doc:`Change streams </changeStreams>`
+* :ref:`Change streams <changeStreams>`
 * :ref:`{+csfle+} <manual-csfle-feature>`
 * :realm:`Database Triggers </triggers/database-triggers>`
 * :realm:`GraphQL API </graphql>`
-* :realm:`Atlas Device Sync </sync>` (Atlas Device Sync is supported if
-  the time series collections are asymmetrically synchronized. For
-  details, see :realm:`Enable Atlas Device Sync
-  </sync/configure/enable-sync>`.)
+* :ref:`Schema validation rules <schema-validation-overview>`
 * :dbcommand:`reIndex`
 * :dbcommand:`renameCollection`
-* :doc:`Schema validation rules </core/schema-validation>`
+
+:realm:`Atlas Device Sync </sync>` is only supported if the time series
+collections are asymmetrically synchronized. For details, see
+:realm:`Enable Atlas Device Sync </sync/configure/enable-sync>`.
 
 Aggregation $out and $merge
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can't use aggregation pipeline stages :pipeline:`$out` and :pipeline:`$merge`
-to output or merge into to :ref:`time series collections
-<manual-timeseries-collection>` from another collection.
+You cannot use the :pipeline:`$out` or :pipeline:`$merge` aggregation
+pipeline stages to add data from another collection to a time series
+collection.
 
 .. _timeseries-limitations-updates-deletes:
 
@@ -54,18 +54,19 @@ operations.
 
 Delete commands must meet the following requirements:
 
-- The query may only match on ``metaField`` field values.
-- The delete command may not limit the number of documents to be
-  deleted. You must use a delete command with ``justOne: false`` or the
+- You can only match on :ref:`metaField <time-series-fields>` field
+  values.
+- Your delete command must not limit the number of documents to be
+  deleted. Set ``justOne: false`` or use the
   :method:`~db.collection.deleteMany()` method.
 
 Update commands must meet the following requirements:
 
 .. include:: /includes/time-series/fact-update-limitations.rst
 
-In MongoDB 5.0, :ref:`Time series collections
-<manual-timeseries-collection>` only support insert operations and read
-queries. Updates and manual delete operations result in an error.
+In MongoDB 5.0, time series collections only support insert operations
+and read queries. Updates and manual delete operations result in an
+error.
 
 To automatically delete old data, :ref:`set up automatic removal (TTL)
 <set-up-automatic-removal>`.
@@ -78,32 +79,32 @@ To remove all documents from a collection, use the
 Time Series Secondary Indexes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+There is improved support for secondary indexes in MongoDB 6.0.
+
 Time Series Secondary Indexes with MongoDB 6.0 and Later
 ````````````````````````````````````````````````````````
 
 Starting in MongoDB 6.0, you can add a :term:`secondary index <secondary
 index>` to any field.
 
-These index types aren't supported:
-
-- :doc:`Text </core/index-text>`
-- :doc:`2d </core/2d>`
+These index types are not supported:
 
-These index properties aren't supported:
+- :ref:`Text indexes <index-feature-text>`
+- :ref:`2d indexes <2d-index>`
+- :ref:`Unique indexes <index-type-unique>`
 
-- :doc:`TTL </core/index-ttl>`. For TTL deletion, use
-  :ref:`expireAfterSeconds <db.createCollection.expireAfterSeconds>`.
-- :doc:`Unique </core/index-unique>`
+The :ref:`TTL <index-feature-ttl>` index property is not supported. For
+TTL deletion, use :ref:`expireAfterSeconds
+<db.createCollection.expireAfterSeconds>`.
 
-The :doc:`multikey index </core/index-multikey>` type is allowed on the
-``metaField`` only.
+You can only use the :ref:`multikey index <index-type-multikey>` type on
+the ``metaField``.
 
-These index properties are partially supported:
+These index properties are partially supported. You can create:
 
-- :doc:`Partial indexes </core/index-partial>` are allowed on all fields
-  except the ``metaField`` and ``timeField``.
-- :doc:`Sparse indexes </core/index-sparse>` are allowed on the
-  ``metaField`` only.
+- :ref:`partial indexes <index-type-partial>` on every field except
+  ``metaField`` and ``timeField``.
+- :ref:`sparse indexes <index-type-sparse>` on the ``metaField``.
 
 For improvements to time series secondary indexes available starting in
 MongoDB 6.0, see :ref:`timeseries-add-secondary-index-mongodb-6.0`.
@@ -115,10 +116,10 @@ Time Series Secondary Indexes with MongoDB 5.0 and Earlier
 
 In MongoDB 5.0 and earlier:
 
-- Secondary indexes can only be defined on the ``metaField`` or the
-  ``timeField``.
+- The ``metaField`` can have secondary indexes.
+- The ``timeField``  can have secondary indexes.
 - If the ``metaField`` is a document, you can add secondary indexes on
-  fields inside that document.
+  fields inside the document.
 
 .. seealso::
 
@@ -127,18 +128,18 @@ In MongoDB 5.0 and earlier:
 Capped Collections
 ~~~~~~~~~~~~~~~~~~
 
-A time series collection can't be created as a :ref:`capped collection
+You cannot create a time series collection as a :ref:`capped collection
 <manual-capped-collection>`.
 
 Modification of Collection Type
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-A collection's type can only be set when creating the collection:
+You can only set the collection type when you create a collection:
 
-- An existing collection can't be converted into a :ref:`time series
-  collection <manual-capped-collection>`.
-- A :ref:`time series collection <manual-capped-collection>` can't be
-  converted into a different collection type.
+- An existing collection cannot be converted into a time series
+  collection.
+- A time series collection cannot be converted into a different
+  collection type.
 
 To move data from an existing collection to a time series collection,
 :ref:`migrate data into a time series collection
@@ -148,27 +149,29 @@ Modification of ``timeField`` and ``metaField``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can only set a collection's ``timeField`` and ``metaField``
-parameters when creating the collection. After creation these parameters
-can't be modified.
+parameters when you create the collection. You cannot modify these
+parameters later.
 
 .. _timeseries-limitations-granularity:
 
 Modification of ``granularity``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Once the ``granularity`` is set it can only be increased by one level at
-a time. From ``"seconds"`` to ``"minutes"`` or from ``"minutes"`` to
-``"hours"``. Other changes are not allowed. If you need to change the
-``granularity`` from ``"seconds"`` to ``"hours"``, first increase the
-``granularity`` to ``"minutes"`` and then to ``"hours"``.
+After you set the ``granularity``, you can only increase it one level at
+a time. The ``granularity`` can change from ``"seconds"`` to
+``"minutes"`` or from ``"minutes"`` to ``"hours"``. Other changes are
+not allowed. 
+
+To change the ``granularity`` from ``"seconds"`` to ``"hours"``, first
+increase the ``granularity`` to ``"minutes"`` and then to ``"hours"``.
 
 .. _time-series-limitations-sharding:
 
 Sharding
 ~~~~~~~~
 
-Starting in MongoDB 5.1 (and 5.0.6), sharded time series collections are
-supported.
+Starting in MongoDB 5.1 (and 5.0.6), you can create sharded time series
+collections.
 
 In versions earlier than MongoDB 5.0.6, you cannot shard time series
 collections.
@@ -191,14 +194,13 @@ Shard Key Fields
 Resharding
 ``````````
 
-You can't reshard sharded time series collections.
+You cannot reshard sharded time series collections.
 
 Transactions
 ~~~~~~~~~~~~
 
-You can't write to :ref:`time series collections
-<manual-timeseries-collection>` in :doc:`transactions
-</core/transactions>`.
+You cannot write to time series collections in :ref:`transactions
+<transactions>`.
 
 .. note::
 
@@ -213,3 +215,4 @@ Views
 
 - You cannot create a view from a time series bucket collection
   namespace (namely, a collection prefixed with ``system.buckets``).
+

source/includes/time-series/fact-update-limitations.rst

@@ -1,8 +1,8 @@
-- The query only matches on ``metaField`` field values.
-- The update command only modifies the ``metaField`` field value.
-- The update document can only contain :ref:`update operator
+- You can only match on the ``metaField`` field value.
+- You can only modify the ``metaField`` field value.
+- Your update document can only contain :ref:`update operator
   <update-operators>` expressions.
-- The update command must not limit the number of documents to be
+- Your update command must not limit the number of documents to be
   updated. Set ``multi: true`` or use the
   :method:`~db.collection.updateMany()` method. 
-- The update command must not set :ref:`upsert: true <update-upsert>`.
+- Your update command must not set :ref:`upsert: true <update-upsert>`.