DOCSP-39421-detailed-extras

source/mongodump.txt

@@ -79,16 +79,16 @@ For a directory export, ``mongodump`` creates:
   <mongodump --out>` option.
 - A subdirectory in the root directory for each database.
 - A ``.metadata.json`` file for each collection in each database
-  directory. For example, if a collection is named ``sales``, the
-  metadata file is ``sales.metadata.json`. The BSON file is an Extended
+  directory. For example, if a collection name is ``sales``, the
+  metadata file is ``sales.metadata.json`. The file is an extended
   JSON v2 formatted file, and contains a document with the exported
   collection metadata, options, and indexes.
 - A corresponding BSON file with the collection documents for each
   collection.
 - A ``.metadata.json`` file for each view. A view doesn't have a BSON
   file.
 - An optional :term:`oplog` ``oplog.bson`` file, located in the root
-  directory, which contains write operations that occur during the
+  directory, which contains write operations that occurred during the
   ``mongodump`` run.
 
 Example directory export structure and files:
@@ -107,9 +107,8 @@ Example directory export structure and files:
    └── oplog.bson
 
 If you use the ``mongodump`` :option:`--gzip <mongodump --gzip>` option,
-the BSON files and ``.metadata.json`` files are compressed using
-``gzip``. The exported file extensions are ``.bson.gz`` and
-``.metadata.json.gz``.
+the BSON files and JSON metadata files are compressed using ``gzip``.
+The exported file extensions are ``.bson.gz`` and ``.metadata.json.gz``.
 
 Export Data to an Archive File
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~