Apply suggestions from code review

Co-authored-by: Jeff Allen <[email protected]>

Author: ianf-mongodb

source/mapping-rules/mapping-rule-options/time-series.txt

@@ -20,7 +20,7 @@ About this Task
 ---------------
 
 - You can use :ref:`field customizations <rm-field-customizations>` to 
-  convert string columns to datetime in Relational Migrator.
+  convert string columns to datetime fields in Relational Migrator.
 
 - CDC jobs that have time series configurations do not create the 
   time series collections until the CDC job completes. 
@@ -41,20 +41,19 @@ Before you Begin
 - If the time series data in your sync job does not require any 
   complex transformations you may benefit from migrating your time 
   series data as a separate sync job. This can make it easier to 
-  preload a large time series collection and once completed migrate 
-  the rest of your data.
+  preload a large time series collection and migrate the rest of your data after the initial job completes.
 
 - If your migrating larges amounts of data, consider using 
   :ref:`table filters <rm-table-filters>` to batch your sync jobs 
   based on logical conditions. For example, you might import one year 
-  of historical data at a time using table filters. This allows a large 
-  job to be broken into more manageable segments.
+  of historical data at a time using table filters. This allows you to break down a large 
+  job into more manageable segments.
 
 - If a long-running sync job fails unexpectedly (for example, due to a 
   database outage) and is not able to automatically recover, you may 
   be able to use :ref:`table filters <rm-table-filters>` to create a 
   new sync job that picks up from where the previous one left off. This 
-  approach saves you from re-importing your previous data from scratch.
+  approach lets you avoid having to repeat the entire sync job.
 
 Steps
 -----
@@ -90,15 +89,15 @@ Steps
 
       #. (Optional) Select a :guilabel:`Meta Field`.
 
-         ``Meta Field`` is the name of the field which contains metadata
+         ``Meta Field`` is the name of the field that contains metadata
          in each time series document. The metadata in the specified 
-         field should be data that is used to label a unique series of
+         field is used to label a unique series of
          documents. The metadata should rarely, if ever, change.
 
       #. Select a :guilabel:`Granularity`.
 
          ``Granularity`` should be a value that most closely matches 
-         the time between consecutive incoming timestamps. This
+         the time between consecutive incoming timestamps. Setting the correct granularity
          improves performance by optimizing how MongoDB stores data in the 
          collection. Possible values are ``seconds``, ``minutes``, and 
          ``hours``.