Skip to content

Commit 3109e0a

Browse files
Fix more links (#1574)
* more glossary link fixes * fix
1 parent 2cb07df commit 3109e0a

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

source/includes/steps-deploy-k8s-opsmgr-http.yaml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -181,9 +181,9 @@ content: |
181181
182182
To configure backup, you must enable it, and then:
183183
184-
- Choose to configure an :term:`S3 snapshot store <S3 Snapshot Store>` snapshot store <s3 snapshot store>`
184+
- Choose to configure an :term:`S3 snapshot store <S3 Snapshot Store>`
185185
or a :term:`blockstore <Backup Blockstore Database>`. If you deploy
186-
both an |s3| :term:`snapshot store <s3 snapshot store>` and a
186+
both an |s3| :term:`snapshot store <S3 Snapshot Store>` and a
187187
:term:`blockstore <Backup Blockstore Database>`, |onprem|
188188
randomly choses one to use for backup.
189189
@@ -255,12 +255,12 @@ content: |
255255
- Name of the MongoDB database resource for the |s3| oplog store.
256256
- ``my-s3-oplog-db``
257257
258-
You must also configure an :term:`S3 snapshot store <S3 Snapshot Store>` snapshot store <s3 snapshot store>`
258+
You must also configure an :term:`S3 snapshot store <S3 Snapshot Store>`
259259
or a :term:`blockstore <Backup Blockstore Database>`.
260260
261261
.. note::
262262
263-
If you deploy both an |s3| :term:`snapshot store <s3 snapshot store>`
263+
If you deploy both an |s3| :term:`snapshot store <S3 Snapshot Store>`
264264
and a :term:`blockstore <Backup Blockstore Database>`, |onprem|
265265
randomly choses one to use for backup.
266266

source/includes/steps-deploy-k8s-opsmgr-https.yaml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -314,9 +314,9 @@ content: |
314314
315315
To configure backup, you must enable it, and then:
316316
317-
- Choose to configure an :term:`S3 snapshot store <S3 Snapshot Store>` snapshot store <s3 snapshot store>`
317+
- Choose to configure an :term:`S3 snapshot store <S3 Snapshot Store>`
318318
or a :term:`blockstore <Backup Blockstore Database>`. If you deploy
319-
both an |s3| :term:`snapshot store <s3 snapshot store>` and a
319+
both an |s3| :term:`snapshot store <S3 Snapshot Store>` and a
320320
:term:`blockstore <Backup Blockstore Database>`, |onprem|
321321
randomly choses one to use for backup.
322322
@@ -388,12 +388,12 @@ content: |
388388
The resource's ``metadata.name`` must match this name.
389389
- ``my-s3-oplog-db``
390390
391-
You must also configure an :term:`S3 snapshot store <S3 Snapshot Store>` snapshot store <s3 snapshot store>`
391+
You must also configure an :term:`S3 snapshot store <S3 Snapshot Store>`
392392
or a :term:`blockstore <Backup Blockstore Database>`.
393393
394394
.. note::
395395
396-
If you deploy both an :term:`S3 snapshot store <S3 Snapshot Store>` snapshot store <s3 snapshot store>`
396+
If you deploy both an :term:`S3 snapshot store <S3 Snapshot Store>`
397397
and a :term:`blockstore <Backup Blockstore Database>`, |onprem|
398398
randomly choses one to use for Backup.
399399

source/tutorial/plan-om-resource.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -197,8 +197,8 @@ enable the Backup Daemon and configure the head database.
197197
- :term:`oplog store <Oplog Store Database>` or |s3| oplog store.
198198
If you deploy both the oplog store and the |s3| oplog store, |onprem|
199199
chooses one to use for Backup at random.
200-
- |s3| :term:`snapshot store <s3 snapshot store>` or :term:`blockstore <Backup Blockstore Database>`.
201-
If you deploy both an |s3| :term:`snapshot store <s3 snapshot store>` and a
200+
- |s3| :term:`snapshot store <S3 Snapshot Store>` or :term:`blockstore <Backup Blockstore Database>`.
201+
If you deploy both an |s3| :term:`snapshot store <S3 Snapshot Store>` and a
202202
:term:`blockstore <Backup Blockstore Database>`, |onprem| chooses one
203203
to use for Backup at random.
204204

0 commit comments

Comments
 (0)