(DOCSP-30191) Clarify the time for scheduling snapshots (#218)

Merging.

Author: JuliaMongo

source/includes/list-tables/backup/edit-snapshot.rst

@@ -48,30 +48,39 @@
    * - Allow point-in-time restores going back
 
      - Sets the number of days that |mms| retains oplogs alongside
-       snapshots.
-
-       .. seealso::
-
-          To learn how snapshots and point-in-time restores work,
-          see :doc:`/tutorial/nav/restore-overview`.
+       snapshots. To learn how snapshots and point-in-time restores work,
+       see :ref:`restore-overview`.
 
    * - Reference Time of Day (UTC)
 
      - Sets the time of day at
        `UTC <https://www.timeanddate.com/time/aboututc.html>`_ from
-       which the snapshot schedule starts. When you change the
-       :guilabel:`Reference Time of Day`, snapshots that are in
-       progress remain unaffected. Only snapshots taken after you
-       change the reference time follow the updated schedule.
-
-       .. note::
-
-          Changing the reference time changes the time of the next scheduled snapshot.
-          You can't make the next scheduled snapshot happen sooner than the current
-          next snapshot time. The current next snapshot time is the current reference
-          time plus the interval between snapshots.
-          
-          .. seealso::
-
-             To review more examples, see
-             :ref:`Snapshot Frequency and Retention <snapshot-frequency-and-retention>`.
+       which the snapshot schedule starts. When you change the value in
+       :guilabel:`Reference Time of Day`, snapshots that are in progress
+       or that are already scheduled remain unaffected. Only snapshots
+       taken after you change the reference time follow the updated schedule.
+
+       The following statements describe how |mms| behaves in relation
+       to the value you specify in :guilabel:`Reference Time of Day`:
+
+       - This value acts as a timer that |mms| uses for scheduling and then
+         taking the next snapshot. This value isn't the same as the time
+         when |mms| takes the next snapshot, but it is close to it. This
+         value differs from the actual time that |mms| uses to take a
+         snapshot by a small interval. You can't control this interval.
+       - If you leave this value blank, |mms| interprets it as ``null``,
+         starts the timer for scheduling the next snapshot, and then takes
+         the next snapshot after a short interval from the time when it
+         took the previous snapshot.
+  
+       - If you change the time value in this field, |mms| uses the new
+         time value as the starting time for scheduling the snapshot that
+         will occur *after the currently scheduled snapshot*.
+         In other words, for each snapshot that is already scheduled, |mms| uses
+         the time it already established: either based on the ``null`` value
+         plus a short interval, or based on the custom reference time value
+         plus a short interval. If you change the reference time value in
+         this field, the next scheduled snapshot will not happen sooner
+         than the snapshot that is already scheduled.
+
+         To review examples, see :ref:`Snapshot Frequency and Retention <snapshot-frequency-and-retention>`.

source/includes/steps-edit-backup-snapshot-schedule.yaml

@@ -14,11 +14,7 @@ level: 4
 ref: configure-snapshot-schedule
 content: |
   a. Enter the following information as needed.
-
-     .. seealso::
-
-        To learn about retention values, see
-        :ref:`snapshot-frequency-and-retention`.
+     To learn about retention values, see :ref:`snapshot-frequency-and-retention`.
 
      .. include:: /includes/list-tables/backup/edit-snapshot.rst
 

source/reference/monitoring.txt

@@ -6,11 +6,10 @@ Database Commands Used by {+magent+}
 
 .. default-domain:: mongodb
 
-The {+magent+} uses a set of MongoDB diagnostic, administrative, and
-other :manual:`database commands </reference/command>` to report on the status
-of your MongoDB deployment. The agent uses these commands:
+The {+magent+} uses a set of the following MongoDB diagnostic, administrative,
+and other :manual:`database commands </reference/command>` to report on
+the status of your MongoDB deployment.
 
-- :dbcommand:`_isSelf`
 - :dbcommand:`buildInfo`
 
 - :dbcommand:`collStats` on the following :manual:`local database

source/tutorial/nav/restore-overview.txt

@@ -1,3 +1,5 @@
+.. _restore-overview:
+
 ================
 Restore Overview
 ================