Skip to content

formatting typo that affects meaning #291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 9, 2012
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/core/sharding.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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 <mongos --keyFile>` run-time option or :the
setting:`keyFile` configuration option for all :program:`mongos`,
the :option:`--keyFile <mongos --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:
Expand All @@ -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 <admin database>` and these
credentials are *completely* distinct from the cluster-wide
administrative credentials.