diff --git a/source/core/sharding.txt b/source/core/sharding.txt
index c616f08e66d..68d69476714 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 <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:
@@ -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.