trivial: cleanup merge since repairDatabase removed in 4.2

Author: kay-kim

source/includes/extracts-manage-journaling.yaml

@@ -72,6 +72,5 @@ content: |
   replay journal files, :binary:`~bin.mongod` notes these events in the log
   output.
 
-  There is no reason to run :dbcommand:`repairDatabase` in these
-  situations.
+  There is no reason to run ``--repair``.
 ...

source/release-notes/4.2-compatibility.txt

@@ -89,8 +89,6 @@ MongoDB removes the MMAPv1 specific options:
 
 - ``verbose`` for :dbcommand:`collStats`
 
-- ``preserveClonedFilesOnFailure`` and ``backupOriginalFiles`` for
-  :dbcommand:`repairDatabase`
 
 - ``flags`` for :dbcommand:`create`
 

source/release-notes/4.2.txt

@@ -92,9 +92,6 @@ MongoDB removes the MMAPv1 specific options:
 
 - ``verbose`` for :dbcommand:`collStats`
 
-- ``preserveClonedFilesOnFailure`` and ``backupOriginalFiles`` for
-  :dbcommand:`repairDatabase`
-
 - ``flags`` for :dbcommand:`create`
 
 - ``paddingFactor``, ``paddingBytes``, ``preservePadding`` for