Skip to content

Commit 1e83f3e

Browse files
davidhou17euniceadam-mdb
davidhou17
and
euniceadam-mdb
authored
Fixed the apostrophes in all new constants (#1741) (#1761)
Co-authored-by: euniceadam-mdb <[email protected]>
1 parent 83bdaf3 commit 1e83f3e

23 files changed

+56
-56
lines changed

‎source/includes/facts/fact-om-in-multi-clusters-summary-of-diffs.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ These procedures are the same as the procedures for deploying |onprem| in single
2525

2626
You can choose to deploy |onprem| on the central cluster and the Application
2727
Database on a subset of selected member clusters, to increase the
28-
{+appdb+}'s resilience and availability in |onprem|. Configure
28+
{+appdb+}\'s resilience and availability in |onprem|. Configure
2929
the following settings in the |onprem| CRD:
3030

3131
- Use :opsmgrkube:`topology <spec.applicationDatabase.topology>` to specify the ``MultiCluster`` value.

‎source/includes/setting-k8sRsConf-spec.security.authentication.agents.clientCertificateSecretRef.name.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
*Type*: string
44

55

6-
Specifies the |k8s-secret| that contains the {+mdbagent+}'s
6+
Specifies the |k8s-secret| that contains the {+mdbagent+}\'s
77
|tls| certificate. If omitted, defaults to ``agent-certs``.
88

99
This secret must contain the following keys, the

‎source/includes/steps-deploy-k8s-om-multi-https.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -373,11 +373,11 @@
373373
d. Deploy |onprem|. The |k8s-op-short| deploys |onprem| by performing
374374
the following steps. It:
375375

376-
- Deploys the {+appdb+}'s replica set nodes and waits
376+
- Deploys the {+appdb+}\'s replica set nodes and waits
377377
for the MongoDB processes in the replica set to start running.
378-
- Deploys the |application| instance with the {+appdb+}'s
378+
- Deploys the |application| instance with the {+appdb+}\'s
379379
connection string and waits for it to become ready.
380-
- Adds the Monitoring {+mdbagent+} containers to each {+appdb+}'s Pod.
380+
- Adds the Monitoring {+mdbagent+} containers to each {+appdb+}\'s Pod.
381381
- Waits for both the |application| and the {+appdb+} Pods to start running.
382382

383383
.. io-code-block::

‎source/includes/steps-deploy-k8s-opsmgr-local-mode.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ content: |
6565
:opsmgrkube:`spec.configuration` to enable Local Mode.
6666
6767
- Define a |k8s-pv| for the |onprem| StatefulSet to store the
68-
MongoDB installation archive. {+mdbagent+}\s running in MongoDB
68+
MongoDB installation archive. {+mdbagent+}\'s running in MongoDB
6969
database resource containers that you create with the |k8s-op-short|
7070
download the installation archives from |onprem| instead of from the
7171
Internet.
@@ -361,7 +361,7 @@ content: |
361361
the secret you created that contains an |onprem| programmatic
362362
API key pair.
363363
364-
{+mdbagent+}\s run in MongoDB database resource containers that
364+
{+mdbagent+}\'s run in MongoDB database resource containers that
365365
you create with the |k8s-op-short|. Download the installation archives
366366
from |onprem| instead of downloading them from the Internet.
367367

‎source/includes/steps-deploy-k8s-opsmgr-remote-mode.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@ content: |
335335
the secret you created that contains an |onprem| programmatic
336336
API key pair.
337337
338-
{+mdbagent+}\s running in MongoDB database resource containers that
338+
{+mdbagent+}\'s running in MongoDB database resource containers that
339339
you create with the |k8s-op-short| download the installation archives
340340
from |onprem| via Nginx instead of from the Internet.
341341

‎source/includes/steps-openshift-airgapped-env-tutorial.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ content: |
9191
:opsmgrkube:`spec.configuration` to enable Local Mode.
9292
9393
- Define a |k8s-pv| for the |onprem| StatefulSet to store the
94-
MongoDB installation archive. {+mdbagent+}\s running in MongoDB
94+
MongoDB installation archive. {+mdbagent+}\'s running in MongoDB
9595
database resource containers that you create with the |k8s-op-short|
9696
download the installation archives from |onprem| instead of from the
9797
Internet.

‎source/includes/steps-source-deploy-om-resource.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ title: "Create a secret with your {+appdb+} |tls| certificate."
66
content: |
77
88
Run this ``kubectl`` command to create a new |k8s-secret| that stores
9-
the {+appdb+}'s |tls| certificate:
9+
the {+appdb+}\'s |tls| certificate:
1010
1111
.. code-block:: sh
1212

‎source/om-resources.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Deploy Ops Manager Resources on Kubernetes Clusters
5353
:ref:`disaster-recovery-om-appdb`
5454
Manually recover the |k8s-op-short|, the |application|, and the {+appdb+}
5555
in cases when the |k8s| cluster hosting the |k8s-op-short| fails, or when
56-
the {+appdb+}'s replica set loses node majority to elect a primary.
56+
the {+appdb+}\'s replica set loses node majority to elect a primary.
5757

5858
.. toctree::
5959
:titlesonly:

‎source/reference/k8s-operator-crd-logging-specification.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Example Manifest
4040
.. literalinclude:: /includes/code-examples/yaml-files/example-mongodb-logging-config.yaml
4141
:language: yaml
4242

43-
Application Database Log Rotation
43+
{+appdb+} Log Rotation
4444
---------------------------------
4545
You can configure the following log's rotation in the ``MongoDBOpsManager`` |crd|,
4646
as shown in the following example manifest. See the preceding table for more

‎source/reference/k8s-operator-multi-cluster-specification.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -786,7 +786,7 @@ Optional ``MongoDBMultiCluster`` Resource Settings
786786

787787
*Default*: agent-certs
788788

789-
Specifies the |k8s-secret| that contains the {+mdbagent+}'s
789+
Specifies the |k8s-secret| that contains the {+mdbagent+}\'s
790790
|tls| certificate.
791791

792792
This secret must contain the following keys, the

‎source/reference/k8s-operator-om-specification.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ resources.
155155

156156
- When you configure external access to the |onprem| instance on an external
157157
domain, you can specify a custom URL.
158-
This also requires the |k8s-op-short| and the {+appdb+}'s
158+
This also requires the |k8s-op-short| and the {+appdb+}\'s
159159
{+monitoring-agent+}s to use this custom URL instead of the default one.
160160

161161
.. opsmgrkube:: spec.clusterDomain
@@ -1267,7 +1267,7 @@ You can use |tls| for both |s3| and your application database, or for
12671267
:opsmgrkube:`spec.backup.s3Stores.customCertificateSecretRefs`
12681268
instead.
12691269

1270-
Flag that indicates whether you use {+appdb+}'s certificates
1270+
Flag that indicates whether you use {+appdb+}\'s certificates
12711271
(``appdb-ca``) as the custom |tls| certificate for your |s3| backups.
12721272
The default is ``False``.
12731273

@@ -1463,7 +1463,7 @@ You can use |tls| for both |s3| and your application database, or for
14631463
Don't use this field with |aws| |s3| buckets. For more information, see
14641464
:opsmgr:`S3 Blockstore Configuration </reference/api/admin/backup/snapshot/s3Configs/create-one-s3-blockstore-configuration/>`.
14651465

1466-
Application Database Required Settings
1466+
{+appdb+} Required Settings
14671467
--------------------------------------
14681468

14691469
This section describes settings that you must use
@@ -1491,7 +1491,7 @@ configure your |onprem| {+appdb+}.
14911491
``featureCompatibilityVersion``
14921492
parameter under :opsmgrkube:`spec.applicationDatabase`.
14931493

1494-
Application Database Optional Settings
1494+
{+appdb+} Optional Settings
14951495
--------------------------------------
14961496

14971497
This section describes optional settings related to
@@ -2055,7 +2055,7 @@ This section describes settings that you must use for your
20552055
in the |k8s| documentation.
20562056

20572057

2058-
Application Database Required Settings
2058+
{+appdb+} Required Settings
20592059
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20602060

20612061
This section describes settings specific to your

‎source/reference/known-issues.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -211,12 +211,12 @@ downtime.
211211
Unable to Update the {+mdbagent+} on {+appdb+} Pods
212212
-----------------------------------------------------------------
213213

214-
You can't use |onprem| to upgrade the {+mdbagent+}\s that run on the
215-
Application Database Pods. The {+mdbagent+} version that runs on these
214+
You can't use |onprem| to upgrade the {+mdbagent+}\'s that run on the
215+
{+appdb+} Pods. The {+mdbagent+} version that runs on these
216216
Pods is embedded in the {+appdb+} Docker image.
217217

218218
You can use the |k8s-op-short| to upgrade the {+mdbagent+} version on
219-
Application Database Pods as MongoDB publishes new images.
219+
{+appdb+} Pods as MongoDB publishes new images.
220220

221221
.. seealso::
222222

‎source/release-notes.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -814,7 +814,7 @@ Bug Fixes
814814
`````````
815815

816816
- Fixes the issue where you configure a liveness probe and it reports a
817-
positive result when you terminate a {+mdbagent+}'s process. This could
817+
positive result when you terminate a {+mdbagent+}\'s process. This could
818818
cause Pods hosting MongoDB resources to run without the MongoDB Agent.
819819
In addition to this fix, consider configuring
820820
:ref:`readiness probe overrides <readiness-probe-override>`.
@@ -1833,7 +1833,7 @@ Changes
18331833
to the ``matchLabels`` Backup Daemon |k8s-statefulset| attribute.
18341834

18351835
- The |k8s-op-short| changes the way it collects the status of
1836-
{+mdbagent+}\s in {+appdb+} |k8s-pods|.
1836+
{+mdbagent+}\'s in {+appdb+} |k8s-pods|.
18371837

18381838
New Images
18391839
``````````

‎source/tutorial/deploy-om-container-local-mode.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Configure an |onprem| Resource to use Local Mode
1919
Configuring |onprem| to use Local Mode in |k8s| is not recommended.
2020
Consider :ref:`configuring Ops Manager to use Remote Mode <deploy-om-container-remote-mode>` instead.
2121

22-
In a default configuration, the {+mdbagent+}\s and Backup Daemons
22+
In a default configuration, the {+mdbagent+}\'s and Backup Daemons
2323
access MongoDB installation archives over the Internet from |company|
2424

2525
You can configure |onprem| to run in **Local Mode** with the

‎source/tutorial/deploy-om-container-remote-mode.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Configure an |onprem| Resource to use Remote Mode
1414
:depth: 2
1515
:class: singlecol
1616

17-
In a default configuration, the {+mdbagent+}\s and Backup Daemons
17+
In a default configuration, the {+mdbagent+}\'s and Backup Daemons
1818
access MongoDB installation archives over the Internet from |company|
1919

2020
You can configure |onprem| to run in **Remote Mode** with the

‎source/tutorial/deploy-om-multi-cluster.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,13 +58,13 @@ procedure in this section, you:
5858
to it.
5959

6060
5. Deploy an additional {+appdb+} replica set on the second member
61-
|k8s| cluster to improve {+appdb+}'s resiliency. You also
61+
|k8s| cluster to improve {+appdb+}\'s resiliency. You also
6262
deploy an additional |application| instance in the second member
6363
|k8s| cluster.
6464

6565
6. Create valid certificates for |tls| encryption, and establish
6666
|tls|-encrypted connections to and from the |application| and between
67-
the {+appdb+}'s replica set members. When running over |https|,
67+
the {+appdb+}\'s replica set members. When running over |https|,
6868
|onprem| runs on port ``8443`` by default.
6969

7070
7. Enable backup using |s3|-compatible storage and deploy the Backup Daemon

‎source/tutorial/disaster-recovery-om-appdb.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Disaster Recovery for |onprem| and AppDB Resources
2020
fails.
2121

2222
:ref:`recover-appdb-forced-reconfig`
23-
Recover the {+appdb+}'s replica set when the replica
23+
Recover the {+appdb+}\'s replica set when the replica
2424
set no longer has a majority of nodes to elect a primary.
2525

2626
.. toctree::

‎source/tutorial/om-arch-reconciliation.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ to the ``MongoDBOpsManager`` |k8s-crd| on each member |k8s| cluster.
4040
configure the {+appdb+} replica set.
4141

4242
In multi-cluster deployments, the |k8s-op-short| assigns the member
43-
cluster's index suffix to each {+appdb+}'s StatefulSet, in
43+
cluster's index suffix to each {+appdb+}\'s StatefulSet, in
4444
the form of ``<om_resource_name>-db-<cluster-idx>``, for example: ``om-db-1``.
4545

4646
3. The |k8s-op-short| creates or updates the ``<om_resource_name>``

‎source/tutorial/om-nw-lb-mesh-multi-cluster.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ Configure a service mesh for the following |k8s| clusters and include them into
9898

9999
Having the same service mesh configured for all |k8s| clusters ensures that each
100100
|onprem| instance can establish a secure connection to any of the
101-
Application Database instances deployed in multiple |k8s| clusters.
101+
{+appdb+} instances deployed in multiple |k8s| clusters.
102102

103103
After you deploy the {+appdb+} instances on member |k8s| clusters,
104104
the API endpoint for each |onprem| instance that you deploy on member |k8s|

‎source/tutorial/om-resource-crd-parts.txt

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ deployment:
5050

5151
.. _appdb-om-arch:
5252

53-
Application Database
53+
{+appdb+}
5454
---------------------
5555

5656
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:
6262
- {+mdbagent+}. To override the {+mdbagent+} version, use
6363
the ``$AGENT_IMAGE`` environment variable or ``agent.version``
6464
in the Helm chart that you use for installing the |k8s-op-short|.
65-
- {+monitoring-agent+}. You can't override the {+monitoring-agent+}'s version.
65+
- {+monitoring-agent+}. You can't override the {+monitoring-agent+}\'s version.
6666
The version that the |k8s-op-short| uses ensures backwards compatibility
6767
with the |onprem| versions.
6868

69-
To view the {+monitoring-agent+}'s version:
69+
To view the {+monitoring-agent+}\'s version:
7070

7171
- Inspect ``/usr/local/om_version_mapping.json`` inside the Pod for
7272
the |k8s-op-short| or the image for the |k8s-op-short|.
73-
- Check the {+monitoring-agent+}'s container image on the Pod where you deploy
73+
- Check the {+monitoring-agent+}\'s container image on the Pod where you deploy
7474
the {+appdb+}.
7575

7676
In multi-cluster deployments (when you set
@@ -92,12 +92,12 @@ MongoDB replica set nodes for the {+appdb+}:
9292
:qr-mdb:`container registry </mongodb-enterprise-server?tab=tags>`.
9393

9494
- Each {+mdbagent+} starts |mongod|\s on its {+appdb+}
95-
Pod. {+mdbagent+}\s add |mongod| processes to the {+appdb+} replica set.
95+
Pod. {+mdbagent+}\'s add |mongod| processes to the {+appdb+} replica set.
9696

9797
You configure the number of replicas and other configuration options
9898
for the {+appdb+} replica set in the :opsmgrkube:`spec.applicationDatabase`
9999
collection in the ``MongoDBOpsManager`` custom resource. The |k8s-op-short|
100-
passes this configuration to the {+mdbagent+}\s using a |k8s-secret| that the
100+
passes this configuration to the {+mdbagent+}\'s using a |k8s-secret| that the
101101
|k8s-op-short| mounts to each Pod in the {+appdb+} StatefulSet.
102102

103103
In multi-cluster {+appdb+} deployments, (where :opsmgrkube:`spec.applicationDatabase.topology`
@@ -129,7 +129,7 @@ MongoDB replica set nodes for the {+appdb+}:
129129
:opsmgrkube:`spec.applicationDatabase.podSpec.persistence.single <spec.applicationDatabase>`
130130
or :opsmgrkube:`spec.applicationDatabase.podSpec.persistence.multiple <spec.applicationDatabase>`.
131131

132-
Application Database Topology
132+
{+appdb+} Topology
133133
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
134134

135135
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.
138138
To learn more, see :manual:`Replica Set Deployment Architectures </core/replica-set-architectures/>`.
139139

140140
If possible, use an odd number of member |k8s| clusters and distribute your
141-
Application Database nodes across data centers, zones, or |k8s| clusters.
141+
{+appdb+} nodes across data centers, zones, or |k8s| clusters.
142142
To learn more, see :manual:`Replica Sets Distributed Across Two or More Data Centers </core/replica-set-architecture-geographically-distributed/>`.
143143

144-
Consider the following examples of the {+appdb+}'s topology:
144+
Consider the following examples of the {+appdb+}\'s topology:
145145

146146
.. tabs::
147147

@@ -153,7 +153,7 @@ Consider the following examples of the {+appdb+}'s topology:
153153
- Two clusters: three members to ``Cluster 1`` and two members to ``Cluster 2``.
154154

155155
- If ``Cluster 2`` fails, ``Cluster 1`` hosts a sufficient number of
156-
{+appdb+}'s replica set members to elect a primary node.
156+
{+appdb+}\'s replica set members to elect a primary node.
157157
- If ``Cluster 1`` fails, ``Cluster 2`` doesn't have enough Application
158158
Database's members to elect a primary node.
159159

@@ -173,7 +173,7 @@ Consider the following examples of the {+appdb+}'s topology:
173173
- If ``Cluster 1`` fails, there are not enough members on ``Cluster 2`` to elect a primary node.
174174

175175
Although ``Cluster 2`` meets the three member minimum for the {+appdb+},
176-
a majority of the {+appdb+}'s seven members must be available
176+
a majority of the {+appdb+}\'s seven members must be available
177177
to elect a primary node.
178178

179179
To learn more, see :ref:`disaster-recovery-om-appdb`.

‎source/tutorial/plan-om-resource.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ the |k8s-op-short| reuses the secret. If you create an |onprem|
7171
resource with a different name, then |k8s-op-short| creates a new
7272
secret and {+appdb+}, and the old secret isn't reused.
7373

74-
Application Database
74+
{+appdb+}
7575
~~~~~~~~~~~~~~~~~~~~
7676

7777
.. _app-db-topology:
@@ -95,12 +95,12 @@ Monitoring
9595
++++++++++
9696

9797
The |k8s-op-short| automatically configures |onprem| to monitor the
98-
Application Database that backs the |application|. The |k8s-op-short|
98+
{+appdb+} that backs the |application|. The |k8s-op-short|
9999
creates a project named ``<ops-manager-deployment-name>-db`` for you to
100100
monitor the {+appdb+} deployment.
101101

102102
|onprem| monitors the {+appdb+} deployment, but |onprem| doesn't
103-
manage it. You can't change the {+appdb+}'s configuration in
103+
manage it. You can't change the {+appdb+}\'s configuration in
104104
the |application|.
105105

106106
.. important::

0 commit comments

Comments
 (0)