[Kafka] Terminology update - use MongoDB cluster instead of server (#150)

* change MongoDB server mentions to MongoDB cluster using a constant

Author: rachel-mack

snooty.toml

@@ -45,3 +45,4 @@ mongodb-port-mapping="35001"
 jmx-port-mapping="35000"
 sandbox-directory="kafka-edu/docs-examples/mongodb-kafka-base/"
 win-sandbox-directory="kafka-edu\\docs-examples\\mongodb-kafka-base\\"
+cluster = "MongoDB cluster"

source/compatibility.txt

@@ -4,6 +4,13 @@
 Compatibility
 =============
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: version, backwards, conflict, platforms
+
 MongoDB Compatibility
 ---------------------
 

source/facets.toml

@@ -0,0 +1,3 @@
+[[facets]]
+category = "target_product"
+value = "kafka-connector"

source/monitoring.txt

@@ -4,6 +4,13 @@
 Monitoring
 ==========
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: logging, audit, metrics
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -509,11 +516,11 @@ Sink Connector JMX Metrics
 
    * - **batch-writes-successful**
      - The total number of batches a MongoDB sink task successfully wrote
-       to the MongoDB server.
+       to the {+cluster+}.
 
    * - **batch-writes-successful-duration-ms**
      - The total number of milliseconds a MongoDB sink task spent successfully
-       writing to the MongoDB server.
+       writing to the {+cluster+}.
 
    * - **batch-writes-successful-duration-over-1-ms**
      - The total number of successful batch writes performed by the MongoDB
@@ -537,11 +544,11 @@ Sink Connector JMX Metrics
 
    * - **batch-writes-failed**
      - The total number of batches a MongoDB sink task failed to write
-       to the MongoDB server.
+       to the {+cluster+}.
 
    * - **batch-writes-failed-duration-ms**
      - The total number of milliseconds a MongoDB sink task spent
-       unsuccessfully attempting to write batches to the MongoDB server.
+       unsuccessfully attempting to write batches to the {+cluster+}.
 
    * - **batch-writes-failed-duration-over-1-ms**
      - The total number of failed batch writes attempted by the MongoDB
@@ -603,7 +610,7 @@ Source Connector JMX Metrics
 
    * - **mongodb-bytes-read**
      - The total number of bytes a MongoDB source task read from the
-       MongoDB server.
+       {+cluster+}.
 
        .. _kafka-monitoring-averge-record-size-span:      
 
@@ -621,7 +628,7 @@ Source Connector JMX Metrics
 
    * - **latest-mongodb-time-difference-secs**
      - The number of seconds of the most recent time difference recorded between
-       a MongoDB server and the post-batch resume token held by a MongoDB
+       a {+cluster+} and the post-batch resume token held by a MongoDB
        source task. This value is calculated by subtracting the timestamp
        of the task's post-batch resume token from the ``operationTime`` value of
        the most recent successful MongoDB command executed by the task.
@@ -688,7 +695,7 @@ Source Connector JMX Metrics
    * - **initial-commands-successful**
      - The total number of initial commands issued by a MongoDB source
        task that succeeded. An initial command is a find or aggregate command
-       sent to a MongoDB server that retrieves the first set of documents in a
+       sent to a {+cluster+} that retrieves the first set of documents in a
        cursor. A ``getMore`` command is not an initial command.
 
    * - **initial-commands-successful-duration-ms**
@@ -746,7 +753,7 @@ Source Connector JMX Metrics
    * - **initial-commands-failed**
      - The total number of initial commands issued by a MongoDB source
        task that failed. An initial command is a find or aggregate command
-       sent to a MongoDB server that retrieves the first set of documents in a
+       sent to a {+cluster+} that retrieves the first set of documents in a
        cursor. A ``getMore`` command is not an initial command.
 
    * - **initial-commands-failed-duration-ms**

source/security-and-authentication/mongodb-aws-auth.txt

@@ -4,6 +4,13 @@
 MongoDB AWS-based Authentication
 ================================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: AWS, IAM, credentials
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -24,8 +31,8 @@ AWS IAM credentials, see the guide on :atlas:`How to Set Up Unified AWS Access <
 
 .. important::
 
-   You must use {+connector+} version 1.5 of later to connect to a MongoDB
-   server set up to authenticate using your AWS IAM credentials. AWS IAM
+   You must use {+connector+} version 1.5 of later to connect to a {+cluster+}
+   set up to authenticate using your AWS IAM credentials. AWS IAM
    credential authentication is available in MongoDB server version 4.4
    and later.
 

source/sink-connector/configuration-properties/time-series.txt

@@ -4,6 +4,10 @@
 Kafka Time Series Properties
 ============================
 
+.. facet::
+   :name: genre
+   :values: reference
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -137,7 +141,7 @@ Settings
        | **Description:**
        | The expected interval between subsequent measurements of your
          source data. For more information on this setting, see the
-         MongoDB Server Manual page on :manual:`Granularity for Time
+         MongoDB server manual page on :manual:`Granularity for Time
          Series Data </core/timeseries/timeseries-granularity/>`.
        |
        | *Optional*

source/source-connector/configuration-properties/mongodb-connection.txt

@@ -4,6 +4,13 @@
 MongoDB Source Connection Properties
 ====================================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: communicate
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -81,7 +88,7 @@ Settings
        | **Description:**
        | The {+stable-api+} version you want to use with your MongoDB
          cluster. For more information on the {+stable-api+} and versions of
-         MongoDB Server that support it, see the :manual:`{+stable-api+} </reference/stable-api/>`
+         MongoDB server that support it, see the :manual:`{+stable-api+} </reference/stable-api/>`
          guide.
        |
        | **Default**: ``""``

source/source-connector/usage-examples/custom-pipeline.txt

@@ -4,6 +4,13 @@
 Customize a Pipeline to Filter Change Events
 ============================================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: code example, aggregate, publishing
+
 This usage example demonstrates how to configure a **pipeline** to
 customize the data that your {+source-connector+} consumes. A pipeline is a
 MongoDB aggregation pipeline composed of instructions to the database to
@@ -12,7 +19,7 @@ filter or transform data.
 MongoDB notifies the connector of data changes that match your aggregation
 pipeline on a **change stream**. A change stream is a sequence of events that
 describe data changes a client made to a MongoDB deployment in real-time.
-For more information, see the MongoDB Server manual entry on
+For more information, see the MongoDB server manual entry on
 :manual:`Change Streams </changeStreams/>`.
 
 

source/tutorials/facets.toml

@@ -0,0 +1,4 @@
+
+[[facets]]
+category = "genre"
+value = "tutorial"

source/tutorials/tutorial-setup.txt

@@ -4,6 +4,9 @@
 Kafka Connector Tutorial Setup
 ==============================
 
+.. meta:: 
+   :keywords: environment, ports
+
 The tutorials in this section run on a development environment using Docker to
 package the dependencies and configurations required to run the
 {+connector-long+}. Make sure you complete the development environment setup
@@ -122,7 +125,7 @@ Set Up Your Development Environment with Docker
 
       .. tip:: Connect To Development Environment MongoDB
 
-         You can connect to the MongoDB server running in your
+         You can connect to the {+cluster+} running in your
          development environment with the following connection string:
 
          .. code-block:: text