Skip to content

Commit 742aa38

Browse files
author
Sam Kleinman
committed
DOCS-1007 minor correction/clarification
1 parent 273c0b6 commit 742aa38

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/administration/sharded-clusters.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -326,14 +326,14 @@ different locations within the cluster and have different roles:
326326
database.
327327

328328
This means that you *can* authenticate to these users and databases
329-
while connected directly to the primary shard for a database. However,
329+
while connected directly to the *primary* shard for a database. However,
330330
for clarity and consistency all interactions between the client and
331331
the database should use a :program:`mongos` instance.
332332

333333
.. note::
334334

335335
Individual shards can store administrative credentials to their
336336
instance, which only permit access to a single shard. MongoDB
337-
stores these credentials in the shards' :term:`admin databases <admin database>` and these
338-
credentials are *completely* distinct from the cluster-wide
339-
administrative credentials.
337+
stores these credentials in the shards' :term:`admin databases
338+
<admin database>` and these credentials are *completely* distinct
339+
from the cluster-wide administrative credentials.

0 commit comments

Comments
 (0)