DOCSP-17535 revert mongosh options links

Author: andf-mongodb

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

@@ -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 <mongosh
+      file, you can use the :option:`--tlsCertificateSelector <mongo
       --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
 
          mongosh --tls --tlsCertificateSelector subject="<TestClientCertificateCommonName>"
 
-      Although still available, :option:`--ssl <mongosh --ssl>` and
-      :option:`--sslCertificateSelector <mongosh
+      Although still available, :option:`--ssl <mongo --ssl>` and
+      :option:`--sslCertificateSelector <mongo
       --sslCertificateSelector>` are :ref:`deprecated as of MongoDB 4.2
       <4.2-tls>`.
 

source/core/retryable-writes.txt

@@ -75,7 +75,7 @@ MongoDB Drivers
 
 :mongosh:`mongosh </>`
   To enable retryable writes in :mongosh:`mongosh </>`, use
-  the :option:`--retryWrites <mongosh --retryWrites>` command line option:
+  the :option:`--retryWrites <mongo --retryWrites>` command line option:
 
   .. code-block:: bash
 

source/core/security-ldap-external.txt

@@ -405,9 +405,9 @@ Connecting to a MongoDB server using LDAP Authorization
 When using LDAP for authorization, users connecting via
 :mongosh:`mongosh </>` must:
 
-- set :option:`--authenticationDatabase <mongosh --authenticationDatabase>` to ``$external``.
+- set :option:`--authenticationDatabase <mongo --authenticationDatabase>` to ``$external``.
 
-- set :option:`--authenticationMechanism <mongosh --authenticationMechanism>` to the appropriate authentication
+- set :option:`--authenticationMechanism <mongo --authenticationMechanism>` to the appropriate authentication
   mechanism.
 
   If using :ref:`LDAP authentication <security-ldap>`, set this to ``PLAIN``.
@@ -417,13 +417,13 @@ When using LDAP for authorization, users connecting via
 
   If using :ref:`x.509 <security-auth-x509>`, set this to ``MONGODB-X.509``.
 
-- set :option:`--username <mongosh --username>` to a username that respects the
+- set :option:`--username <mongo --username>` to a username that respects the
   :setting:`security.ldap.authz.queryTemplate`, or any configured
   :setting:`security.ldap.userToDNMapping` template.
 
-- set :option:`--password <mongosh --password>` to the appropriate password.
+- set :option:`--password <mongo --password>` to the appropriate password.
 
-Include the :option:`--host <mongosh --host>` and :option:`--port <mongosh --port>` of the MongoDB server,
+Include the :option:`--host <mongo --host>` and :option:`--port <mongo --port>` of the MongoDB server,
 along with any other options relevant to your deployment.
 
 For example, the following operation authenticates to a MongoDB server running

source/core/security-x.509.txt

@@ -65,36 +65,36 @@ To connect and authenticate using x.509 client certificate:
 
 - For MongoDB 4.2 or greater, include the following options for the client:
 
-  - :option:`--tls <mongosh --tls>` (or the deprecated :option:`--ssl
-    <mongosh --ssl>` option)
+  - :option:`--tls <mongo --tls>` (or the deprecated :option:`--ssl
+    <mongo --ssl>` option)
 
-  - :option:`--tlsCertificateKeyFile <mongosh --tlsCertificateKeyFile>`
+  - :option:`--tlsCertificateKeyFile <mongo --tlsCertificateKeyFile>`
     (or the deprecated :option:`--sslPEMKeyFile 
-    <mongosh --sslPEMKeyFile>` option)
+    <mongo --sslPEMKeyFile>` option)
 
-  - :option:`--tlsCertificateKeyFilePassword <mongosh --tlsCertificateKeyFile>`
+  - :option:`--tlsCertificateKeyFilePassword <mongo --tlsCertificateKeyFile>`
     (or the deprecated :option:`--sslPEMKeyPassword 
-    <mongosh --sslPEMKeyPassword>` option) if the certificate key file is encrypted
+    <mongo --sslPEMKeyPassword>` option) if the certificate key file is encrypted
 
   - :option:`--authenticationDatabase '$external' 
-    <mongosh --authenticationDatabase>`
+    <mongo --authenticationDatabase>`
 
   - :option:`--authenticationMechanism MONGODB-X509 
-    <mongosh --authenticationMechanism>`
+    <mongo --authenticationMechanism>`
 
 - For MongoDB 4.0 and earlier, include the following options for the client:
 
-  - :option:`--ssl <mongosh --ssl>`
+  - :option:`--ssl <mongo --ssl>`
 
-  - :option:`--sslPEMKeyFile <mongosh --sslPEMKeyFile>`
+  - :option:`--sslPEMKeyFile <mongo --sslPEMKeyFile>`
 
-  - :option:`--sslPEMKeyPassword <mongosh --sslPEMKeyPassword>` option if
-    the :option:`--sslPEMKeyFile <mongosh --sslPEMKeyFile>` is encrypted.
+  - :option:`--sslPEMKeyPassword <mongo --sslPEMKeyPassword>` option if
+    the :option:`--sslPEMKeyFile <mongo --sslPEMKeyFile>` is encrypted.
 
   - :option:`--authenticationDatabase '$external' 
-    <mongosh --authenticationDatabase>`
+    <mongo --authenticationDatabase>`
 
-  - :option:`--authenticationMechanism MONGODB-X509 <mongosh --authenticationMechanism>`
+  - :option:`--authenticationMechanism MONGODB-X509 <mongo --authenticationMechanism>`
 
 You can also make the TLS/SSL connection first, and then use
 :method:`db.auth()` in the ``$external`` database to authenticate.

source/core/sharded-cluster-query-router.txt

@@ -346,9 +346,9 @@ server>`, with the :option:`--auth <mongod --auth>` option in order to enforce R
 Alternatively, enforcing :doc:`/core/security-internal-authentication` for
 inter-cluster security also enables user access controls via RBAC.
 
-With RBAC enforced, clients must specify a :option:`--username <mongosh --username>`,
-:option:`--password <mongosh --password>`, and
-:option:`--authenticationDatabase <mongosh --authenticationDatabase>` when
+With RBAC enforced, clients must specify a :option:`--username <mongo --username>`,
+:option:`--password <mongo --password>`, and
+:option:`--authenticationDatabase <mongo --authenticationDatabase>` when
 connecting to the :binary:`~bin.mongos` in order to access cluster resources.
 
 Each cluster has its own cluster users. These users cannot be used

source/includes/extracts-ssl-facts.yaml

@@ -82,7 +82,7 @@ ref: ssl-facts-mongo-ssl-hostname-verification
 content: |
 
    :mongosh:`mongosh </>` verifies that the hostname (specified
-   in :option:`--host <mongosh --host>` option or the connection string)
+   in :option:`--host <mongo --host>` option or the connection string)
    matches the ``SAN`` (or, if ``SAN`` is not present, the ``CN``) in
    the certificate presented by the :binary:`~bin.mongod` or
    :binary:`~bin.mongos`. If ``SAN`` is present, :mongosh:`mongosh </>`

source/includes/fact-authenticate.rst

@@ -5,9 +5,9 @@ associated with that user.
 To authenticate using :mongosh:`mongosh </>`, either:
 
 - Use the :mongosh:`mongosh </>` command-line authentication options
-  (:option:`--username <mongosh --username>`,
-  :option:`--password <mongosh --password>`, and
-  :option:`--authenticationDatabase <mongosh --authenticationDatabase>`)
+  (:option:`--username <mongo --username>`,
+  :option:`--password <mongo --password>`, and
+  :option:`--authenticationDatabase <mongo --authenticationDatabase>`)
   when connecting to the :binary:`~bin.mongod` or
   :binary:`~bin.mongos` instance, or
 

source/includes/steps-authenticate-as-client.yaml

@@ -5,7 +5,7 @@ action:
   pre: |
     When using :mongosh:`mongosh </>` to connect to a :binary:`~bin.mongod` or
     :binary:`~bin.mongos`, enter your ``username``, ``password``, and
-    :option:`authenticationDatabase <mongosh --authenticationDatabase>`. For
+    :option:`authenticationDatabase <mongo --authenticationDatabase>`. For
     example:
   language: javascript
   code: |

source/includes/steps-change-own-password-and-custom-data-prereq.yaml

@@ -11,7 +11,7 @@ action:
   code: |
      mongosh --port 27017 -u myUserAdmin -p  --authenticationDatabase 'admin'
   post: |
-     If you do not specify the password to the :option:`-p <mongosh -p>`
+     If you do not specify the password to the :option:`-p <mongo -p>`
      command-line option, :mongosh:`mongosh </>` prompts for the
      password.
 ---

source/includes/steps-change-own-password-and-custom-data.yaml

@@ -14,7 +14,7 @@ action:
     mongosh --port 27017 -u user123 --authenticationDatabase 'test' -p
 post: |
   
-  If you do not specify the password to the :option:`-p <mongosh -p>`
+  If you do not specify the password to the :option:`-p <mongo -p>`
   command-line option, :mongosh:`mongosh </>` prompts for the
   password.