Skip to content

Commit b8796ac

Browse files
committed
Additional minor fixes and updates to sharding draft
1 parent 4c26eca commit b8796ac

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

draft/core/sharding.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -250,7 +250,7 @@ The ideal shard key:
250250

251251
- is easily divisible which makes it easy for MongoDB to distribute
252252
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
254254
are "un-splitable." See the ":ref:`sharding-shard-key-cardinality`"
255255
section for more information.
256256

@@ -327,7 +327,7 @@ up time is not required for a functioning shard cluster. As a result,
327327
backing up the config servers is not difficult. Backups of config
328328
servers are crucial as shard clusters become totally inoperable when
329329
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.
331331

332332
.. index:: mongos
333333
.. _sharding-mongos:
@@ -403,7 +403,7 @@ possible. Operations have the following targeting characteristics:
403403
- All single :func:`update() <db.collection.update()>` operations
404404
target to one shard. This includes :term:`upsert` operations.
405405

406-
- The :program:`mongos` brodcasts multi-update operations to every
406+
- The :program:`mongos` broadcasts multi-update operations to every
407407
shard.
408408

409409
- The :program:`mongos` broadcasts :func:`remove()

0 commit comments

Comments
 (0)