DOCSP-26498 - Standardize MongoDB Server Naming (#399)

Author: mongoKart

snooty.toml

@@ -21,7 +21,7 @@ driver-long = "MongoDB Java Driver"
 driver-short = "Java Driver"
 version = "4.9"
 full-version = "{+version+}.1"
-mdb-server = "MongoDB server"
+mdb-server = "MongoDB Server"
 package-name-org = "mongodb-org"
 api = "https://mongodb.github.io/mongo-java-driver/{+version+}"
 stable-api = "Stable API"

source/fundamentals/aggregation-expression-operations.txt

@@ -23,7 +23,7 @@ that is both more compact and more naturally readable.
 The operations in this guide use methods from the
 `com.mongodb.client.model.mql <{+api+}/apidocs/mongodb-driver-core/com/mongodb/client/model/mql/package-summary.html>`__ package.
 These methods provide an idiomatic way to use the Query API,
-the mechanism by which the driver interacts with the {+mdb-server+}. To learn more
+the mechanism by which the driver interacts with a MongoDB deployment. To learn more
 about the Query API, see the :manual:`Server manual documentation </query-api/>`.
 
 How to Use Operations

source/fundamentals/auth.txt

@@ -19,7 +19,7 @@ Overview
 
 In this guide, you can learn how to authenticate with MongoDB using each
 **authentication mechanism** available in the MongoDB Community Edition.
-Authentication mechanisms are processes by which the driver and server
+Authentication mechanisms are processes by which the driver and MongoDB deployment
 confirm identity and establish trust to ensure security.
 
 The mechanisms that you can use with the latest version of MongoDB Community
@@ -51,23 +51,24 @@ Default
 ~~~~~~~
 
 The default authentication mechanism setting uses one of the following
-authentication mechanisms depending on what your MongoDB server supports:
+authentication mechanisms depending on what your version of {+mdb-server+} 
+supports:
 
 #. ``SCRAM-SHA-256``
 #. ``SCRAM-SHA-1``
 #. ``MONGODB-CR``
 
 Server versions 3.6 and earlier use ``MONGODB-CR`` as the default
-mechanism. Newer versions of the server use one of the mechanisms for
+mechanism. Newer versions of {+mdb-server+} use one of the mechanisms for
 which they advertise support.
 
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
 * ``username`` - your MongoDB username
 * ``password`` - your MongoDB user's password
-* ``hostname`` - network address of your MongoDB server, accessible by your client
-* ``port`` - port number of your MongoDB server
+* ``hostname`` - network address of your MongoDB deployment, accessible by your client
+* ``port`` - port number of your MongoDB deployment
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
@@ -102,7 +103,8 @@ mechanism:
 
 For more information on the challenge-response (CR) and salted
 challenge-response authentication mechanisms (SCRAM) that MongoDB supports,
-see the :manual:`SCRAM </core/security-scram/>` section of the server manual.
+see the :manual:`SCRAM </core/security-scram/>` section of the {+mdb-server+}
+manual.
 
 .. _scram-sha-256-auth-mechanism:
 
@@ -123,8 +125,8 @@ using the following placeholders:
 
 * ``username`` - your MongoDB username.
 * ``password`` - your MongoDB user's password.
-* ``hostname`` - network address of your MongoDB server, accessible by your client.
-* ``port`` - port number of your MongoDB server.
+* ``hostname`` - network address of your MongoDB deployment, accessible by your client.
+* ``port`` - port number of your MongoDB deployment.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
@@ -175,8 +177,8 @@ using the following placeholders:
 
 * ``username`` - your MongoDB username.
 * ``password`` - your MongoDB user's password.
-* ``hostname`` - network address of your MongoDB server, accessible by your client.
-* ``port`` - port number of your MongoDB server.
+* ``hostname`` - network address of your MongoDB deployment, accessible by your client.
+* ``port`` - port number of your MongoDB deployment.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
@@ -509,8 +511,8 @@ the subject name of the client certificate.
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
-* ``hostname`` - network address of your MongoDB server, accessible by your client.
-* ``port`` - port number of your MongoDB server.
+* ``hostname`` - network address of your MongoDB deployment, accessible by your client.
+* ``port`` - port number of your MongoDB deployment.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.

source/fundamentals/connection/connect.txt

@@ -97,7 +97,7 @@ method. Chain the ``applyConnectionString()`` method to the builder to specify y
 connection URI.
 
 You can set the {+stable-api+} version client option to avoid
-breaking changes when you upgrade to a new server version. To 
+breaking changes when you upgrade to a new version of {+mdb-server+}. To 
 learn more about the {+stable-api+} feature, see the :ref:`{+stable-api+} page
 <stable-api-java>`.
 
@@ -114,18 +114,18 @@ deployment on Atlas and verify that the connection is successful:
 Other Ways to Connect to MongoDB
 --------------------------------
 
-If you are connecting to a single MongoDB server instance or replica set
+If you are connecting to a single MongoDB deployment or replica set
 that is not hosted on Atlas, see the following sections to find out how to
 connect.
 
 .. _connect-local-java-driver:
 
-Connect to a MongoDB Server on Your Local Machine
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Connect to a MongoDB Deployment on Your Local Machine
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. include:: /includes/fundamentals/localhost-connection.rst
 
-To test whether you can connect to your server, replace the connection
+To test whether you can connect to your deployment, replace the connection
 string in the :ref:`Connect to MongoDB Atlas <connect-atlas-java-driver>` code
 example and run it.
 

source/fundamentals/connection/mongoclientsettings.txt

@@ -234,7 +234,7 @@ settings to modify the driver's behavior:
      - Uses the cluster settings specified in a ``ClusterSettings`` object.
 
    * - ``hosts()``
-     - Sets all the specified locations of a Mongo server.
+     - Sets all the specified locations of a Mongo deployment.
 
    * - ``localThreshold()``
      - | Sets the amount of time that a server’s round trip can take and still
@@ -243,7 +243,7 @@ settings to modify the driver's behavior:
        | **Default**: ``15 milliseconds``
 
    * - ``mode()``
-     - Sets how to connect to a MongoDB server.
+     - Sets how to connect to a MongoDB deployment.
 
    * - ``requiredClusterType()``
      - Sets the type of cluster required for the cluster.
@@ -434,7 +434,7 @@ Server Settings
 
 Chain the `applyToServerSettings() <{+api+}/apidocs/mongodb-driver-core/com/mongodb/MongoClientSettings.Builder.html#applyToServerSettings(com.mongodb.Block)>`__
 method to modify the driver's behavior when monitoring each MongoDB
-server.
+deployment.
 
 The following table describes the methods you can chain to your
 settings to modify the driver's behavior:
@@ -471,7 +471,7 @@ settings to modify the driver's behavior:
 Example
 ~~~~~~~
 
-This example specifies the following driver behavior in a MongoDB server:
+This example specifies the following driver behavior in a MongoDB deployment:
 
 - The minimum interval for server monitoring checks to be at least
   ``700 MILLISECONDS``
@@ -491,7 +491,7 @@ Socket Settings
 
 Chain the `applyToSocketSettings() <{+api+}/apidocs/mongodb-driver-core/com/mongodb/MongoClientSettings.Builder.html#applyToSocketSettings(com.mongodb.Block)>`__
 method to modify the driver's behavior when connecting and communicating
-with your MongoDB server.
+with your MongoDB deployment.
 
 The following table describes the methods you can chain to your settings
 to modify the driver's behavior:

source/fundamentals/connection/tls.txt

@@ -144,7 +144,7 @@ genuine and secure from tampering by third parties.
 
 An application that initiates TLS/SSL requests needs to set two JVM system
 properties to ensure that the client presents a TLS/SSL certificate to
-the MongoDB server:
+the MongoDB deployment:
 
 - ``javax.net.ssl.keyStore``: the path to a key store containing the client's
   TLS/SSL certificates

source/fundamentals/crud/read-operations/change-streams.txt

@@ -46,7 +46,7 @@ To open a change stream, call the ``watch()`` method on an instance of a
 
    Standalone MongoDB deployments don't support change streams because
    the feature requires a replica set oplog. To learn more about the oplog,
-   see the :ref:`<replica-set-oplog>` server manual page.
+   see the :ref:`<replica-set-oplog>` {+mdb-server+} manual page.
 
 The object on which you call the ``watch()`` method on determines the scope of
 events that the change stream listens for.
@@ -151,7 +151,7 @@ must connect to a MongoDB v6.0 or later deployment and set up the following:
 
      To learn how to enable these on your deployment, see the
      :manual:`Change Streams with Document Pre- and Post-Images </changeStreams/#change-streams-with-document-pre--and-post-images>`
-     MongoDB server manual page.
+     {+mdb-server+} manual page.
 
      To learn how to instruct the driver to create a collection with pre-images
      and post-images enabled, see the :ref:`<java-change-stream-pre-post-collection>`
@@ -186,7 +186,7 @@ and call the ``createCollection()`` method as shown in the following example:
 You can change the pre-image and post-image option in an existing collection
 by running the ``collMod`` command from the MongoDB Shell. To learn how to
 perform this operation, see the :manual:`collMod </reference/command/collMod#change-streams-with-document-pre--and-post-images>`
-server manual documentation.
+{+mdb-server+} manual.
 
 .. warning::
 
@@ -211,7 +211,7 @@ include the pre-image and output the results:
 The preceding example configures the change stream to use the
 ``FullDocumentBeforeChange.REQUIRED`` option. This configures the change
 stream to return pre-images for replace, update, and delete change events and
-for the server to raise an error if the pre-image is unavailable.
+for the MongoDB deployment to raise an error if the pre-image is unavailable.
 
 Suppose an application updated the ``latestVersion`` field of a document in a
 collection of software library dependencies from the value of ``2.0.0`` to

source/fundamentals/crud/read-operations/cursor.txt

@@ -41,7 +41,7 @@ to see by setting parameters through methods.
 Terminal Methods
 ----------------
 
-Terminal methods execute an operation on the MongoDB server after
+Terminal methods execute an operation on the MongoDB deployment after
 configuring all parameters of an ``Iterable`` instance controlling the
 operation.
 
@@ -212,9 +212,9 @@ Cursor Cleanup
 Close
 ~~~~~
 
-Use the ``close()`` method in a finally block to free up a cursor's
+Use the ``close()`` method in a ``finally`` block to free up a cursor's
 consumption of resources in both the client application and the MongoDB
-server:
+deployment:
 
 .. literalinclude:: /includes/fundamentals/code-snippets/Cursor.java
    :language: java
@@ -227,7 +227,7 @@ Try with Resources Statement
 
 Use a try-with-resources statement
 to automatically free up a cursor's consumption of resources in both the
-client application and the MongoDB server:
+client application and the MongoDB deployment:
 
 .. literalinclude:: /includes/fundamentals/code-snippets/Cursor.java
    :language: java

source/fundamentals/crud/read-operations/geo.txt

@@ -134,7 +134,7 @@ For more information on the ``Indexes`` builder, see our
 :doc:`guide on the Indexes builder </fundamentals/builders/indexes>`. 
 
 For more information on legacy coordinate pairs, see the
-:manual:`MongoDB server manual page on legacy coordinate pairs </geospatial-queries/#legacy-coordinate-pairs>`.
+:manual:`{+mdb-server+} manual page on legacy coordinate pairs </geospatial-queries/#legacy-coordinate-pairs>`.
 
 .. external resource
 
@@ -301,6 +301,6 @@ For more information on the ``$geoWithin`` operator, see the
 .. external resource
 
 For more information on the operators you can use in your query, see the
-:manual:`MongoDB server manual page on geospatial query operators </geospatial-queries/index.html>`
+:manual:`{+mdb-server+} manual page on geospatial query operators </geospatial-queries/index.html>`
 
 .. external resource

source/fundamentals/crud/read-operations/retrieve.txt

@@ -134,7 +134,7 @@ After the owner runs the aggregation, they find that "green" is the most
 purchased color.
 
 For more information on how to construct an aggregation pipeline, see
-the MongoDB server manual page on :manual:`Aggregation </aggregation>`.
+the {+mdb-server+} manual page on :manual:`Aggregation </aggregation>`.
 
 For additional information on the methods mentioned on this page, see
 the following API Documentation: