DOCSP-15525 update Manual for mongosh - binary link

Author: andf-mongodb

source/administration/configuration.txt

@@ -235,8 +235,8 @@ among all members of the set. Consider the following:
    replication:
       replSetName: set0
 
-Use descriptive names for sets. Once configured, use the
-:binary:`~bin.mongo` shell to add hosts to the replica set.
+Use descriptive names for sets. Once configured, use
+:mongosh:`mongosh </>` to add hosts to the replica set.
 
 .. seealso::
 

source/administration/monitoring.txt

@@ -499,15 +499,15 @@ has a background :term:`balancer` process that distributes data to ensure that
 chunks are always optimally distributed among the :term:`shards <shard>`.
 
 Issue the :method:`db.printShardingStatus()` or :method:`sh.status()`
-command to the :binary:`~bin.mongos` by way of the :binary:`~bin.mongo`
-shell. This returns an overview of the entire cluster including the
+command to the :binary:`~bin.mongos` from within :mongosh:`mongosh </>`.
+This returns an overview of the entire cluster including the
 database name, and a list of the chunks.
 
 Stale Locks
 ~~~~~~~~~~~
 
 To check the lock status of the database, connect to a
-:binary:`~bin.mongos` instance using the :binary:`~bin.mongo` shell. Issue the
+:binary:`~bin.mongos` instance using :mongosh:`mongosh </>`. Issue the
 following command sequence to switch to the ``config`` database and
 display all outstanding locks on the shard database:
 

source/administration/production-notes.txt

@@ -56,7 +56,7 @@ MongoDB requires the following minimum ``x86_64`` microarchitectures:
 - For AMD ``x86_64``, MongoDB requires *Bulldozer* or later.
 
 Starting in MongoDB 5.0, :binary:`~bin.mongod`, :binary:`~bin.mongos`,
-and the :binary:`~bin.mongo` shell no longer support ``x86_64``
+and the legacy :binary:`~bin.mongo` shell no longer support ``x86_64``
 platforms which do not meet this minimum microarchitecture requirement.
 
 .. include:: /includes/fact-platform-x86_64.rst
@@ -76,7 +76,7 @@ MongoDB on ``arm64`` requires the *ARMv8.2-A* or later
 microarchitecture.
 
 Starting in MongoDB 5.0, :binary:`~bin.mongod`, :binary:`~bin.mongos`,
-and the :binary:`~bin.mongo` shell no longer support ``arm64``
+and the legacy :binary:`~bin.mongo` shell no longer support ``arm64``
 platforms which do not meet this minimum microarchitecture requirement.
 
 .. include:: /includes/fact-platform-arm64.rst

source/appendix/security/appendixA-openssl-ca.txt

@@ -159,7 +159,7 @@ B. Generate the Test CA PEM File
       cat mongodb-test-ca.crt mongodb-test-ia.crt  > test-ca.pem
 
 You can use the :red:`test` PEM file when configuring :binary:`~bin.mongod`,
-:binary:`~bin.mongos`, or :binary:`~bin.mongo` for TLS/SSL :red:`testing`.
+:binary:`~bin.mongos`, or :mongosh:`mongosh </>` for TLS/SSL :red:`testing`.
 
 You can use the :red:`test` intermediate authority to sign the :red:`test`
 certificates for both the server(s) and client(s). A single authority

source/appendix/security/appendixC-openssl-client.txt

@@ -132,9 +132,9 @@ B. Generate the Test PEM File for Client
 
       cat mongodb-test-client.crt mongodb-test-client.key > test-client.pem
 
-   You can use the :red:`test` PEM file to configure the :binary:`~bin.mongo`
-   shell for TLS/SSL :red:`testing`. For example, to connect to a
-   :binary:`~bin.mongod` or a :binary:`~bin.mongos`:
+   You can use the :red:`test` PEM file to configure
+   :mongosh:`mongosh </>` for TLS/SSL :red:`testing`. For example, to
+   connect to a :binary:`~bin.mongod` or a :binary:`~bin.mongos`:
 
    .. example:: 
 
@@ -163,7 +163,7 @@ B. Generate the Test PEM File for Client
          openssl pkcs12 -export -out test-client.pfx -inkey mongodb-test-client.key -in mongodb-test-client.crt -certfile mongodb-test-ia.crt
 
       Once added to Keychain Access, instead of specifying the Certificate Key
-      file, you can use the :option:`--tlsCertificateSelector <mongo
+      file, you can use the :option:`--tlsCertificateSelector <mongosh
       --tlsCertificateSelector>` to specify the certificate to use. If
       the CA file is also in Keychain Access, you can omit
       ``--tlsCAFile`` as well as in the following example:
@@ -174,8 +174,8 @@ B. Generate the Test PEM File for Client
 
          mongo --tls --tlsCertificateSelector subject="<TestClientCertificateCommonName>"
 
-      Although still available, :option:`--ssl <mongo --ssl>` and
-      :option:`--sslCertificateSelector <mongo
+      Although still available, :option:`--ssl <mongosh --ssl>` and
+      :option:`--sslCertificateSelector <mongosh
       --sslCertificateSelector>` are :ref:`deprecated as of MongoDB 4.2
       <4.2-tls>`.
 

source/changeStreams.txt

@@ -69,7 +69,7 @@ You can open change streams against:
 
        The examples on this page use the MongoDB drivers to open and
        work with a change stream cursor for a single collection. See
-       also the :binary:`~bin.mongo` shell method
+       also the :mongosh:`mongosh </>` method
        :method:`db.collection.watch()`.
 
    * - A database
@@ -80,7 +80,7 @@ You can open change streams against:
        collections.
 
        For the MongoDB driver method, refer to your driver
-       documentation. See also the :binary:`~bin.mongo` shell method
+       documentation. See also the :mongosh:`mongosh </>` method
        :method:`db.watch()`.
 
 
@@ -92,7 +92,7 @@ You can open change streams against:
        databases except for ``admin``, ``local``, and ``config``.
 
        For the MongoDB driver method, refer to your driver
-       documentation. See also the :binary:`~bin.mongo` shell method
+       documentation. See also the :mongosh:`mongosh </>` method
        :method:`Mongo.watch()`.
 
 .. note:: Change Stream Examples

source/core/aggregation-pipeline.txt

@@ -49,9 +49,8 @@ exception of :pipeline:`$out`, :pipeline:`$merge`, and
 of all available stages, see
 :ref:`aggregation-pipeline-operator-reference`.
 
-MongoDB provides the :method:`db.collection.aggregate()` method in the
-:binary:`~bin.mongo` shell and the :dbcommand:`aggregate` command to
-run the aggregation pipeline. 
+MongoDB provides the :method:`db.collection.aggregate()` shell method
+and the :dbcommand:`aggregate` command to run the aggregation pipeline. 
 
 For example usage of the aggregation pipeline, consider
 :doc:`/tutorial/aggregation-with-user-preference-data` and

source/core/authentication-mechanisms.txt

@@ -46,7 +46,7 @@ To specify the authentication mechanism to use, set the
 :binary:`~bin.mongos`.
 
 Clients specify the authentication mechanism in the :method:`db.auth()` method.
-For the :binary:`~bin.mongo` shell and the MongoDB tools, you can also specify the
+For :mongosh:`mongosh </>` and the MongoDB tools, you can also specify the
 authentication mechanism from the command line.
 
 .. toctree::

source/core/capped-collections.txt

@@ -144,12 +144,12 @@ Create a Capped Collection
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You must create capped collections explicitly using the
-:method:`db.createCollection()` method, which is a helper in the
-:binary:`~bin.mongo` shell for the :dbcommand:`create` command. When
-creating a capped collection you must specify the maximum size of the
-collection in bytes, which MongoDB will pre-allocate for the collection.
-The size of the capped collection includes a small amount of space for
-internal overhead.
+:method:`db.createCollection()` method, which is a
+:mongosh:`mongosh </>` helper for the :dbcommand:`create` command.
+When creating a capped collection you must specify the maximum size of
+the collection in bytes, which MongoDB will pre-allocate for the
+collection. The size of the capped collection includes a small amount of
+space for internal overhead.
 
 .. code-block:: javascript
 

source/core/databases-and-collections.txt

@@ -21,7 +21,7 @@ gathered together in :term:`collections <collection>`.  A
 Databases
 ---------
 In MongoDB, databases hold one or more collections of documents. To
-select a database to use, in the :binary:`~bin.mongo` shell, issue the
+select a database to use, in :mongosh:`mongosh </>`, issue the
 ``use <db>`` statement, as in the following example:
 
 .. code-block:: javascript
@@ -33,8 +33,8 @@ Create a Database
 
 If a database does not exist, MongoDB creates the database when you
 first store data for that database. As such, you can switch to a
-non-existent database and perform the following operation in the
-:binary:`~bin.mongo` shell:
+non-existent database and perform the following operation in
+:mongosh:`mongosh </>`:
 
 .. code-block:: javascript