DOCSP-43480 moved groom job intervals table (#363)

Author: kyuan-mongodb

source/admin/backup/grooms-page.txt

@@ -22,19 +22,7 @@ space.
 If no existing :manual:`snapshots </reference/glossary/#std-term-snapshot>` reference a given
 block, |onprem| considers the block *unused* or *dead*. |onprem| grooms
 blockstores after the snapshot drops below the threshold of living
-bytes. |onprem| runs groom jobs at the following minimum intervals:
-
-.. list-table::
-   :widths: 20 80
-   :header-rows: 1
-   :stub-columns: 1
-
-   * - Blockstore Location
-     - Minimum Groom Interval
-   * - MongoDB
-     - One time per year
-   * - |s3|
-     - One time every two weeks
+bytes. 
 
 .. _how-groom-jobs-work:
 
@@ -114,8 +102,21 @@ What Triggers a Groom Job
 - the percentage of living bytes drops below a given threshold and
 - the number of dead bytes reaches a minimum value.
 
-When grooming, Ops Manager removes all the dead bytes.
+|onprem| also runs groom jobs at the following minimum intervals:
 
+.. list-table::
+   :widths: 20 80
+   :header-rows: 1
+   :stub-columns: 1
+
+   * - Blockstore Location
+     - Minimum Groom Interval
+   * - S3
+     - One time every two weeks
+   * - MongoDB
+     - One time per year
+
+When grooming, Ops Manager removes all the dead bytes.
 
 .. list-table::
    :widths: 30 35 35