From a7cbb4ab6e43827348fa857849a0f356905ce4ca Mon Sep 17 00:00:00 2001 From: Bob Grabar Date: Fri, 5 Oct 2012 17:49:50 -0400 Subject: [PATCH 1/2] formatting typo that affects meaning --- source/core/sharding.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/core/sharding.txt b/source/core/sharding.txt index c616f08e66d..d678ac28553 100644 --- a/source/core/sharding.txt +++ b/source/core/sharding.txt @@ -520,8 +520,8 @@ Security To control access to a shard cluster, you must set the :setting:`keyFile` option on all components of the shard cluster. Use -the :option:`--keyFile ` run-time option or :the -setting:`keyFile` configuration option for all :program:`mongos`, +the :option:`--keyFile ` run-time option or the +:setting:`keyFile` configuration option for all :program:`mongos`, configuration instances, and shard :program:`mongod` instances. There are two classes of security credentials in a shard cluster: From 7fea5c65e53ea11e5095ae9e9e53b96e01f5160b Mon Sep 17 00:00:00 2001 From: Bob Grabar Date: Fri, 5 Oct 2012 17:54:43 -0400 Subject: [PATCH 2/2] type --- source/core/sharding.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/core/sharding.txt b/source/core/sharding.txt index d678ac28553..68d69476714 100644 --- a/source/core/sharding.txt +++ b/source/core/sharding.txt @@ -546,6 +546,6 @@ the database should use a :program:`mongos` instance. Individual shards can store administrative credentials to their instance, which only permit access to a single shard. MongoDB - stores these credentials in the shards' :term:`admin database`\s and these + stores these credentials in the shards' :term:`admin databases ` and these credentials are *completely* distinct from the cluster-wide administrative credentials.