Fixed the apostrophes in all new constants (#1741) (#1761)

davidhou17 · euniceadam-mdb · web-flow · commit 1e83f3e895c2 · 2024-06-27T08:55:20.000-07:00
Co-authored-by: euniceadam-mdb &lt;eunice.adam@mongodb.com&gt;
diff --git a/source/includes/facts/fact-om-in-multi-clusters-summary-of-diffs.rst b/source/includes/facts/fact-om-in-multi-clusters-summary-of-diffs.rst
@@ -25,7 +25,7 @@ These procedures are the same as the procedures for deploying |onprem| in single
 
   You can choose to deploy |onprem| on the central cluster and the Application
   Database on a subset of selected member clusters, to increase the
-  {+appdb+}'s resilience and availability in |onprem|. Configure
+  {+appdb+}\'s resilience and availability in |onprem|. Configure
   the following settings in the |onprem| CRD:
 
   - Use :opsmgrkube:`topology <spec.applicationDatabase.topology>` to specify the ``MultiCluster`` value.
diff --git a/source/includes/setting-k8sRsConf-spec.security.authentication.agents.clientCertificateSecretRef.name.rst b/source/includes/setting-k8sRsConf-spec.security.authentication.agents.clientCertificateSecretRef.name.rst
@@ -3,7 +3,7 @@
    *Type*: string
 
    
-   Specifies the |k8s-secret| that contains the {+mdbagent+}'s
+   Specifies the |k8s-secret| that contains the {+mdbagent+}\'s
    |tls| certificate. If omitted, defaults to ``agent-certs``.
    
    This secret must contain the following keys, the 
diff --git a/source/includes/steps-deploy-k8s-om-multi-https.rst b/source/includes/steps-deploy-k8s-om-multi-https.rst
@@ -373,11 +373,11 @@
    d. Deploy |onprem|. The |k8s-op-short| deploys |onprem| by performing
       the following steps. It:
 
-      - Deploys the {+appdb+}'s replica set nodes and waits
+      - Deploys the {+appdb+}\'s replica set nodes and waits
         for the MongoDB processes in the replica set to start running.
-      - Deploys the |application| instance with the {+appdb+}'s
+      - Deploys the |application| instance with the {+appdb+}\'s
         connection string and waits for it to become ready.
-      - Adds the Monitoring {+mdbagent+} containers to each {+appdb+}'s Pod.
+      - Adds the Monitoring {+mdbagent+} containers to each {+appdb+}\'s Pod.
       - Waits for both the |application| and the {+appdb+} Pods to start running.
 
       .. io-code-block::
diff --git a/source/includes/steps-deploy-k8s-opsmgr-local-mode.yaml b/source/includes/steps-deploy-k8s-opsmgr-local-mode.yaml
@@ -65,7 +65,7 @@ content: |
     :opsmgrkube:`spec.configuration` to enable Local Mode.
 
   - Define a |k8s-pv| for the |onprem| StatefulSet to store the 
-    MongoDB installation archive. {+mdbagent+}\s running in MongoDB
+    MongoDB installation archive. {+mdbagent+}\'s running in MongoDB
     database resource containers that you create with the |k8s-op-short|
     download the installation archives from |onprem| instead of from the
     Internet.
@@ -361,7 +361,7 @@ content: |
         the secret you created that contains an |onprem| programmatic 
         API key pair.
 
-  {+mdbagent+}\s run in MongoDB database resource containers that
+  {+mdbagent+}\'s run in MongoDB database resource containers that
   you create with the |k8s-op-short|. Download the installation archives
   from |onprem| instead of downloading them from the Internet.
 
diff --git a/source/includes/steps-deploy-k8s-opsmgr-remote-mode.yaml b/source/includes/steps-deploy-k8s-opsmgr-remote-mode.yaml
@@ -335,7 +335,7 @@ content: |
         the secret you created that contains an |onprem| programmatic 
         API key pair.
 
-  {+mdbagent+}\s running in MongoDB database resource containers that
+  {+mdbagent+}\'s running in MongoDB database resource containers that
   you create with the |k8s-op-short| download the installation archives
   from |onprem| via Nginx instead of from the Internet. 
 
diff --git a/source/includes/steps-openshift-airgapped-env-tutorial.yaml b/source/includes/steps-openshift-airgapped-env-tutorial.yaml
@@ -91,7 +91,7 @@ content: |
        :opsmgrkube:`spec.configuration` to enable Local Mode.
 
      - Define a |k8s-pv| for the |onprem| StatefulSet to store the 
-       MongoDB installation archive. {+mdbagent+}\s running in MongoDB
+       MongoDB installation archive. {+mdbagent+}\'s running in MongoDB
        database resource containers that you create with the |k8s-op-short|
        download the installation archives from |onprem| instead of from the
        Internet.
diff --git a/source/includes/steps-source-deploy-om-resource.yaml b/source/includes/steps-source-deploy-om-resource.yaml
@@ -6,7 +6,7 @@ title: "Create a secret with your {+appdb+} |tls| certificate."
 content: |
 
   Run this ``kubectl`` command to create a new |k8s-secret| that stores
-  the {+appdb+}'s |tls| certificate:
+  the {+appdb+}\'s |tls| certificate:
 
   .. code-block:: sh
 
diff --git a/source/om-resources.txt b/source/om-resources.txt
@@ -53,7 +53,7 @@ Deploy Ops Manager Resources on Kubernetes Clusters
 :ref:`disaster-recovery-om-appdb`
   Manually recover the |k8s-op-short|, the |application|, and the {+appdb+}
   in cases when the |k8s| cluster hosting the |k8s-op-short| fails, or when
-  the {+appdb+}'s replica set loses node majority to elect a primary.
+  the {+appdb+}\'s replica set loses node majority to elect a primary.
 
 .. toctree::
    :titlesonly:
diff --git a/source/reference/k8s-operator-crd-logging-specification.txt b/source/reference/k8s-operator-crd-logging-specification.txt
@@ -40,7 +40,7 @@ Example Manifest
 .. literalinclude:: /includes/code-examples/yaml-files/example-mongodb-logging-config.yaml
     :language: yaml
 
-Application Database Log Rotation
+{+appdb+} Log Rotation
 ---------------------------------
 You can configure the following log's rotation in the ``MongoDBOpsManager`` |crd|, 
 as shown in the following example manifest. See the preceding table for more 
diff --git a/source/reference/k8s-operator-multi-cluster-specification.txt b/source/reference/k8s-operator-multi-cluster-specification.txt
@@ -786,7 +786,7 @@ Optional ``MongoDBMultiCluster`` Resource Settings
 
   *Default*: agent-certs
 
-  Specifies the |k8s-secret| that contains the {+mdbagent+}'s
+  Specifies the |k8s-secret| that contains the {+mdbagent+}\'s
   |tls| certificate.
  
   This secret must contain the following keys, the 
diff --git a/source/reference/k8s-operator-om-specification.txt b/source/reference/k8s-operator-om-specification.txt
@@ -155,7 +155,7 @@ resources.
 
    - When you configure external access to the |onprem| instance on an external
      domain, you can specify a custom URL.
-     This also requires the |k8s-op-short| and the {+appdb+}'s
+     This also requires the |k8s-op-short| and the {+appdb+}\'s
      {+monitoring-agent+}s to use this custom URL instead of the default one.
 
 .. opsmgrkube:: spec.clusterDomain
@@ -1267,7 +1267,7 @@ You can use |tls| for both |s3| and your application database, or for
    :opsmgrkube:`spec.backup.s3Stores.customCertificateSecretRefs`
    instead. 
    
-   Flag that indicates whether you use {+appdb+}'s certificates
+   Flag that indicates whether you use {+appdb+}\'s certificates
    (``appdb-ca``) as the custom |tls| certificate for your |s3| backups.
    The default is ``False``. 
 
@@ -1463,7 +1463,7 @@ You can use |tls| for both |s3| and your application database, or for
    Don't use this field with |aws| |s3| buckets. For more information, see 
    :opsmgr:`S3 Blockstore Configuration </reference/api/admin/backup/snapshot/s3Configs/create-one-s3-blockstore-configuration/>`.
 
-Application Database Required Settings
+{+appdb+} Required Settings
 --------------------------------------
 
 This section describes settings that you must use 
@@ -1491,7 +1491,7 @@ configure your |onprem| {+appdb+}.
       ``featureCompatibilityVersion``
       parameter under :opsmgrkube:`spec.applicationDatabase`.
 
-Application Database Optional Settings
+{+appdb+} Optional Settings
 --------------------------------------
 
 This section describes optional settings related to
@@ -2055,7 +2055,7 @@ This section describes settings that you must use for your
    in the |k8s| documentation.
 
 
-Application Database Required Settings 
+{+appdb+} Required Settings 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This section describes settings specific to your 
diff --git a/source/reference/known-issues.txt b/source/reference/known-issues.txt
@@ -211,12 +211,12 @@ downtime.
 Unable to Update the {+mdbagent+} on {+appdb+} Pods
 -----------------------------------------------------------------
 
-You can't use |onprem| to upgrade the {+mdbagent+}\s that run on the
-Application Database Pods. The {+mdbagent+} version that runs on these
+You can't use |onprem| to upgrade the {+mdbagent+}\'s that run on the
+{+appdb+} Pods. The {+mdbagent+} version that runs on these
 Pods is embedded in the {+appdb+} Docker image.
 
 You can use the |k8s-op-short| to upgrade the {+mdbagent+} version on
-Application Database Pods as MongoDB publishes new images.
+{+appdb+} Pods as MongoDB publishes new images.
 
 .. seealso::
 
diff --git a/source/release-notes.txt b/source/release-notes.txt
@@ -814,7 +814,7 @@ Bug Fixes
 `````````
 
 - Fixes the issue where you configure a liveness probe and it reports a
-  positive result when you terminate a {+mdbagent+}'s process. This could
+  positive result when you terminate a {+mdbagent+}\'s process. This could
   cause Pods hosting MongoDB resources to run without the MongoDB  Agent.
   In addition to this fix, consider configuring 
   :ref:`readiness probe overrides <readiness-probe-override>`.  
@@ -1833,7 +1833,7 @@ Changes
   to the ``matchLabels`` Backup Daemon |k8s-statefulset| attribute.
 
 - The |k8s-op-short| changes the way it collects the status of
-  {+mdbagent+}\s in {+appdb+} |k8s-pods|.
+  {+mdbagent+}\'s in {+appdb+} |k8s-pods|.
 
 New Images
 ``````````
diff --git a/source/tutorial/deploy-om-container-local-mode.txt b/source/tutorial/deploy-om-container-local-mode.txt
@@ -19,7 +19,7 @@ Configure an |onprem| Resource to use Local Mode
    Configuring |onprem| to use Local Mode in |k8s| is not recommended.
    Consider :ref:`configuring Ops Manager to use Remote Mode <deploy-om-container-remote-mode>` instead.
 
-In a default configuration, the {+mdbagent+}\s and Backup Daemons
+In a default configuration, the {+mdbagent+}\'s and Backup Daemons
 access MongoDB installation archives over the Internet from |company|
 
 You can configure |onprem| to run in **Local Mode** with the 
diff --git a/source/tutorial/deploy-om-container-remote-mode.txt b/source/tutorial/deploy-om-container-remote-mode.txt
@@ -14,7 +14,7 @@ Configure an |onprem| Resource to use Remote Mode
    :depth: 2
    :class: singlecol
 
-In a default configuration, the {+mdbagent+}\s and Backup Daemons
+In a default configuration, the {+mdbagent+}\'s and Backup Daemons
 access MongoDB installation archives over the Internet from |company|
 
 You can configure |onprem| to run in **Remote Mode** with the 
diff --git a/source/tutorial/deploy-om-multi-cluster.txt b/source/tutorial/deploy-om-multi-cluster.txt
@@ -58,13 +58,13 @@ procedure in this section, you:
    to it.
 
 5. Deploy an additional {+appdb+} replica set on the second member
-   |k8s| cluster to improve {+appdb+}'s resiliency. You also
+   |k8s| cluster to improve {+appdb+}\'s resiliency. You also
    deploy an additional |application| instance in the second member
    |k8s| cluster.
 
 6. Create valid certificates for |tls| encryption, and establish
    |tls|-encrypted connections to and from the |application| and between
-   the {+appdb+}'s replica set members.  When running over |https|,
+   the {+appdb+}\'s replica set members.  When running over |https|,
    |onprem| runs on port ``8443`` by default.
 
 7. Enable backup using |s3|-compatible storage and deploy the Backup Daemon
diff --git a/source/tutorial/disaster-recovery-om-appdb.txt b/source/tutorial/disaster-recovery-om-appdb.txt
@@ -20,7 +20,7 @@ Disaster Recovery for |onprem| and AppDB Resources
   fails.
 
 :ref:`recover-appdb-forced-reconfig`
-  Recover the {+appdb+}'s replica set when the replica
+  Recover the {+appdb+}\'s replica set when the replica
   set no longer has a majority of nodes to elect a primary.
 
 .. toctree::
diff --git a/source/tutorial/om-arch-reconciliation.txt b/source/tutorial/om-arch-reconciliation.txt
@@ -40,7 +40,7 @@ to the ``MongoDBOpsManager`` |k8s-crd| on each member |k8s| cluster.
      configure the {+appdb+} replica set.
 
      In multi-cluster deployments, the |k8s-op-short| assigns the member
-     cluster's index suffix to each {+appdb+}'s StatefulSet, in
+     cluster's index suffix to each {+appdb+}\'s StatefulSet, in
      the form of ``<om_resource_name>-db-<cluster-idx>``, for example: ``om-db-1``.
 
 3. The |k8s-op-short| creates or updates the ``<om_resource_name>``
diff --git a/source/tutorial/om-nw-lb-mesh-multi-cluster.txt b/source/tutorial/om-nw-lb-mesh-multi-cluster.txt
@@ -98,7 +98,7 @@ Configure a service mesh for the following |k8s| clusters and include them into
 
 Having the same service mesh configured for all |k8s| clusters ensures that each
 |onprem| instance can establish a secure connection to any of the
-Application Database instances deployed in multiple |k8s| clusters.
+{+appdb+} instances deployed in multiple |k8s| clusters.
 
 After you deploy the {+appdb+} instances on member |k8s| clusters,
 the API endpoint for each |onprem| instance that you deploy on member |k8s|
diff --git a/source/tutorial/om-resource-crd-parts.txt b/source/tutorial/om-resource-crd-parts.txt
@@ -50,7 +50,7 @@ deployment:
 
 .. _appdb-om-arch:
 
-Application Database
+{+appdb+}
 ---------------------
 
 For the {+appdb+}, the |k8s-op-short| deploys a MongoDB replica set
@@ -62,15 +62,15 @@ Each Pod for the {+appdb+} has the following containers:
 - {+mdbagent+}. To override the {+mdbagent+} version, use
   the ``$AGENT_IMAGE`` environment variable or ``agent.version``
   in the Helm chart that you use for installing the |k8s-op-short|.
-- {+monitoring-agent+}. You can't override the {+monitoring-agent+}'s version.
+- {+monitoring-agent+}. You can't override the {+monitoring-agent+}\'s version.
   The version that the |k8s-op-short| uses ensures backwards compatibility
   with the |onprem| versions.
 
-  To view the {+monitoring-agent+}'s version:
+  To view the {+monitoring-agent+}\'s version:
 
   - Inspect ``/usr/local/om_version_mapping.json`` inside the Pod for
     the |k8s-op-short| or the image for the |k8s-op-short|.
-  - Check the {+monitoring-agent+}'s container image on the Pod where you deploy
+  - Check the {+monitoring-agent+}\'s container image on the Pod where you deploy
     the {+appdb+}.
 
 In multi-cluster deployments (when you set
@@ -92,12 +92,12 @@ MongoDB replica set nodes for the {+appdb+}:
   :qr-mdb:`container registry </mongodb-enterprise-server?tab=tags>`.
   
 - Each {+mdbagent+} starts |mongod|\s on its {+appdb+}
-  Pod. {+mdbagent+}\s add |mongod| processes to the {+appdb+} replica set.
+  Pod. {+mdbagent+}\'s add |mongod| processes to the {+appdb+} replica set.
 
   You configure the number of replicas and other configuration options
   for the {+appdb+} replica set in the :opsmgrkube:`spec.applicationDatabase`
   collection in the ``MongoDBOpsManager`` custom resource. The |k8s-op-short|
-  passes this configuration to the {+mdbagent+}\s using a |k8s-secret| that the
+  passes this configuration to the {+mdbagent+}\'s using a |k8s-secret| that the
   |k8s-op-short| mounts to each Pod in the {+appdb+} StatefulSet.
 
   In multi-cluster {+appdb+} deployments, (where :opsmgrkube:`spec.applicationDatabase.topology`
@@ -129,7 +129,7 @@ MongoDB replica set nodes for the {+appdb+}:
   :opsmgrkube:`spec.applicationDatabase.podSpec.persistence.single <spec.applicationDatabase>`
   or :opsmgrkube:`spec.applicationDatabase.podSpec.persistence.multiple <spec.applicationDatabase>`.
 
-Application Database Topology
+{+appdb+} Topology
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 To elect a primary, a majority of the {+appdb+} replica set's
@@ -138,10 +138,10 @@ the replica set can't form a voting majority to elect a primary node.
 To learn more, see :manual:`Replica Set Deployment Architectures </core/replica-set-architectures/>`.
 
 If possible, use an odd number of member |k8s| clusters and distribute your
-Application Database nodes across data centers, zones, or |k8s| clusters.
+{+appdb+} nodes across data centers, zones, or |k8s| clusters.
 To learn more, see :manual:`Replica Sets Distributed Across Two or More Data Centers </core/replica-set-architecture-geographically-distributed/>`.
 
-Consider the following examples of the {+appdb+}'s topology:
+Consider the following examples of the {+appdb+}\'s topology:
 
 .. tabs::
 
@@ -153,7 +153,7 @@ Consider the following examples of the {+appdb+}'s topology:
       - Two clusters: three members to ``Cluster 1`` and two members to ``Cluster 2``.
 
         - If ``Cluster 2`` fails, ``Cluster 1`` hosts a sufficient number of
-          {+appdb+}'s replica set members to elect a primary node.
+          {+appdb+}\'s replica set members to elect a primary node.
         - If ``Cluster 1`` fails, ``Cluster 2`` doesn't have enough Application
           Database's members to elect a primary node.
 
@@ -173,7 +173,7 @@ Consider the following examples of the {+appdb+}'s topology:
         - If ``Cluster 1`` fails, there are not enough members on ``Cluster 2`` to elect a primary node.
         
       Although ``Cluster 2`` meets the three member minimum for the {+appdb+},
-      a majority of the {+appdb+}'s seven members must be available
+      a majority of the {+appdb+}\'s seven members must be available
       to elect a primary node.
 
 To learn more, see :ref:`disaster-recovery-om-appdb`.
diff --git a/source/tutorial/plan-om-resource.txt b/source/tutorial/plan-om-resource.txt
@@ -71,7 +71,7 @@ the |k8s-op-short| reuses the secret. If you create an |onprem|
 resource with a different name, then |k8s-op-short| creates a new
 secret and {+appdb+}, and the old secret isn't reused.
 
-Application Database
+{+appdb+}
 ~~~~~~~~~~~~~~~~~~~~
 
 .. _app-db-topology:
@@ -95,12 +95,12 @@ Monitoring
 ++++++++++
 
 The |k8s-op-short| automatically configures |onprem| to monitor the
-Application Database that backs the |application|. The |k8s-op-short|
+{+appdb+} that backs the |application|. The |k8s-op-short|
 creates a project named ``<ops-manager-deployment-name>-db`` for you to
 monitor the {+appdb+} deployment.
 
 |onprem| monitors the {+appdb+} deployment, but |onprem| doesn't
-manage it. You can't change the {+appdb+}'s configuration in
+manage it. You can't change the {+appdb+}\'s configuration in
 the |application|.
 
 .. important::
diff --git a/source/tutorial/recover-appdb-forced-reconfig.txt b/source/tutorial/recover-appdb-forced-reconfig.txt
diff --git a/source/tutorial/recover-om-appdb-yes-k8sop-cluster.txt b/source/tutorial/recover-om-appdb-yes-k8sop-cluster.txt
