File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -250,7 +250,7 @@ The ideal shard key:
250
250
251
251
- is easily divisible which makes it easy for MongoDB to distribute
252
252
content among the shards. Shard keys that have a limited number of
253
- possible values are un- ideal, as they can result in some chunks that
253
+ possible values are not ideal as they can result in some chunks that
254
254
are "un-splitable." See the ":ref:`sharding-shard-key-cardinality`"
255
255
section for more information.
256
256
@@ -327,7 +327,7 @@ up time is not required for a functioning shard cluster. As a result,
327
327
backing up the config servers is not difficult. Backups of config
328
328
servers are crucial as shard clusters become totally inoperable when
329
329
you loose all configuration instances and data. Precautions to ensure
330
- that the config servers remain available and intact are critial .
330
+ that the config servers remain available and intact are critical .
331
331
332
332
.. index:: mongos
333
333
.. _sharding-mongos:
@@ -403,7 +403,7 @@ possible. Operations have the following targeting characteristics:
403
403
- All single :func:`update() <db.collection.update()>` operations
404
404
target to one shard. This includes :term:`upsert` operations.
405
405
406
- - The :program:`mongos` brodcasts multi-update operations to every
406
+ - The :program:`mongos` broadcasts multi-update operations to every
407
407
shard.
408
408
409
409
- The :program:`mongos` broadcasts :func:`remove()
You can’t perform that action at this time.
0 commit comments