*

Author: ianf-mongodb

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

@@ -41,7 +41,7 @@ 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 of 
+  preload a large time series collection and once completed migrate 
   the rest of your data.
 
 - If your migrating larges amounts of data, consider using 
@@ -50,11 +50,11 @@ Before you Begin
   of historical data at a time using table filters. This allows a large 
   job to be broken 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 table filters to create a new sync job that picks 
-  up from where the previously one left off. This approach saves you 
-  from re-importing your previous data from scratch
+- 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.
 
 Steps
 -----