diff --git a/locale/zh/LC_MESSAGES/administration/monitoring.po b/locale/zh/LC_MESSAGES/administration/monitoring.po
index cf7c1fc7ade..e43b3fb12e3 100644
--- a/locale/zh/LC_MESSAGES/administration/monitoring.po
+++ b/locale/zh/LC_MESSAGES/administration/monitoring.po
@@ -77,7 +77,7 @@ msgid ""
 "Second, :doc:`database commands </reference/command>` return statistics "
 "regarding the current database state with greater fidelity."
 msgstr ""
-"第二种， :doc:`database commands </reference/command>` 返回有关当前数据库状"
+"第二种， :doc:`数据库命令 </reference/command>` 返回有关当前数据库状"
 "态更高保真度的统计信息。"
 
 #: ../source/administration/monitoring.txt:40
@@ -88,9 +88,10 @@ msgid ""
 "running MongoDB deployments as well as providing visualization and alerts "
 "based on that data."
 msgstr ""
-"第三种， `MMS Monitoring Service <https://mms.mongodb.com/?"
-"pk_campaign=mongodb-org&pk_kwd=monitoring>`_ 从正在运行的MongoDB部署收集数据"
-"并提供可视化和基于该数据的警报。MMS是MongoDB提供的免费服务。"
+"第三种， |mms-home|，一个主机服务， :products:`Ops Manager, an on-"
+"premise solution available in MongoDB Enterprise Advanced </mongodb-"
+"enterprise-advanced?jmp=docs>` ，提供了对从运行中的MongoDB部署上收集数据的监控 "
+"，以及提供在那些数据上的可视化和警报。"
 
 #: ../source/administration/monitoring.txt:47
 msgid ""
@@ -102,7 +103,7 @@ msgstr ""
 
 #: ../source/administration/monitoring.txt:51
 msgid "MongoDB Reporting Tools"
-msgstr "MongoDB报告工具"
+msgstr "MongoDB报表工具"
 
 #: ../source/administration/monitoring.txt:53
 msgid ""
@@ -146,7 +147,7 @@ msgid ""
 "program/mongostat>` for details."
 msgstr ""
 "使用 :program:`mongostat` 以了解操作类型的分布，并告知容量规划。详细信息请参"
-"见 :doc:`mongostat manual </reference/program/mongostat>` 。"
+"见 :doc:`mongostat 手册 </reference/program/mongostat>` 。"
 
 #: ../source/administration/monitoring.txt:77
 msgid "``mongotop``"
@@ -282,7 +283,7 @@ msgid ""
 "size of the collection, the amount of disk space used by the collection, and"
 " information about its indexes."
 msgstr ""
-":dbcommand:`collStats` 在集合级别上提供类似 :dbcommand:`dbStats` 的统计数"
+"shell中的 :dbcommand:`collStats` 或者 :method:`db.collection.stats()` 在集合级别上提供类似 :dbcommand:`dbStats` 的统计数"
 "据，包括集合中对象的计数、集合的大小、集合占用的硬盘空间总量以及集合索引的相"
 "关信息。"
 
@@ -758,7 +759,7 @@ msgid ""
 "data is effectively distributed among nodes and that sharding operations "
 "are functioning appropriately."
 msgstr ""
-"在大多数情况下,:term:`sharded clusters <sharded cluster>` 的组件和所有其他的"
+"在大多数情况下, :term:`sharded clusters <sharded cluster>` 的组件和所有其他的"
 "MongoDB实例同样受益于监测和分析。另外，集群需要更深入的监测以确保数据被高效"
 "地分发在各节点之间，并且分片操作正确地发挥了作用。"
 
@@ -791,8 +792,6 @@ msgid ""
 "servers to ensure that the cluster remains well balanced and that :program:"
 "`mongos` instances can restart."
 msgstr ""
-"由于不可访问的配置服务器会严重影响一个分片集群的可用性,(所以),您应该监控配置"
-"服务器以确保群集保持良好的平衡并且 :program:`mongos` 实例可以重新启动。"
 
 #: ../source/administration/monitoring.txt:447
 msgid ""
@@ -801,8 +800,6 @@ msgid ""
 " config server becomes inaccessible. See the |mms-docs| and :opsmgr:`Ops "
 "Manager documentation </application>` for more information."
 msgstr ""
-"`MMS Monitoring <http://mms.mongodb.com>`_ 可以监控配置服务器并在配置服务器"
-"不可访问时创建通知."
 
 #: ../source/administration/monitoring.txt:454
 msgid "Balancing and Chunk Distribution"
diff --git a/locale/zh/LC_MESSAGES/administration/production-notes.po b/locale/zh/LC_MESSAGES/administration/production-notes.po
index 6789d5edb79..530c752f895 100644
--- a/locale/zh/LC_MESSAGES/administration/production-notes.po
+++ b/locale/zh/LC_MESSAGES/administration/production-notes.po
@@ -263,7 +263,7 @@ msgid ""
 "MMAPv1."
 msgstr ""
 "在SSD可用并且经济可行的条件下，尽可能地使用SSD。旋转式机械硬盘可以达到高性能，"
-"但是固态硬盘执行随机I/O操作的能力与 :program:`mongod` 的更新模式配合得很好。"
+"但是固态硬盘执行随机I/O操作的能力与MMAPv1模式配合得很好。"
 
 #: ../source/administration/production-notes.txt:297
 msgid ""
@@ -929,7 +929,7 @@ msgstr ""
 
 #: ../source/administration/production-notes.txt:772
 msgid "Key fields from ``iostat``:"
-msgstr "``iostat``中的关键字段："
+msgstr " ``iostat`` 中的关键字段："
 
 #: ../source/administration/production-notes.txt:774
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/aggregation.po b/locale/zh/LC_MESSAGES/aggregation.po
index bc18610b8b6..51fd4f915e5 100644
--- a/locale/zh/LC_MESSAGES/aggregation.po
+++ b/locale/zh/LC_MESSAGES/aggregation.po
@@ -26,10 +26,6 @@ msgid ""
 "/mongodb-analytics-learn-aggregation-example-exploratory-analytics-and-"
 "visualization?jmp=docs>`_"
 msgstr ""
-"聚合操作可以处理一组数据记录并返回计算后的结果。聚合操作将多个文档的值组合在一起，"
-"并且可以对这组数据执行一系列操作后返回单个结果。Mongodb提供了三种方法来执行聚合："
-":doc:`聚合管道 </core/aggregation-pipeline>`，:doc:`映射化简方法 </core/map-reduce>`，和"
-" :doc:`单一用途的聚合方法和命令 </core/single-purpose-aggregation>`。 "
 
 
 #: ../source/includes/extracts/additional-resources-aggregation.rst:7
@@ -76,9 +72,6 @@ msgid ""
 "function <aggregation-map-reduce>`, and :ref:`single purpose aggregation "
 "methods <single-purpose-agg-operations>`."
 msgstr ""
-"聚合管道是一个基于数据处理管道概念的框架，它用于执行聚合任务。使用这个框架，"
-"MongoDB可以让一个集合中的多个文档通过一个管道。这个管道会将这组文档转化为聚合结果，"
-"你可以通过数据库的 :dbcommand:`aggregate` 命令来访问这些结果。"
 
 
 #: ../source/aggregation.txt:25
@@ -93,8 +86,6 @@ msgid ""
 "multi-stage pipeline that transforms the documents into an aggregated "
 "result."
 msgstr ""
-"映射化简是一种处理大量数据的，多阶段的泛化数据聚合的方法。"
-"MongoDB提供了 :dbcommand:`mapReduce` 的数据库命令"
 
 
 #: ../source/aggregation.txt:32
@@ -112,8 +103,6 @@ msgid ""
 " :ref:`operators <aggregation-expression-operators>` for tasks such as "
 "calculating the average or concatenating a string."
 msgstr ""
-"MongoDB提供了一些针对特定数据的聚合操作，以支持一些公共的数据聚合的功能。"
-"这些操作包含返回文档个数、对某个字段的值去重、和简单的归类操作。"
 
 
 #: ../source/aggregation.txt:43
@@ -128,7 +117,6 @@ msgid ""
 "The aggregation pipeline can operate on a :doc:`sharded collection </core"
 "/sharding-introduction>`."
 msgstr ""
-"介绍了聚合操作的优化、限制、对分片集合的支持、和并发关系等内部细节。"
 
 
 #: ../source/aggregation.txt:50
diff --git a/locale/zh/LC_MESSAGES/applications/design-notes.po b/locale/zh/LC_MESSAGES/applications/design-notes.po
index 19df1b3b450..ff405251ae0 100644
--- a/locale/zh/LC_MESSAGES/applications/design-notes.po
+++ b/locale/zh/LC_MESSAGES/applications/design-notes.po
@@ -110,7 +110,7 @@ msgid ""
 " JSON-like documents.  BSON encodes additional type information. See "
 "`bsonspec.org <http://bsonspec.org/#/specification>`_ for more information."
 msgstr ""
-"MongoDB的数据被存储为 :meta-driver:`BSON </legacy/bson/>` 格式——类JSON文档的"
+"MongoDB的数据被存储为 BSON 格式——类JSON文档的"
 "二进制编码序列。BSON编码进去了额外的类型信息。更多信息请参见 `bsonspec.org "
 "<http://bsonspec.org/#/specification>`_  。"
 
@@ -151,7 +151,8 @@ msgid ""
 "the :method:`update` method reference documentation."
 msgstr ""
 "对于MongoDB 2.2或之前的版本，你可以在 :method:`update` 方法特定位置上的布尔"
-"型选项中指定 ``upsert`` 和 ``multi`` 选项。 "
+"型选项中指定 ``upsert`` 和 ``multi`` 选项。查阅 "
+" :method:`update` 方法参考文档。"
 
 #: ../source/applications/design-notes.txt:96
 msgid "BSON Document Size Limit"
@@ -172,10 +173,6 @@ msgid ""
 "atomic operation. These kinds of data modification pattern covers most "
 "common uses of transactions in other systems."
 msgstr ""
-"MongoDB没有 :doc:`fully generalized transactions </tutorial/isolate-"
-"sequence-of-operations/>`。如果你用灵活的文档建立的数据模型与你应用中的对象"
-"十分贴近的话，任何一个逻辑上的对象都将在一个MongoDB 文档中。MongoDB允许你在"
-"单个的原子操作中修改文档。这种数据修改模式涉及了其他系统中事务最普遍的用法。"
 
 #: ../source/applications/design-notes.txt:114
 msgid "Replica Set Considerations"
@@ -214,7 +211,7 @@ msgstr ""
 msgid ""
 "Use monitoring tools to alert you to lag events. See :doc:`/administration/"
 "monitoring` for a detailed discussion of MongoDB's monitoring options."
-msgstr "使用监视工具警告你延迟事件。"
+msgstr ""
 
 #: ../source/applications/design-notes.txt:136
 msgid "Specify appropriate write concern."
diff --git a/locale/zh/LC_MESSAGES/core/2dsphere.po b/locale/zh/LC_MESSAGES/core/2dsphere.po
index 74404e2c6c3..a1539c9e301 100644
--- a/locale/zh/LC_MESSAGES/core/2dsphere.po
+++ b/locale/zh/LC_MESSAGES/core/2dsphere.po
@@ -36,16 +36,12 @@ msgid ""
 "converts the data to GeoJSON :ref:`geojson-point`. For details on the "
 "supported GeoJSON objects, see :doc:`/reference/geojson`."
 msgstr ""
-"如下示例存储了GeoJSON `多点 <http://geojson.org/geojson-spec.html#id5>`_ 类型"
-"的坐标数据:"
 
 #: ../source/core/2dsphere.txt:30
 msgid ""
 "The default datum for an earth-like sphere is :term:`WGS84`. Coordinate-axis"
 " order is **longitude, latitude**."
 msgstr ""
-"如下示例存储了GeoJSON `多线段 <http://geojson.org/geojson-spec.html#id6>`_ 类"
-"型的坐标数据:"
 
 #: ../source/core/2dsphere.txt:36
 msgid "``2dsphere (Version 2)``"
@@ -86,9 +82,6 @@ msgid ""
 "of other types, only the ``2dsphere`` index field determines whether the "
 "index references a document."
 msgstr ""
-"对于所有的MongoDB地理查询， ``2dsphere`` 索引都是支持的，包括：包含，交叉，邻"
-"近。参见 :doc:`/reference/operator/query-geospatial` 了解可以支持地理空间查询"
-"的查询操作符。"
 
 #: ../source/core/2dsphere.txt:62
 msgid ""
@@ -96,10 +89,6 @@ msgid ""
 "``2dsphere (Version 1)`` indexes are *not* sparse by default and will reject"
 " documents with ``null`` location fields."
 msgstr ""
-"如果想创建 ``2dsphere`` 索引，请使用 :method:`db.collection.ensureIndex` 命"
-"令。另外， :ref:`复合 <index-type-compound>` ``2dsphere`` 索引可以索引一篇文"
-"档中多个地址和其他非位置型数据。参见 :doc:`/tutorial/build-a-2dsphere-index` "
-"了解更多细节。"
 
 #: ../source/core/2dsphere.txt:67
 msgid "Additional GeoJSON Objects"
@@ -112,9 +101,6 @@ msgid ""
 "multipolygon`, and :ref:`geojson-geometrycollection`. For details on all "
 "supported GeoJSON objects, see :doc:`/reference/geojson`."
 msgstr ""
-"索引版本2添加了对其他GeoJSON对象的支持： :ref:`geojson-multipoint`, :ref:"
-"`geojson-multilinestring`, :ref:`geojson-multipolygon`, and :ref:`geojson-"
-"geometrycollection`."
 
 #: ../source/core/2dsphere.txt:75
 msgid "Considerations"
@@ -147,9 +133,6 @@ msgid ""
 "syntax includes the location field. As such, index selection among multiple "
 "``2d`` indexes or ``2dsphere`` indexes is ambiguous."
 msgstr ""
-"对地理索引的之所以有这样的限制， 是因为 :dbcommand:`geoNear` 命令和 :"
-"pipeline:`$geoNear` 管道 的格式里没有包含位置索引键。因此，如何在多个 ``2d`` "
-"或者 ``2dsphere`` 索引中做选择这将造成歧义。"
 
 #: ../source/includes/fact-limitation-one-geo-index-per-collection.rst:14
 msgid ""
@@ -170,9 +153,6 @@ msgid ""
 "collection. However, you can create and maintain a geospatial index on a "
 "sharded collection by using a different field as the shard key."
 msgstr ""
-"注意， :ref:`geojson-multipoint`, :ref:`geojson-multilinestring`, :ref:"
-"`geojson-multipolygon`, 和 :ref:`geojson-geometrycollection` 都需要 "
-"``2dsphere`` 索引版本2."
 
 #: ../source/core/2dsphere.txt:94
 msgid "``2dsphere`` Indexed Field Restrictions"
diff --git a/locale/zh/LC_MESSAGES/core/aggregation-pipeline.po b/locale/zh/LC_MESSAGES/core/aggregation-pipeline.po
index 0d56224be4a..1743200a7a1 100644
--- a/locale/zh/LC_MESSAGES/core/aggregation-pipeline.po
+++ b/locale/zh/LC_MESSAGES/core/aggregation-pipeline.po
@@ -157,8 +157,6 @@ msgid ""
 "improved performance for certain sequences of operators. For details, see "
 ":doc:`/core/aggregation-pipeline-optimization`."
 msgstr ""
-"有的管道阶段可以使用管道表达式作为运算符。管道表达式可以对输入文档做指定的转换。"
-"管道表达式使用一个 :doc:`文档 </core/document>` 结构体，并且可以包含其他的 :ref:`表达式 <aggregation-expressions>` 。"
 
 #: ../source/core/aggregation-pipeline.txt:137
 msgid ""
@@ -188,7 +186,6 @@ msgid ""
 "/mongodb-time-series-data-part-2-analyzing-time-series-data-using-"
 "aggregation-framework?jmp=docs>`_"
 msgstr ""
-"如果在管道的 **开始** 阶段使用 :pipeline:`$match` 和 :pipeline:`$sort`，这两个操作符会使用索引提高性能。"
 
 #: ../source/includes/extracts/additional-resources-aggregation.rst:8
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/backups.po b/locale/zh/LC_MESSAGES/core/backups.po
index 7a13ec865ea..329e071fe73 100644
--- a/locale/zh/LC_MESSAGES/core/backups.po
+++ b/locale/zh/LC_MESSAGES/core/backups.po
@@ -29,7 +29,6 @@ msgstr ":ref:`backup-with-file-copies`"
 #: ../source/core/backups.txt:18
 msgid ":ref:`backup-and-restore-tools`"
 msgstr ""
-"MongoDB管理服务通过读取MongoDB集群的操作日志，对MongoDB的副本集合以及分片系统进行持续备份。"
 
 #: ../source/core/backups.txt:19
 msgid ":ref:`backup-with-mms`"
@@ -40,8 +39,6 @@ msgstr ""
 #: ../source/core/backups.txt:20
 msgid ":ref:`backup-with-mms-onprem`"
 msgstr ""
-"您可以通过 `注册MongoDB管理服务<http://mms.mongodb.com>`_ 来开始使用MongoDB管理服务备份，"
-"请在 :MongoDB管理服务:`MongoDB管理服务手册</>` 中查阅MongoDB管理服务完整的文档。"
 
 #: ../source/core/backups.txt:25
 msgid "Backup by Copying Underlying Data Files"
@@ -103,9 +100,6 @@ msgid ""
 ":program:`mongod` before copying the files. Otherwise, you will copy the "
 "files in an invalid state."
 msgstr ""
-"如果您的存储系统不支持快照，您可以直接使用 ``cp`` 、``rsyns`` ，或者其它相似的工具来拷贝这些文件。"
-"由于拷贝多个文件并不是一个原子性的操作，您必须在拷贝这些文件之前停止对 :program：`mongod` 的所有写入操作。"
-"否则的话，您将会在一个不可靠的状态下拷贝这些文件。"
 
 #: ../source/core/backups.txt:56
 msgid ""
@@ -149,9 +143,6 @@ msgid ""
 "sharded-cluster-with-mongodump`, and :doc:`/tutorial/backup-sharded-cluster-"
 "with-database-dumps` for more information."
 msgstr ""
-"请查阅 :doc:`/tutorial/backup-with-mongodump` ，  :doc:`/tutorial/backup-small-"
-"sharded-cluster-with-mongodump` 以及  :doc:`/tutorial/backup-sharded-cluster-"
-"with-database-dumps`  了解更多的信息。"
 
 #: ../source/core/backups.txt:142
 msgid "|MMS| Backup"
@@ -243,8 +234,6 @@ msgid ""
 "Describes procedure for restoring a replica set from an archived backup such"
 " as a :program:`mongodump` or |mms-home| Backup file."
 msgstr ""
-"描述从一个已归档的备份中恢复复制集的流程，例如一个 :program:`mongodump` 或者"
-" `MongoDB管理服务备份<https://mms.mongodb.com/?pk_campaign=mongodb-docs-admin-tutorials>`_  文件。"
 
 #: ../source/includes/toc/dfn-list-administration-backup-and-recovery.rst:15
 msgid ":doc:`/tutorial/backup-and-restore-tools`"
@@ -294,9 +283,6 @@ msgid ""
 "`Backup and it's Role in Disaster Recovery White Paper "
 "<https://www.mongodb.com/lp/white-paper/backup-disaster-recovery?jmp=docs>`_"
 msgstr ""
-"由拷贝基础数据产生的备份不支持复制集的时间点恢复，并且在更大型的分片集群中难以管理。"
-"此外，这些备份比较庞大，因为它们包含了索引以及复制了基础的存储填充及碎片。相反地，"
-" :program:`mongodump` 会产生更少的备份。"
 
 #: ../source/includes/extracts/additional-resources-backup.rst:7
 msgid ""
@@ -304,8 +290,6 @@ msgid ""
 "<http://www.mongodb.com/blog/post/backup-vs-replication-why-do-you-need-"
 "both?jmp=docs>`_"
 msgstr ""
-"MongoDB订阅者们可以在他们自己的基础设施上安装和运行相同的核软件 :ref:`backup-with-mms` 。"
-"MongoDB管理服务的On Prem版本拥有和云版本相似的功能，并且在标准版和企业版的订阅中均能获得。"
 
 #: ../source/includes/extracts/additional-resources-backup.rst:8
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/capped-collections.po b/locale/zh/LC_MESSAGES/core/capped-collections.po
index b39a823ac43..00f237c8bf1 100644
--- a/locale/zh/LC_MESSAGES/core/capped-collections.po
+++ b/locale/zh/LC_MESSAGES/core/capped-collections.po
@@ -43,8 +43,6 @@ msgid ""
 "operations in a :term:`replica set` uses a capped collection. Consider the "
 "following potential use cases for capped collections:"
 msgstr ""
-"例如，:term:`oplog.rs <oplog>` 集合用一个限制集存储一个在复制集上的操作日志。考"
-"虑下边限制集的潜在应用案例："
 
 #: ../source/core/capped-collections.txt:49
 msgid ""
@@ -81,7 +79,7 @@ msgstr "用自然顺序检索限制集中大部分最近插入的文档。这类
 msgid ""
 "The aggregation pipeline operator :pipeline:`$out` cannot write results to a "
 "capped collection."
-msgstr "聚合管道操作:pipeline:`$out`不能写结果到限制集中。"
+msgstr ""
 
 #: ../source/core/capped-collections.txt:113
 msgid "Procedures"
@@ -167,7 +165,7 @@ msgstr ""
 #: ../source/core/capped-collections.txt:186
 msgid ""
 "The ``size`` parameter specifies the size of the capped collection in bytes."
-msgstr "``size``参数用bytes指定限制集及的大小。"
+msgstr ""
 
 #: ../source/includes/warning-blocking-global.rst:3
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/data-model-design.po b/locale/zh/LC_MESSAGES/core/data-model-design.po
index 81dc584691b..a321f9d1865 100644
--- a/locale/zh/LC_MESSAGES/core/data-model-design.po
+++ b/locale/zh/LC_MESSAGES/core/data-model-design.po
@@ -87,10 +87,6 @@ msgid ""
 "documents grow after creation. With the MMAPv1 storage engine, document "
 "growth can impact write performance and lead to data fragmentation."
 msgstr ""
-"然而， 内嵌相关数据到同一个文档内会很容易导致文档的增长。 文档增长"
-"会影响写性能并导致数据碎片问题。更多信息请参见 :ref:`data-model-document-growth`。"
-"另外， MongoDB的文档大小必须小于16M。 超过这个大小的话，你可以考虑使用"
-" :doc:`GridFS </core/gridfs>`。"
 
 #: ../source/core/data-model-design.txt:56
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/data-modeling-introduction.po b/locale/zh/LC_MESSAGES/core/data-modeling-introduction.po
index 96879f7c45a..36cff9e04e7 100644
--- a/locale/zh/LC_MESSAGES/core/data-modeling-introduction.po
+++ b/locale/zh/LC_MESSAGES/core/data-modeling-introduction.po
@@ -26,7 +26,7 @@ msgid ""
 "documents in a collection share a similar structure."
 msgstr ""
 "MongoDB 的数据模式是一种 *灵活模式* 。关系型数据库要求你在插入数据之前必须先定义好一个"
-"表的模式结构，而MongoDB的 :term:`集合 <collection>` 则并不限制 :term:`文档` 结构。"
+"表的模式结构，而MongoDB的 :term:`集合 <collection>` 则并不限制 :term:`document` 结构。"
 "这种灵活性让对象和数据库文档之间的映射变得很容易。 即使数据记录之间有很大的变化，每个文档也"
 "可以很好的映射到各条不同的记录。 当然在实际使用中，同一个集合中的文档往往都有一个比较类似的结构。"
 
@@ -118,11 +118,6 @@ msgid ""
 "the data across multiple collections and would require multiple write "
 "operations that are not atomic collectively."
 msgstr ""
-"写操作在MongoDB里在文档级具有原子性 - 意即单个写操作不能针对两个以上的文档或者集合同时操作。"
-"由于一个有内嵌文档的非规范化，冗余数据模型包含了所有相关的数据，这样一个写操作就可以完成"
-"对一个对象所有相关数据的一次性插入或者更新。如果使用规范化，无冗余数据模型，那么一个对象的"
-"数据要分到多个集合里面的多个文档里去。这样一来就需要多个写操作来完成。这多个写操作作为一个整体"
-"是不具由原子性的。" 
 
 #: ../source/core/data-modeling-introduction.txt:83
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/operational-segregation.po b/locale/zh/LC_MESSAGES/core/operational-segregation.po
index 4b05ea0017a..1ab79af413f 100644
--- a/locale/zh/LC_MESSAGES/core/operational-segregation.po
+++ b/locale/zh/LC_MESSAGES/core/operational-segregation.po
@@ -44,7 +44,7 @@ msgid ""
 "or operational parameters, to ensure that certain :program:`mongod` instances "
 "are only used for reporting workloads or that certain high-frequency portions "
 "of a sharded collection only exist on specific shards."
-msgstr "MongoDB 也支持"
+msgstr ""
 
 #: ../source/core/operational-segregation.txt:42
 msgid "Specifically, with MongoDB, you can:"
diff --git a/locale/zh/LC_MESSAGES/core/replica-set-architecture-geographically-distributed.po b/locale/zh/LC_MESSAGES/core/replica-set-architecture-geographically-distributed.po
index 50f75ca9c2f..4be792c4f7a 100644
--- a/locale/zh/LC_MESSAGES/core/replica-set-architecture-geographically-distributed.po
+++ b/locale/zh/LC_MESSAGES/core/replica-set-architecture-geographically-distributed.po
@@ -24,9 +24,6 @@ msgid ""
 "<http://www.mongodb.com/lp/white-paper/multi-dc?jmp=docs>`_"
 
 msgstr ""
-"在多个数据中心建立复制集节点可以提高数据冗余小也可以在主数据中心不可用时提供"
-"很好的故障容忍性。在其他数据中心中得复制集节点应该将 :doc:`优先级设置为0 </"
-"core/replica-set-priority-0-member>` 来避免其升职为主节点。"
 
 #: ../source/includes/extracts/additional-resources-multi-dc.rst:7
 msgid ""
@@ -79,8 +76,6 @@ msgid ""
 "that even with a loss of a data center, the remaining replica set members "
 "can form a majority or at minimum, provide a copy of your data."
 msgstr ""
-"一个 :doc:`优先级为0的节点 </core/replica-set-priority-0-member>` 在另一个数"
-"据中心。这个节点将不能升职为主节点。"
 
 #: ../source/core/replica-set-architecture-geographically-distributed.txt:40
 msgid "Examples"
@@ -95,9 +90,6 @@ msgid ""
 "For example, for a three-member replica set, some possible distributions of "
 "members include:"
 msgstr ""
-"在下面这样的复制集中，主节点和一个从节点在 *数据中心1* 中， *数据中心2* 中有"
-"一个不能升职为主节点的  :doc:`优先级为0的从节点 </core/replica-set-"
-"priority-0-member>` 。"
 
 #: ../source/core/replica-set-architecture-geographically-distributed.txt:48
 msgid ""
@@ -120,18 +112,12 @@ msgid ""
 "If Data Center 2 goes down, the replica set remains writeable as the members"
 " in Data Center 1 can hold an election."
 msgstr ""
-"当 *数据中心1* 不可用了，我们可以在最短的时间内手动的从 *数据中心2* 中将数据"
-"恢复出来。若拥有适当的 :ref:`安全写级别 <write-concern>` ，将不会有数据丢失。"
 
 #: ../source/core/replica-set-architecture-geographically-distributed.txt:57
 msgid ""
 "Three data centers: one members to Data Center 1, one member to Data Center "
 "2, and one member to Data Center 3."
 msgstr ""
-"为了实现选举，主数据中心上应该有多数节点。同时也别忘了让复制集保持奇数个节"
-"点。当我们在其他数据中心新增节点而导致复制集拥有偶数个节点的时候，应该新建一"
-"个 :ref:`投票节点 <replica-set-arbiters>` 。参见 :doc:`/core/replica-set-"
-"elections` 获得更多选举的信息。"
 
 #: ../source/core/replica-set-architecture-geographically-distributed.txt:60
 #: ../source/core/replica-set-architecture-geographically-distributed.txt:80
diff --git a/locale/zh/LC_MESSAGES/core/replication-introduction.po b/locale/zh/LC_MESSAGES/core/replication-introduction.po
index fd3a827c591..e36047012e1 100644
--- a/locale/zh/LC_MESSAGES/core/replication-introduction.po
+++ b/locale/zh/LC_MESSAGES/core/replication-introduction.po
@@ -65,9 +65,6 @@ msgid ""
 "failure of one or more members. For more information on replication "
 "mechanics, see :ref:`replica-set-oplog` and :ref:`replica-set-sync`."
 msgstr ""
-"从节点从主节点上应用操作的过程是异步的。由于从节点是在主节点之后应用操作的，"
-"所以复制集在缺少某些成员的时候仍能继续运行。然而在这种情况下，从节点返回给客"
-"户端的数据可能并不是最新的数据。"
 
 #: ../source/core/replication-introduction.txt:95
 msgid "Automatic Failover"
@@ -94,10 +91,6 @@ msgid ""
 "See :ref:`replica-set-secondary-only-members`, :ref:`replica-set-hidden-"
 "members` and :ref:`replica-set-delayed-members` for more information."
 msgstr ""
-"复制集提供了一些选项来支持实际应用时的需求。例如，:doc:`将一个复制集分布在多"
-"个数据中心</core/replica-set-architecture-geographically-distributed>` ，又或"
-"是通过设置 :data:`~local.system.replset.members[n].priority` 来控制选举的结"
-"果。复制集同时也支持将成员用于报表、灾难恢复或是备份。"
 
 #: ../source/includes/extracts/additional-resources-replication-introduction.rst:4
 msgid "Additional Resources"
@@ -130,11 +123,6 @@ msgid ""
 "multiple copies of data on different database servers, replication provides "
 "a level of fault tolerance against the loss of a single database server."
 msgstr ""
-"**主节点** 接收所有来自客户端的写操作。一个复制集只能有一个主节点。由于在一个"
-"复制集中只有一个成员能够接收写操作，复制集为所有来自主节点的读提供了 **严格的"
-"一致性校验** 。主节点通过将所有数据集的变动记录到 :doc:`oplog </core/replica-"
-"set-oplog>` 中以支持复制的实现。参见 :doc:`主节点 </core/replica-set-"
-"primary>` 获得更多信息。"
 
 #: ../source/core/replication-introduction.txt:26
 msgid ""
@@ -210,12 +198,6 @@ msgid ""
 "In MongoDB, clients can see the results of writes before the writes are "
 ":term:`durable`:"
 msgstr ""
-"**从节点** 将主节点上的oplog复制过来并应用这些操作来修改其自己的数据集以确保"
-"从节点的数据集与主节点的数据集一致。一旦主节点不可用了，复制集就会将一个从节"
-"点选举成为新的主节点。客户端默认是从主节点进行读操作，但是客户端也可以通过指"
-"定 :doc:`复制集读选项 </core/read-preference>` 来将读操作发送给从节点。需要注"
-"意的是，在从节点上进行读操作时，所获得的数据可能不是此时主节点上的值。参见 :"
-"doc:`从节点 </core/replica-set-secondary>` 获得更多信息。"
 
 #: ../source/includes/list-visibility-of-data.rst:1
 msgid ""
@@ -242,8 +224,6 @@ msgid ""
 "For more information on read isolations, consistency and recency for "
 "MongoDB, see :doc:`/core/read-isolation-consistency-recency`."
 msgstr ""
-"参见 :ref:`replica-set-oplog` 和 :ref:`replica-set-sync` 获得更多信息。 参"
-"见 :ref:`replica-set-read-preference` 获得更多有关读操作与从节点的信息。"
 
 #: ../source/core/replication-introduction.txt:128
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/sharding-introduction.po b/locale/zh/LC_MESSAGES/core/sharding-introduction.po
index b887bc0b711..a013b219141 100644
--- a/locale/zh/LC_MESSAGES/core/sharding-introduction.po
+++ b/locale/zh/LC_MESSAGES/core/sharding-introduction.po
@@ -115,8 +115,6 @@ msgid ""
 "Sharded cluster has the following components: :term:`shards <shard>`, :term:"
 "`query routers <mongos>` and :term:`config servers <config server>`."
 msgstr ""
-"集群拥有以下组件: :term:`分片 <shard>`, :term:`分发路由 <mongos>`,:term:`配置"
-"服务器 <config server>`."
 
 #: ../source/core/sharding-introduction.txt:76
 msgid ""
@@ -306,10 +304,6 @@ msgid ""
 "splits. Splits are an efficient meta-data change. To create splits, MongoDB "
 "does *not* migrate any data or affect the shards."
 msgstr ""
-"分裂是防止某个数据块过大而进行的一个后台任务.当一个数据块的大小超过 :ref:`设"
-"定的数据块大小 <sharding-chunk-size>`时,MongoDB会将其一分为二,插入与更新触发"
-"分裂过程.分裂改变了元信息,但是效率很高.进行分裂时,MongoDB *不会* 迁移任何数"
-"据,对集群性能也没有影响."
 
 #: ../source/core/sharding-introduction.txt:216
 msgid "Balancing"
diff --git a/locale/zh/LC_MESSAGES/core/tag-aware-sharding.po b/locale/zh/LC_MESSAGES/core/tag-aware-sharding.po
index 5ae34de8944..a2dd9e8c86b 100644
--- a/locale/zh/LC_MESSAGES/core/tag-aware-sharding.po
+++ b/locale/zh/LC_MESSAGES/core/tag-aware-sharding.po
@@ -80,8 +80,6 @@ msgid ""
 "shards associated with a tag that has a :term:`shard key` range with an "
 "*upper* bound *greater* than the chunk's *lower* bound."
 msgstr ""
-"使用了标记方式的分片之后,范围下限小于标记的范围上限的数据块,会被均衡器迁移到"
-"这个标记所在的分片上."
 
 #: ../source/core/tag-aware-sharding.txt:50
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/core/write-performance.po b/locale/zh/LC_MESSAGES/core/write-performance.po
index a87ff9845fd..c816d7825f5 100644
--- a/locale/zh/LC_MESSAGES/core/write-performance.po
+++ b/locale/zh/LC_MESSAGES/core/write-performance.po
@@ -91,9 +91,6 @@ msgid ""
 "efficiently reuse free space created by document deletion or relocation as "
 "well as reduce the occurrences of reallocations in many cases."
 msgstr ""
-"一些更新操作，例如  :update:`$inc` 操作，并不会造成文档大小的增加。对这些更新"
-"操作，MongoDB可以就地执行这个更新操作。其它的像 :update:`$push` 这样的更新操作"
-"将会改变文档的大小。"
 
 #: ../source/core/write-performance.txt:63
 msgid ""
@@ -153,17 +150,12 @@ msgstr ""
 #: ../source/core/write-performance.txt:121
 msgid "For additional information on journaling, see :doc:`/core/journaling`."
 msgstr ""
-"当日志和数据文件位于相同的块设备时，数据文件和日志也会将不得不竞争数量有限的写"
-"操作。将日志移动到一个单独的设备有可能能够提高写操作的容量。"
 
 
 #: ../source/includes/extracts/additional-resources-performance-eval.rst:4
 msgid "Additional Resources"
 
 msgstr ""
-"如果应用在  :doc:`write concern </core/write-concern>` 中指定包含  :ref:"
-"`journaled <write-concern-replica-journaled>` ， :program:`mongod`  将会减少日"
-"志提交的时间间隔，这样将会提高整体的写入负载。"
 
 #: ../source/includes/extracts/additional-resources-performance-eval.rst:6
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/data-center-awareness.po b/locale/zh/LC_MESSAGES/data-center-awareness.po
index 32689176d9f..68278288982 100644
--- a/locale/zh/LC_MESSAGES/data-center-awareness.po
+++ b/locale/zh/LC_MESSAGES/data-center-awareness.po
@@ -64,7 +64,6 @@ msgid ""
 "Tags associate specific ranges of :term:`shard key` values with specific "
 "shards for use in managing deployment patterns."
 msgstr ""
-"标签使特定访问的 :term:`shard key` 值与特定的分片联系起来，应用在管理发布模式中。"
 
 #: ../source/includes/toc/dfn-list-spec-data-center-awareness.rst:12
 msgid ":doc:`/tutorial/administer-shard-tags`"
diff --git a/locale/zh/LC_MESSAGES/reference/method/db.collection.update.po b/locale/zh/LC_MESSAGES/reference/method/db.collection.update.po
index e7d9fe8d5c7..85d4f83172c 100644
--- a/locale/zh/LC_MESSAGES/reference/method/db.collection.update.po
+++ b/locale/zh/LC_MESSAGES/reference/method/db.collection.update.po
@@ -311,12 +311,6 @@ msgid ""
 "update so that no client can see the updated documents until they are all "
 "processed, or an error stops the update operation."
 msgstr ""
-"如果  ``multi`` 选项被设置成  ``true`` ，  :method:`~db.collection.update()` "
-"方法会更新所有 ``<query>`` 条件匹配到的文档记录。 ``multi`` 选项可以和其他读"
-"写操作符交叉使用。在未分片的集合中，可以使用独占操作符 （ :update:`"
-"$isolated` ）忽略批量更新操作， :update:`$isolated` 操作会让当前更新操作使用"
-"独占模式，在操作完成前忽略其他操作。在独占操作进行时，其他使用者都看不到正在"
-"被更新的文档记录，直到操作完成或发生异常。"
 
 #: ../source/reference/method/db.collection.update.txt:211
 msgid ""
@@ -359,9 +353,6 @@ msgid ""
 "To update specific fields in a document, use :ref:`update operators <update-"
 "operators>` in the ``<update>`` parameter."
 msgstr ""
-"如果要修改文档中的指定字段，可以在  ``<update>`` 参数中使用更新操作符（ :ref:"
-"`update operators <update-operators>` ）。如果  ``<update>`` 参数中有文档中不"
-"存在的字段， :method:`~db.collection.update()` 操作会在文档中加入这些字段。"
 
 #: ../source/reference/method/db.collection.update.txt:241
 msgid "For example, given a ``books`` collection with the following document:"
@@ -465,8 +456,6 @@ msgid ""
 "For more information on ``upsert`` option and the inserted document, :ref"
 ":`upsert-parameter`."
 msgstr ""
-"使用批量更新文档记录需要把 ``multi`` 选项设置成 ``true`` 。例如，下面的操作会"
-"更新所有 ``stock`` 小于  ``5`` 的文档记录："
 
 #: ../source/reference/method/db.collection.update.txt:401
 msgid "Update Multiple Documents"
@@ -513,9 +502,6 @@ msgstr ""
 #: ../source/reference/method/db.collection.update.txt:446
 msgid "Given a ``books`` collection that includes the following documents:"
 msgstr ""
-"下面的操作查找 :doc:`bios collection </reference/bios-example-collection>` 集"
-"合中第一个 ``_id`` 等于 ``1`` 的文档记录并在 ``awards`` 数组字段中添加一个内"
-"嵌文档："
 
 #: ../source/reference/method/db.collection.update.txt:465
 msgid ""
@@ -524,18 +510,11 @@ msgid ""
 "matching documents. If no matching documents exist, the operation inserts a "
 "new document."
 msgstr ""
-"下一个例子，使用更新操作符（ :update:`$set` ）和点号分隔法 :ref:`dot "
-"notation <document-dot-notation>` 访问 ``name`` 嵌入文档中的 ``middle`` 字"
-"段。使用追加操作符 :update:`$push` （ :update:`$push` operator ）在 "
-"``awards`` 数组中添加一个嵌入文档。"
 
 #: ../source/reference/method/db.collection.update.txt:478
 msgid ""
 "The operation updates all matching documents and results in the following:"
 msgstr ""
-"修改 ``name`` 字段中包含子文档的记录。更新操作符（ :update:`$set` ）修改 "
-"``name`` 文档中的 ``middle`` 字段。使用点号分隔法（ :ref:`dot notation "
-"<document-dot-notation>` ）访问内嵌文档中的字段。"
 
 #: ../source/reference/method/db.collection.update.txt:500
 msgid ""
@@ -543,8 +522,6 @@ msgid ""
 "the insertion of a document using the fields from both the ``<query>`` and "
 "the ``<update>`` specifications:"
 msgstr ""
-"在 ``awards`` 数字字段中添加一个元素。追加操作符（ :update:`$push` ）会在 "
-"``awards``字段中添加一个文档作为新元素。"
 
 #: ../source/reference/method/db.collection.update.txt:519
 msgid "WriteResult"
diff --git a/locale/zh/LC_MESSAGES/reference/sql-comparison.po b/locale/zh/LC_MESSAGES/reference/sql-comparison.po
index 6deec6d33d2..a6d5bbb3572 100644
--- a/locale/zh/LC_MESSAGES/reference/sql-comparison.po
+++ b/locale/zh/LC_MESSAGES/reference/sql-comparison.po
@@ -262,8 +262,6 @@ msgid ""
 "However, at the document level, :method:`~db.collection.update()` operations"
 " can add fields to existing documents using the :update:`$set` operator."
 msgstr ""
-"然而，在文档级别，可以使用 :method:`~db.collection.update()`方法中的"
-" :update:`$set`操作符添加新的字段到现有的文档中。"
 
 
 #: ../source/includes/table/sql-to-mongo-schema-examples.rst:73
@@ -271,8 +269,6 @@ msgid ""
 "However, at the document level, :method:`~db.collection.update()` operations"
 " can remove fields from documents using the :update:`$unset` operator."
 msgstr ""
-"然而，在文档级别，可以使用 :method:`~db.collection.update()`方法中的"
-":update:`$unset` 操作符从现有文档中删除一个字段。"
 
 
 #: ../source/reference/sql-comparison.txt:73
diff --git a/locale/zh/LC_MESSAGES/release-notes/3.0.po b/locale/zh/LC_MESSAGES/release-notes/3.0.po
index 0ca439148d4..283c44c00ff 100644
--- a/locale/zh/LC_MESSAGES/release-notes/3.0.po
+++ b/locale/zh/LC_MESSAGES/release-notes/3.0.po
@@ -24,9 +24,10 @@ msgid ""
 "MongoDB 3.0 is now available. Key features include support for the "
 "WiredTiger storage engine, pluggable storage engine API, ``SCRAM-SHA-1`` "
 "authentication mechanism, and improved ``explain`` functionality."
-msgstr "MongoDB 3.0目前正式发布了。主要的功能包括："
-"对WiredTiger存储引擎、可插拔存储引擎API、``SCRAM-SHA-1``"
-"认证机制以及改进的``explain``功能性的支持。"
+msgstr ""
+"MongoDB 3.0目前正式发布了。主要的功能包括："
+"对WiredTiger存储引擎、可插拔存储引擎API、``SCRAM-SHA-1`` "
+"认证机制以及改进的 ``explain`` 功能性的支持。"
 
 #: ../source/release-notes/3.0.txt:20
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/release-notes/3.2-upgrade.po b/locale/zh/LC_MESSAGES/release-notes/3.2-upgrade.po
index a2532b69038..df232da57f7 100644
--- a/locale/zh/LC_MESSAGES/release-notes/3.2-upgrade.po
+++ b/locale/zh/LC_MESSAGES/release-notes/3.2-upgrade.po
@@ -275,10 +275,6 @@ msgid ""
 ":doc:`/tutorial/upgrade-config-servers-to-replica-set` (requires MongoDB "
 "version 3.2.4 or later versions)."
 msgstr ""
-"一旦分片集群的二级制文件升级到3.2，现有的配置服务器将会继续"
-"作为  :program:`mongod` 实例的镜像运行。查阅"
-":doc:`/tutorial/upgrade-config-servers-to-replica-set` (要求 MongoDB "
-"版本 3.2.4 或者之后的版本)快回将现有配置服务器升级到复制集的指令。"
 
 #: ../source/includes/extracts/additional-resources-upgrades.rst:4
 msgid "Additional Resources"
diff --git a/locale/zh/LC_MESSAGES/tutorial/analyze-query-plan.po b/locale/zh/LC_MESSAGES/tutorial/analyze-query-plan.po
index f9354748ab3..cb602ac8d49 100644
--- a/locale/zh/LC_MESSAGES/tutorial/analyze-query-plan.po
+++ b/locale/zh/LC_MESSAGES/tutorial/analyze-query-plan.po
@@ -53,8 +53,6 @@ msgid ""
 "The following query retrieves documents where the ``quantity`` field has a "
 "value between ``100`` and ``200``, inclusive:"
 msgstr ""
-"想要使用 :method:`~cursor.explain()` 方法，可以在 :method:`~db.collection."
-"find()` 返回的游标上来调用这个方法。"
 
 #: ../source/tutorial/analyze-query-plan.txt:51
 #: ../source/tutorial/analyze-query-plan.txt:204
@@ -94,9 +92,6 @@ msgid ""
 "MongoDB had to scan ten documents (i.e. all documents in the collection) to "
 "find the three matching documents."
 msgstr ""
-"为了返回这5个文档，正如 :data:`~explain.nscanned` 字段显示的那样，查询在索引"
-"中扫描了5个文档，然后如 :data:`~explain.nscannedObjects` 字段所显示的那样，在"
-"集合中读取了5个完整的文档。"
 
 #: ../source/tutorial/analyze-query-plan.txt:109
 msgid ""
@@ -175,8 +170,6 @@ msgid ""
 "With :doc:`compound indexes </core/index-compound>`, the order of the fields"
 " matter."
 msgstr ""
-"想要手动的比较一个使用多个索引的查询的性能，你可以同时使用 :method:`~cursor."
-"hint()` 方法和 `~cursor.explain()` 方法。"
 
 #: ../source/tutorial/analyze-query-plan.txt:215
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-database-dumps.po b/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-database-dumps.po
index 441a27d1e88..bb4497b8cff 100644
--- a/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-database-dumps.po
+++ b/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-database-dumps.po
@@ -53,8 +53,6 @@ msgid ""
 "filesystem snapshots; otherwise the snapshot will only approximate a moment "
 "in time."
 msgstr ""
-"要备份一个数据库,需要在指定的数据库上有 ``read`` 权限.有一些角色提供了这个权"
-"限,比如 :authrole:`backup` 角色."
 
 #: ../source/tutorial/backup-sharded-cluster-with-database-dumps.txt:63
 msgid "Procedure"
@@ -74,10 +72,7 @@ msgid ""
 ":doc:`MMAPv1 </core/mmapv1>` and the :doc:`WiredTiger </core/wiredtiger>` "
 "storage engines. With previous versions of MongoDB, the procedure applied to"
 " :doc:`MMAPv1 </core/mmapv1>` only."
-
 msgstr ""
-"要备份数据库的用户以及 ref:`user-defined roles <user-defined-roles>` ,需要对 "
-"``admin`` 数据库有权限,MongoDB在 ``admin`` 数据库中存储了这些信息."
 
 #: ../source/tutorial/backup-sharded-cluster-with-database-dumps.txt:23
 msgid ""
@@ -87,10 +82,6 @@ msgid ""
 "snapshots to capture the backup data, and may be more efficient in some "
 "situations if your system configuration allows file system backups."
 msgstr ""
-"更确切地说,要想备份一个数据库的用户,必须在 ``admin`` 数据库的 :data:`admin."
-"system.users` 集合拥有 :authaction:`find` :ref:`action <security-user-"
-"actions>`.:authrole:`backup` 与 :authrole:`userAdminAnyDatabase` 角色都有这种"
-"权限."
 
 #: ../source/tutorial/backup-sharded-cluster-with-database-dumps.txt:30
 msgid ""
@@ -98,10 +89,6 @@ msgid ""
 "in particular, see :doc:`/core/backups` and :doc:`/administration/backup-"
 "sharded-clusters`."
 msgstr ""
-"要备份数据库上用户定义的角色,需要有 ``admin`` 数据库上 :data:`admin.system."
-"roles` 集合的 :authaction:`find` 权限.:authrole:`backup` 与 :authrole:"
-"`userAdminAnyDatabase` 角色都有这种权限."
-
 
 #: ../source/tutorial/backup-sharded-cluster-with-database-dumps.txt:40
 msgid "Access Control"
@@ -124,8 +111,6 @@ msgid ""
 "when running with :ref:`database profiling <database-profiling>`. "
 "Previously, users required an additional ``read`` access on this collection."
 msgstr ""
-"使用每个分片的复制集中一个从节点进行近似在某个时间点附近的备份,可以在备份时对"
-"集群的性能影响最小."
 
 #: ../source/tutorial/backup-sharded-cluster-with-database-dumps.txt:58
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-filesystem-snapshots.po b/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-filesystem-snapshots.po
index cfb46cdc5c7..e9f5c2642ca 100644
--- a/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-filesystem-snapshots.po
+++ b/locale/zh/LC_MESSAGES/tutorial/backup-sharded-cluster-with-filesystem-snapshots.po
@@ -30,10 +30,6 @@ msgid ""
 "not available. See :doc:`/tutorial/backup-sharded-cluster-with-database-"
 "dumps` for the alternate procedure."
 msgstr ""
-"这篇文档描述了备份集群中所有组件的过程.使用文件系统的快照进行备份,在文件系统"
-"快照不可用时,可以使用 :program:`mongodump` 备份二进制数据.参见 :doc:`/"
-"tutorial/backup-sharded-cluster-with-database-dumps` 获得更多信息."
-
 
 
 #: ../source/includes/note-shard-cluster-backup.rst:1
@@ -73,8 +69,6 @@ msgid ""
 "before taking the filesystem snapshots; otherwise the snapshot will only "
 "approximate a moment in time."
 msgstr ""
-"使用 :program:`mongodump` 备份配置服务器.可以通过任意一个配置服务器的 :"
-"program:`mongod` 或通过 :program:`mongos` 使用 :program:`mongodump` ."
 
 #: ../source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt:65
 msgid "Consistency"
@@ -95,9 +89,6 @@ msgid ""
 "engines. With previous versions of MongoDB, the procedure applied to "
 ":doc:`MMAPv1 </core/mmapv1>` only."
 msgstr ""
-"如果配置服务器使用的MongoDB版本大于等于2.4,可以在运行 :program:`mongodump`  "
-"时添加 :option:`--oplog <mongod --oplog>` 选项,这样可以备份拷贝基础数据期间配"
-"置服务器的增量oplog,比如:"
 
 #: ../source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt:33
 msgid ""
@@ -105,8 +96,6 @@ msgid ""
 "in particular, see :doc:`/core/backups` and :doc:`/administration/backup-"
 "sharded-clusters`."
 msgstr ""
-"备份被锁住的分片,可以并行的对每个分片进行备份.参见 :doc:`/tutorial/backup-"
-"with-filesystem-snapshots` 获得更多信息."
 
 #: ../source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt:41
 msgid "Balancer"
diff --git a/locale/zh/LC_MESSAGES/tutorial/backup-small-sharded-cluster-with-mongodump.po b/locale/zh/LC_MESSAGES/tutorial/backup-small-sharded-cluster-with-mongodump.po
index a95589319a4..8fe8a682606 100644
--- a/locale/zh/LC_MESSAGES/tutorial/backup-small-sharded-cluster-with-mongodump.po
+++ b/locale/zh/LC_MESSAGES/tutorial/backup-small-sharded-cluster-with-mongodump.po
@@ -65,9 +65,6 @@ msgid ""
 "need to capture a backup that reflects a single moment in time, you must "
 "stop all writes to the cluster for the duration of the backup operation."
 msgstr ""
-"在使用 :program:`mongodump` 连接:program:`mongos` 备份数据时不能使用 :option:"
-"`--oplog <mongodump --oplog>` 选项,因此,如果要备份指定时间点的数据,需要在备份"
-"期间停止集群的写入."
 
 #: ../source/tutorial/backup-small-sharded-cluster-with-mongodump.txt:44
 msgid "Procedure"
@@ -83,7 +80,6 @@ msgid ""
 "`mongodump` to a :program:`mongos`. Use the following operation at your "
 "system's prompt:"
 msgstr ""
-"按照以下操作使用 :program:`mongodump` 从 :program:`mongos` 备份集群数据:"
 
 #: ../source/tutorial/backup-small-sharded-cluster-with-mongodump.txt:57
 msgid ""
@@ -106,9 +102,6 @@ msgid ""
 "program:`mongodump` output, these backups contain separate directories for "
 "each database and :term:`BSON` files for each collection in that database."
 msgstr ""
-"使用 :program:`mongodump` 备份的数据不包含数据在源集群的分布,也不包含数据块信"
-"息,备份的数据中每个数据库都是一个单独的目录,目录中每个集合是一个单独的 :term:"
-"`BSON` 文件."
 
 #: ../source/tutorial/backup-small-sharded-cluster-with-mongodump.txt:71
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/backup-with-filesystem-snapshots.po b/locale/zh/LC_MESSAGES/tutorial/backup-with-filesystem-snapshots.po
index 35969c53892..77192b6d4d2 100644
--- a/locale/zh/LC_MESSAGES/tutorial/backup-with-filesystem-snapshots.po
+++ b/locale/zh/LC_MESSAGES/tutorial/backup-with-filesystem-snapshots.po
@@ -62,8 +62,6 @@ msgid ""
 "writes accepted by the database need to be fully written to disk: either to "
 "the :term:`journal` or to data files."
 msgstr ""
-"在快照发生时，必须保证数据库可用。这就意味着所有被数据库接受的写操作都必须全部"
-"写入磁盘，要么是:term:`journal` 或者是数据文件"
 
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:79
@@ -197,8 +195,6 @@ msgid ""
 "snap01``. The location and paths to your systems volume groups and devices may "
 "vary slightly depending on your operating system's :term:`LVM` configuration."
 msgstr ""
-"本例在 ``/dev/vg0/mdb-snap01``路径创建了一个名为``mdb-snap01``的快照。可能位置"
-"路径会有些许不同，这取决于你系统中 :term:`LVM` 的设置"
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:183
 msgid ""
@@ -274,8 +270,6 @@ msgid ""
 "command and compresses the result in a gzipped file in the current working "
 "directory."
 msgstr ""
-"对于整个快照映像执行块级别的拷贝操作，使用 ``dd``命令，并在当前工作目录中的"
-"gzipped文件中保压缩结果"
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:233
 msgid ""
@@ -344,10 +338,6 @@ msgid ""
 "do not need to remove the ``mongod.lock`` file. If you use :method:`db."
 "fsyncLock()` you will need to remove the lock."
 msgstr ""
-"恢复的快照将有一个陈旧的``mongod.lock``文件。如果不从快照中删除该文件，MongoDB"
-"可能会认为陈旧的锁文件显示异常关机。如果在 :setting:`storage.journal.enabled` "
-"启用的情况下，你*不使用* :method:`db.fsyncLock()`方法，那么你并不需要删除"
-"``mongod.lock``文件。如果你使用 :method:`db.fsyncLock()` 方法，你将需要移除锁。"
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:284
 msgid "Restore Directly from a Snapshot"
@@ -357,7 +347,7 @@ msgstr "直接从快照中恢复"
 msgid ""
 "To restore a backup without writing to a compressed ``gz`` file, use the "
 "following sequence of commands:"
-msgstr "使用如下命令，将在恢复时不写入 ``gz``压缩文档"
+msgstr ""
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:297
 msgid "Remote Backup Storage"
@@ -416,15 +406,9 @@ msgstr ""
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:59
 msgid ""
-
 "If all writes are not on disk when the backup occurs, the backup will not "
 "reflect these changes."
-
 msgstr ""
-"如果 :program:`mongod` 实例中日志功能未开启，或者是日志在另外的卷上，获得一致状"
-"态的备份是比较困难的。正如本节所述，你必须刷新所有向硬盘的写操作，并且锁住数据"
-"库来防止在备份过程中的写操作。如果你进行了 :term:`replica set` 配置，然后对你的"
-"备份使用 :term:`secondary`，那么将不会接受读操作(即 :term:`hidden member`)"
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:62
 msgid ""
@@ -437,9 +421,6 @@ msgid ""
 "backup procedure. If you do use journaling, the journal **must** reside on "
 "the same volume as the data."
 msgstr ""
-"MongoDB2.0在 :program:`mongo` shell中增加了 :method:`db.fsyncLock()` 和 :"
-"method:`db.fsyncUnlock()` 。早于该版本的MongoDB，在``lock`` 选项下使用 :"
-"dbcommand:`fsync`命令，如下所示："
 
 #: ../source/tutorial/backup-with-filesystem-snapshots.txt:71
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/convert-sharded-cluster-to-replica-set.po b/locale/zh/LC_MESSAGES/tutorial/convert-sharded-cluster-to-replica-set.po
index 3f65eb8d5db..b9b426471ea 100644
--- a/locale/zh/LC_MESSAGES/tutorial/convert-sharded-cluster-to-replica-set.po
+++ b/locale/zh/LC_MESSAGES/tutorial/convert-sharded-cluster-to-replica-set.po
@@ -53,8 +53,6 @@ msgid ""
 "Optionally remove the :option:`--shardsrv <mongod --shardsvr>` option, if "
 "your :program:`mongod` started with this option."
 msgstr ""
-"如果分片启动时使用了 :option:`--shardsrv <mongod --shardsvr>` 选项,将其移除重"
-"启."
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:0
 msgid "Tip"
@@ -64,7 +62,7 @@ msgstr "注意事项"
 msgid ""
 "The single-shard cluster is now a non-sharded :term:`replica set` that will "
 "accept read and write operations on the data set."
-msgstr "现在单节点的集群已经可以作为复制集进行读写操作了."
+msgstr ""
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:41
 msgid "You may now decommission the remaining sharding infrastructure."
@@ -78,7 +76,7 @@ msgstr "将集群转化为复制集."
 msgid ""
 "Use the following procedure to transition from a :term:`sharded cluster` "
 "with more than one shard to an entirely new :term:`replica set`."
-msgstr "使用以下步骤,将拥有一个以上节点的集群转化为一个全新的复制集."
+msgstr ""
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:49
 msgid ""
@@ -88,9 +86,6 @@ msgid ""
 "current shards combined. Do not configure the application to connect to the "
 "new replica set until the data transfer is complete."
 msgstr ""
-"在集群运行时,参照 :doc:`部署一个新复制集 <deploy-replica-set>` 部署一个新的复"
-"制集,新的复制集必须足够大以容纳集群中所有的数据,在数据转移完成之前,不要将应用"
-"连接到新的复制集上."
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:56
 msgid ""
@@ -101,10 +96,6 @@ msgid ""
 "temporary :program:`mongos` instance on that applications cannot access for "
 "the data migration procedure."
 msgstr ""
-"停止集群所有的写入,你可以重新配置应用不向集群写入数据,也可以停止所有的 :"
-"program:`mongos` , 不过停止所有的mongos之后,应用也不能从集群读取数据.如果你停"
-"止了所有mongos,需要启动一个临时的mongos,这个mongos不能被应用访问到,是用来做数"
-"据迁移的."
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:63
 msgid ""
@@ -112,8 +103,6 @@ msgid ""
 "to migrate the data from the :program:`mongos` instance to the new "
 ":term:`replica set`."
 msgstr ""
-"使用 :doc:`mongodump and mongorestore </tutorial/backup-and-restore-tools/>` 将"
-"数据通过 :program:`mongos` 从集群中迁移到新的复制集中."
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:68
 msgid ""
@@ -128,7 +117,7 @@ msgstr ""
 msgid ""
 "Reconfigure the application to use the non-sharded :term:`replica set` "
 "instead of the :program:`mongos` instance."
-msgstr "重新配置应用,使用未分片的复制集代替 :program:`mongos` ."
+msgstr ""
 
 #: ../source/tutorial/convert-sharded-cluster-to-replica-set.txt:75
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/expand-replica-set.po b/locale/zh/LC_MESSAGES/tutorial/expand-replica-set.po
index 1e17e074c14..8142bce83b5 100644
--- a/locale/zh/LC_MESSAGES/tutorial/expand-replica-set.po
+++ b/locale/zh/LC_MESSAGES/tutorial/expand-replica-set.po
@@ -26,7 +26,7 @@ msgid ""
 "This tutorial explains how to add an additional member to an existing :term:"
 "`replica set`. For background on replication deployment patterns, see the :"
 "doc:`/core/replica-set-architectures` document."
-msgstr "本文描述了如何为已有的 :term:`replica set` 新增节点。有关复制集部署的"
+msgstr ""
 
 #: ../source/tutorial/expand-replica-set.txt:21
 msgid "Maximum Voting Members"
diff --git a/locale/zh/LC_MESSAGES/tutorial/manage-mongodb-processes.po b/locale/zh/LC_MESSAGES/tutorial/manage-mongodb-processes.po
index 7c38ae6c572..b322a3eedc0 100644
--- a/locale/zh/LC_MESSAGES/tutorial/manage-mongodb-processes.po
+++ b/locale/zh/LC_MESSAGES/tutorial/manage-mongodb-processes.po
@@ -78,10 +78,6 @@ msgid ""
 " on permissions, see the :doc:`security operations documentation "
 "</administration/security-checklist>`."
 msgstr ""
-"如果您想将数据文件存储在除 ``/data/db`` 以外的其他路径下，您可以指定一个 :setting:`~storage.dbPath` 。"
-":setting:`~storage.dbPath` 必须在您启动 :program:`mongod` 之前就已存在。如果该目录不存在，创建它之后再赋予足够的权限，"
-"以便于 :program:`mongod` 能在此路径下正常进行读写。更多关于权限的信息，请参阅  :doc:`security operations documentation "
-"</administration/security-checklist>`。"
 
 #: ../source/tutorial/manage-mongodb-processes.txt:57
 msgid ""
@@ -133,7 +129,7 @@ msgid ""
 "--logpath>` options. You must create the log directory; however, "
 ":program:`mongod` will create the log file if it does not exist."
 msgstr ""
-"要运行一个 :program:`mongod` 进程来作为一个守护进程（也就是 :setting:`~processManagement.fork`），*并且*将输出写入到一个日志文件里，"
+"要运行一个 :program:`mongod` 进程来作为一个守护进程（也就是 :setting:`~processManagement.fork`），*并且* 将输出写入到一个日志文件里，"
 "可以使用 :option:`--fork <mongod --fork>` 和  :option:`--logpath <mongod --logpath>` 选项。您必须创建一个log目录；可是，如果这个日志"
 "文件不存在的话，:program:`mongod` 会代劳。"
 
@@ -169,7 +165,8 @@ msgstr "使用 ``shutdownServer()``"
 msgid ""
 "Shut down the :program:`mongod` from the :program:`mongo` shell using the "
 ":method:`db.shutdownServer()` method as follows:"
-msgstr "在 :program:`mongo` shell中使用 :method:`db.shutdownServer()` 方法来关闭:method:`db.shutdownServer()` ，如下所示："
+msgstr ""
+"在 :program:`mongo` shell中使用 :method:`db.shutdownServer()` 方法来关闭  :program:`mongod` ，如下所示："
 
 
 #: ../source/tutorial/manage-mongodb-processes.txt:140
@@ -237,7 +234,7 @@ msgstr "步骤"
 #: ../source/tutorial/manage-mongodb-processes.txt:186
 
 msgid "Check how up-to-date the :term:`secondaries <secondary>` are."
-msgstr "检查当前所有从节点的oplog时间戳。"
+msgstr "检查 :term:`secondaries <secondary>` 的oplog时间戳。"
 
 #: ../source/tutorial/manage-mongodb-processes.txt:188
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/reconfigure-replica-set-with-unavailable-members.po b/locale/zh/LC_MESSAGES/tutorial/reconfigure-replica-set-with-unavailable-members.po
index 67fee88005c..3332abdb338 100644
--- a/locale/zh/LC_MESSAGES/tutorial/reconfigure-replica-set-with-unavailable-members.po
+++ b/locale/zh/LC_MESSAGES/tutorial/reconfigure-replica-set-with-unavailable-members.po
@@ -24,9 +24,6 @@ msgid ""
 "`primary`, following the example in the :ref:`Replica Set Reconfiguration "
 "Procedure <replica-set-reconfiguration-usage>`."
 msgstr ""
-"当复制集中有 **少数** 节点不可用的时候，我们可以在现在的 :term:`primary` 上使"
-"用  :method:`rs.reconfig()`  来进行重新配置，下列就是 :ref:`Replica Set "
-"Reconfiguration Procedure <replica-set-reconfiguration-usage>` 的例子。"
 
 #: ../source/tutorial/reconfigure-replica-set-with-unavailable-members.txt:32
 msgid "Reconfigure by Forcing the Reconfiguration"
@@ -133,8 +130,6 @@ msgid ""
 "majority. See :ref:`replica-set-elections` for more information on this "
 "situation."
 msgstr ""
-"您也许需要使用以下步骤，例如，在一个地理分离的复制集中，*没有* 当地的复制集成员"
-"可以连接到主节点。查阅了解这种情况的更多信息。"
 
 #: ../source/tutorial/reconfigure-replica-set-with-unavailable-members.txt:56
 msgid ""
diff --git a/locale/zh/LC_MESSAGES/tutorial/recover-data-following-unexpected-shutdown.po b/locale/zh/LC_MESSAGES/tutorial/recover-data-following-unexpected-shutdown.po
index a205529fb80..fcfa05ea947 100644
--- a/locale/zh/LC_MESSAGES/tutorial/recover-data-following-unexpected-shutdown.po
+++ b/locale/zh/LC_MESSAGES/tutorial/recover-data-following-unexpected-shutdown.po
@@ -86,10 +86,10 @@ msgid ""
 "allow replication to perform an initial :ref:`sync <replica-set-syncing>` "
 "to restore data."
 msgstr ""
-"在未开启日志的情况下，如果发现 :program:`mongod` 意外停止，并且你也未启用复"
+"在未开启日志的情况下，如果发现 :program:`mongod` 意外停止，**并且** 你也未启用复"
 "制集，在MongoDB重新运行之前需要启动修复程序。如果你已经启用复制集，你需要从"
-"备份中恢复数据并且让复制集进入 :ref:`sync <replica-set-syncing>`状态以恢复数"
-"据"
+"备份中恢复数据并且让复制集进入 :ref:`sync <replica-set-syncing>` 状态以恢复数"
+"据。"
 
 #: ../source/tutorial/recover-data-following-unexpected-shutdown.txt:64
 msgid ""
@@ -247,7 +247,7 @@ msgid ""
 "files, and attempt to recover data from the database; however, it's "
 "impossible to predict the state of the database in these situations."
 msgstr ""
-"通常情况下，你*不能*移除 ``mongod.lock`` 文件，并启动 :program:`mongod` 。请"
+"通常情况下，你 *不能* 移除 ``mongod.lock`` 文件，并启动 :program:`mongod` 。请"
 "考虑上述方法来恢复数据库和移除锁文件。在最差的情况下，你可以移除锁文件，在有"
 "损坏数据的情况下启动数据库，并且试图恢复数据，但是在这种情况下数据库的状态将"
 "会变得不可预测。"