expunging the word export from backup guide

Author: Sam Kleinman

source/administration/backups.txt

@@ -393,11 +393,11 @@ tool. As a result you may:
 
 .. _database-dumps:
 
-Binary Import/Export Formats
+Binary Dump/Restore Formats
 ----------------------------
 
-This section describes the process for exporting the entire contents
-of your MongoDB instance, to a file in a binary format. This command
+This section describes the process for writing the entire contents of
+your MongoDB instance, to a file in a binary format. This command
 provides the best option for full system database backups if
 disk-level snapshots are not available.
 
@@ -411,8 +411,8 @@ disk-level snapshots are not available.
    If your system has disk level snapshot capabilities, consider the
    backup methods described :ref:`above <block-level-backup>`.
 
-Database Export with :program:`mongodump`
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Database Dump with :program:`mongodump`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The :program:`mongodump` utility performs a live backup the data, or
 can work against an inactive set of database
@@ -461,9 +461,9 @@ configuration. Consider the following example:
    mongodump --dbpath /srv/mongodb
 
 Additionally, the ":option:`--host <mongodump --host>`" and
-":option:`--port <mongodump --port>`" options allow you to
-specify a non-local host to connect to capture the export. Consider
-the following example:
+":option:`--port <mongodump --port>`" options allow you to specify a
+non-local host to connect to capture the dump. Consider the following
+example:
 
 .. code-block:: sh
 
@@ -489,7 +489,7 @@ will look for a database dump in the ``dump/`` directory and restore
 that. If you wish to restore to a non-default host, the
 ":option:`--host <mongod>`" and ":option:`--port <mongod --port>`"
 options allow you to specify a non-local host to connect to capture
-the export. Consider the following example:
+the dump. Consider the following example:
 
 .. code-block:: sh
 
@@ -559,17 +559,17 @@ across all shards.
 Shard Clusters
 ~~~~~~~~~~~~~~
 
-Using Database Exports From a Cluster
-`````````````````````````````````````
+Using Database Dumps From a Cluster
+```````````````````````````````````
 
 If you have a small collection of data, the easiest way to connecting
-to the :program:`mongos` and taking a dump or export of the database
-from the running copy. This will create a consistent copy of the data
-in your database. If your data corpus is small enough that:
+to the :program:`mongos` and taking a dump of the database from the
+running copy. This will create a consistent copy of the data in your
+database. If your data corpus is small enough that:
 
 - it's possible to store the entire backup on one system, or a single
   storage device. Consider both backups of entire instances, and
-  incremental exports of data.
+  incremental dups of data.
 
 - the state of the database at the beginning of the operation is
   not significantly different than the state of the database at the
@@ -582,21 +582,20 @@ in your database. If your data corpus is small enough that:
 Using Conventional Backups from All Database Instances
 ``````````````````````````````````````````````````````
 
-If you there is no way to conduct a backup reasonably using an export,
+If you there is no way to conduct a backup reasonably with a dump,
 then you'll need to either snapshot the database using the
 :ref:`snapshot backup procedure <block-level-backup>` or create a
-binary dump of each database instance using :ref:`binary export
-systems <database-dumps>`.
-
-These backups must not only capture the database in a
-consistent state, as described in the aforementioned procedures, but
-the :term:`shard cluster` needs to be consistent in itself. Also,
-disable the balancer process that equalizes the distribution of data
-among the :term:`shards <shard>` before taking the backup.
-
-You should also all cluster members so that your backups reflect your
-entire database system at a single point in time, even if your backup
-methodology does not require.
+binary dump of each database instance using :ref:`binary dump methods
+<database-dumps>`.
+
+These backups must not only capture the database in a consistent
+state, as described in the aforementioned procedures, but the
+:term:`shard cluster` needs to be consistent in itself. Also, disable
+the balancer process that equalizes the distribution of data among the
+:term:`shards <shard>` before taking the backup.
+
+You should also lock all cluster members at once so that your backups
+reflect your entire database system at a single point in time.
 
 .. warning::