mongodb
diff --git a/‎source/includes/fact-configure-connections-to-app-db.rst
Lines changed: 4 additions & 6 deletions b/‎source/includes/fact-configure-connections-to-app-db.rst
Lines changed: 4 additions & 6 deletions
diff --git a/‎source/includes/steps-admin-add-blockstore.yaml
Lines changed: 6 additions & 4 deletions b/‎source/includes/steps-admin-add-blockstore.yaml
Lines changed: 6 additions & 4 deletions
diff --git a/‎source/includes/steps-admin-add-filestore.yaml
Lines changed: 6 additions & 10 deletions b/‎source/includes/steps-admin-add-filestore.yaml
Lines changed: 6 additions & 10 deletions
diff --git a/‎source/includes/steps-admin-add-oplogstore.yaml
Lines changed: 3 additions & 1 deletion b/‎source/includes/steps-admin-add-oplogstore.yaml
Lines changed: 3 additions & 1 deletion
diff --git a/‎source/includes/steps-admin-edit-blockstore.yaml
Lines changed: 55 additions & 65 deletions b/‎source/includes/steps-admin-edit-blockstore.yaml
Lines changed: 55 additions & 65 deletions
diff --git a/‎source/includes/steps-admin-edit-oplogstore.yaml
Lines changed: 18 additions & 20 deletions b/‎source/includes/steps-admin-edit-oplogstore.yaml
Lines changed: 18 additions & 20 deletions
diff --git a/‎source/includes/steps-configure-agent-ssl-to-web-interface.yaml
Lines changed: 22 additions & 28 deletions b/‎source/includes/steps-configure-agent-ssl-to-web-interface.yaml
Lines changed: 22 additions & 28 deletions
diff --git a/‎source/includes/steps-configure-application-high-availability.yaml
Lines changed: 3 additions & 5 deletions b/‎source/includes/steps-configure-application-high-availability.yaml
Lines changed: 3 additions & 5 deletions
@@ -1,6 +1,4 @@
-.. note::
-
-   If your :ref:`Ops Manager Application Database 
-   <deploy-om-appdb>` uses authentication or |tls|, you must have 
-   connections configured to the application database. To learn 
-   more, see :ref:`configure-connections-to-app-db`.
+If your :ref:`Ops Manager Application Database 
+<deploy-om-appdb>` uses authentication or |tls|, you must have 
+connections configured to the application database. To learn 
+more, see :ref:`configure-connections-to-app-db`.
@@ -40,9 +40,11 @@ content: |
          Sharded Cluster) in the ``<hostname:port>`` format that
          comprise the blockstore database.
 
-         .. example::
+         For example: 
 
-            ``h1.ex.com:27017,h2.ex.com:27017,h2.ex.com:27018``
+         .. code-block:: ini
+
+            h1.ex.com:27017,h2.ex.com:27017,h2.ex.com:27018
 
          This field displays only if you set
          :guilabel:`Datastore Type` to :guilabel:`Replica Set` or
@@ -72,10 +74,10 @@ content: |
        - Optional
        - If you set this value:
 
-         .. include:: /includes/warning-plaintext-password.rst
-
          .. include:: /includes/tabsets/storage-settings-password.rst
 
+         .. include:: /includes/warning-plaintext-password.rst
+
      * - Connection Options
        - Optional
        - Add additional :ref:`connection string options
 
@@ -36,23 +36,19 @@ content: |
           compressed. Any backup job using MMapV1 snapshots inherits
           this setting. The default value is ``on``.
 
-          .. note::
-
-             If you plan on using queryable backups, set this value to
-             ``off``. Queryable backup cannot query compressed
-             snapshots.
+          If you plan on using queryable backups, set this value to
+          ``off``. Queryable backup cannot query compressed
+          snapshots.
 
       * - :guilabel:`WiredTiger Compression Setting`
 
         - Select whether or not WiredTiger storage engine snapshots are
           compressed. Any backup job using WiredTiger snapshots
           inherits this setting. The default value is ``off``.
 
-          .. note::
-
-             If you plan on using queryable backups, set this value to
-             ``off``. Queryable backup cannot query compressed
-             snapshots.
+          If you plan on using queryable backups, set this value to
+          ``off``. Queryable backup cannot query compressed
+          snapshots.
 
       * - :guilabel:`New Assignment Enabled` checkbox
 
 
@@ -40,7 +40,9 @@ content: |
           the ``<hostname:port>`` format that comprise the Oplog Store
           database.
 
-          .. example::
+          For example: 
+
+          .. code-block:: ini
 
              host1.example.com:27017, host2.example.com:27017, host2.example.com:27018
 
 
@@ -32,24 +32,23 @@ content: |
        - Type in one or more hosts that comprise the blockstore
          database in the ``<hostname:port>`` format.
 
-         .. important::
+         :gold:`IMPORTANT:` If these hosts are changed, the blockstore database they
+         host must have the same data as the original blockstore database. 
+         Changing the host to a new blockstore databases results in data loss.
 
-            If these hosts are changed, the blockstore database they
-            host must have the same data as the original blockstore
-            database. Changing the host to a new blockstore
-            databases results in data loss.
+         If the blockstore database is a Replica Set or Sharded Cluster, 
+         type a comma-separated list of :manual:`mongod </reference/program/mongod/#mongodb-binary-bin.mongod>`
+         instances (for a Replica Set) or :manual:`mongos </reference/program/mongos/#mongodb-binary-bin.mongos>`
+         instances (for a Sharded Cluster).
 
-         - If the blockstore database is a Replica Set or Sharded
-           Cluster, type a comma-separated list of :manual:`mongod </reference/program/mongod/#mongodb-binary-bin.mongod>`
-           instances (for a Replica Set) or :manual:`mongos </reference/program/mongos/#mongodb-binary-bin.mongos>`
-           instances (for a Sharded Cluster).
+         For example: 
 
-           .. example::
+         .. code-block:: ini
 
-              ``host1.example.com:27017,host2.example.com:27017,host2.example.com:27018``
+            host1.example.com:27017,host2.example.com:27017,host2.example.com:27018
 
-         - If the blockstore database is a standalone MongoDB
-           instance, type the ``hostname:port`` of the instance.
+         If the blockstore database is a standalone MongoDB
+         instance, type the ``hostname:port`` of the instance.
 
      * - MongoDB Auth Username
 
@@ -63,13 +62,11 @@ content: |
 
          .. include:: /includes/tabsets/storage-settings-password.rst
 
+         |onprem| doesn't display the existing
+         :guilabel:`MongoDB Auth Password`.
+         
          .. include:: /includes/warning-plaintext-password.rst
 
-         .. note::
-
-            |onprem| doesn't display the existing
-            :guilabel:`MongoDB Auth Password`.
-
      * - Encrypted Credentials
 
        - Select if the Username and Password for the database were
@@ -105,54 +102,57 @@ content: |
          snapshot store.
 
          Backup work includes running backups, restoring snapshots or
-         :term:`grooming <groom>` blockstores. The backup work
-         ratio assigned to a single snapshot store is called its *Load
-         Factor*.
-
-         .. important::
+         :term:`grooming <groom>` blockstores. The ratio of backup work
+         assigned to a single snapshot store is called its *Load
+         Factor*.         
+
+         :gold:`IMPORTANT:` If you have only one snapshot store,
+         :guilabel:`Load Factor` represents the number of concurrent 
+         backup work processes the snapshot store performs at a time.
+         To avoid performance costs associated with running multiple 
+         concurrent processes when you have one snapshot store, 
+         omit this setting to assign your snapshot store the 
+         default :guilabel:`Load Factor` of ``1``. 
+
+         When you have multiple snapshot stores, the default :guilabel:`Load Factor` 
+         of ``1`` assigns each snapshot store the same amount of work. If a snapshot 
+         store's :guilabel:`Load Factor` is set to ``0``, 
+         it performs no backup work at all. 
          
-            If you have only one snapshot store, the :guilabel:`Load Factor`
-            setting represents the number of concurrent backup work processes the 
-            snapshot store performs at a time. 
-              
-            To avoid performance costs associated with running multiple 
-            concurrent processes when you have one snapshot store, omit this
-            setting to assign your snapshot store the default :guilabel:`Load Factor` of ``1``. 
-
-         By default, |mms| assigns each snapshot store a
-         :guilabel:`Load Factor` of ``1``. This means each snapshot
-         store performs the same amount of backup work.
+         If a snapshot store's :guilabel:`Load Factor` is changed while 
+         backup work is in progress, all jobs or tasks running on that snapshot store
+         are allowed to finish. All future backup work is then re-
+         distributed among the remaining snapshot stores that have a
+         :guilabel:`Load Factor` of ``1`` or greater and 
+         :guilabel:`Assignment Enabled` selected. 
 
          As a snapshot store's :guilabel:`Load Factor` increases, it
          performs more backup work compared to another snapshot store.
-         If the :guilabel:`Load Factor` of snapshot store ``A`` is set
+         For example, if the :guilabel:`Load Factor` of snapshot store ``A`` is set
          to ``2`` and the :guilabel:`Load Factor` of snapshot store
-         ``B`` is set to ``1``, ``A`` performs two times the backup
+         ``B`` is set to ``1``, then ``A`` performs two times the backup
          work of ``B``.
 
-         .. example:: **How to estimate Load Factor**
+         Snapshot stores with greater computer or storage performance
+         should be given a greater :guilabel:`Load Factor`. 
+         For example, consider a five-shard sharded cluster with the
+         following backup storage configuration:
 
-            Consider a five-shard sharded cluster with the
-            following backup storage configuration:
+         - File system store (``F``) manages the backup work for
+           one shard in the cluster. ``F`` is running on a single
+           two-core physical server.
 
-            - File system store (``F``) manages the backup work for
-              one shard in the cluster. ``F`` is running on a single
-              two-core physical server.
+         - Blockstore (``B``) manages the backup work for four
+           shards in the cluster. ``B`` is running as a four-node
+           sharded cluster on four physical servers with two cores
+           on each server.
 
-            - Blockstore (``B``) manages the backup work for four
-              shards in the cluster. ``B`` is running as a four-node
-              sharded cluster on four physical servers with two cores
-              on each server.
+         In this example, ``B`` has four times the capability of
+         ``F``. You should set the :guilabel:`Load Factor`\s of ``B`` to ``4`` and ``F`` to ``1``. 
+         For every ``1`` backup task ``F`` performs, ``B`` performs ``4``.
 
-            In this example, ``B`` has four times the capability of
-            ``F``. ``B`` should receive the greater part of the ratio
-            of backup work: ``4:1``. For every one backup task ``F``
-            performs, ``B`` performs ``4``.
-
-            Set the Load Factors of ``B`` to ``4`` and ``F`` to ``1``.
-
-         Snapshot stores with greater compute or storage performance
-         should be given a greater :guilabel:`Load Factor`:
+         For more examples comparing the storage capabilities of 
+         different backup configurations, see:  
 
          - A file system store with 16-cores and 128 GB of RAM can
            back up more databases in less time than a file system
@@ -162,16 +162,6 @@ content: |
            up more databases and groom more databases than a
            blockstore backed by a single replica set.
 
-         :guilabel:`Load Factor` can be set to ``0``. When one
-         snapshot store's :guilabel:`Load Factor` is set to ``0``, it
-         performs no backup work at all. If a snapshot store's
-         :guilabel:`Load Factor` is changed while backup work is in
-         progress, all jobs or tasks running on that snapshot store
-         are allowed to finish. All future backup work then is re-
-         distributed among the remaining snapshot stores with a
-         :guilabel:`Load Factor` of ``1`` or greater and have
-         :guilabel:`Assignment Enabled` selected.
-
      * - Write Concern
 
        - Select your preferred
 
@@ -31,24 +31,24 @@ content: |
        - Type in one or more hosts that comprise the Oplog Store
          database in the ``<hostname:port>`` format.
 
-         .. important::
+         :gold:`IMPORTANT:` If these hosts are changed, the Oplog Store database they
+         host must have the same data as the original Oplog Store
+         database. Changing the host to a new Oplog Store database
+         results in data loss.
 
-            If these hosts are changed, the Oplog Store database they
-            host must have the same data as the original Oplog Store
-            database. Changing the host to a new Oplog Store database
-            results in data loss.
+         If the Oplog Store database is a Replica Set or Sharded
+         Cluster, type a comma-separated list of |mongod| instances
+         (for a Replica Set) or |mongos| instances (for a Sharded
+         Cluster).
 
-         - If the Oplog Store database is a Replica Set or Sharded
-           Cluster, type a comma-separated list of |mongod| instances
-           (for a Replica Set) or |mongos| instances (for a Sharded
-           Cluster).
+         For example:
+         
+         .. code-block:: ini
+         
+            host1.example.com:27017,host2.example.com:27017,host2.example.com:27018
 
-           .. example::
-
-              host1.example.com:27017, host2.example.com:27017, host2.example.com:27018
-
-         - If the Oplog Store database is a standalone MongoDB
-           instance, type the ``hostname:port`` of the instance.
+         If the Oplog Store database is a standalone MongoDB
+         instance, type the ``hostname:port`` of the instance.
 
      * - MongoDB Auth Username
 
@@ -62,12 +62,10 @@ content: |
 
          .. include:: /includes/tabsets/storage-settings-password.rst
 
-         .. include:: /includes/warning-plaintext-password.rst
+         |onprem| doesn't display the existing
+         :guilabel:`MongoDB Auth Password`.
 
-         .. note::
-
-            |onprem| doesn't display the existing
-            :guilabel:`MongoDB Auth Password`.
+         .. include:: /includes/warning-plaintext-password.rst
 
      * - Encrypted Credentials
 
 
@@ -32,16 +32,14 @@ content: |
        - Set this value to match the |url| you entered in the
          :guilabel:`URL to Access Ops Manager` box.
 
-         .. important::
-
-            Ensure that you update both this property and the 
-            :guilabel:`URL to Access Ops Manager` box. Both values must 
-            match. If {+magent+} and {+bagent+} are enabled for the 
-            {+mdbagent+}, they use the :guilabel:`URL to Access Ops 
-            Manager` configured on the |onprem| server, unless the 
-            ``mmsBaseURL`` custom monitoring setting is set for the 
-            {+mdbagent+}. For more information, see the 
-            :ref:`MongoDB Agent Monitoring Settings <mongodb-agent-settings>`.
+         :gold:`IMPORTANT:` Ensure that you update both this property and the 
+         :guilabel:`URL to Access Ops Manager` box. Both values must 
+         match. If {+magent+} and {+bagent+} are enabled for the 
+         {+mdbagent+}, they use the :guilabel:`URL to Access Ops 
+         Manager` configured on the |onprem| server, unless the 
+         ``mmsBaseURL`` custom monitoring setting is set for the 
+         {+mdbagent+}. For more information, see the 
+         :ref:`MongoDB Agent Monitoring Settings <mongodb-agent-settings>`.
 
      * - :setting:`tlsRequireValidMMSServerCertificates`
        - Conditional
@@ -53,37 +51,33 @@ content: |
            hosts with a known external |certauth| or self-signed
            |certauth|.
 
-         .. note::
-
-            If you set this value to ``true``, you must set
-            :msetting:`httpsCAFile`.
+         If you set this value to ``true``, you must set
+         :msetting:`httpsCAFile`.
 
      * - :msetting:`httpsCAFile`
        - Conditional
        - If you are using your own self-signed |certauth| ``.pem``
          files, add this property and set it to the absolute path to
          your |certauth| file on the MongoDB host.
 
-         .. important::
-
-            This |certauth| file must be in the same location on each
-            MongoDB host in the same sharded cluster or replica set.
-            Any MongoDB host that does not have the file in the same
-            file location as the others may become unaccessible.
+         :gold:`IMPORTANT:` This |certauth| file must be in the same 
+         location on each MongoDB host in the same sharded cluster 
+         or replica set. Any MongoDB host that does not have the file 
+         in the same file location as the others may become unaccessible.
 
-            Add the |certauth| for the ``downloads.mongodb.com``
-            certificate to this ``.pem`` file if you:
+         Add the |certauth| for the ``downloads.mongodb.com``
+         certificate to this ``.pem`` file if you:
 
-            1. Need your {+mdbagent+}s to download their MongoDB
+         1. Need your {+mdbagent+}s to download their MongoDB
                installers from the Internet,
 
-            #. Use TLS to encrypt connections, and
+         #. Use TLS to encrypt connections, and
 
-            #. Signed your certificates with a private CA. (You set the
-               ``httpsCAFile`` option.)
+         #. Signed your certificates with a private CA. (You set the
+            ``httpsCAFile`` option.)
 
-            To learn how to download TLS certificates from another web
-            site, see the `OpenSSL Cookbook entry <https://www.feistyduck.com/library/openssl-cookbook/online/ch-testing-with-openssl.html#extracting-remote-certificates>`__.
+         To learn how to download TLS certificates from another web
+         site, see the `OpenSSL Cookbook entry <https://www.feistyduck.com/library/openssl-cookbook/online/ch-testing-with-openssl.html#extracting-remote-certificates>`__.
 
      * - :setting:`tlsMMSServerClientCertificate`
        - Conditional
 
@@ -26,11 +26,9 @@ pre: |
       * - 500
         - |onprem| host or :term:`application database` appear 
           unhealthy.
-
-          .. seealso::
-
-             If this endpoint returns ``HTTP 500`` often, review the 
-             :doc:`/troubleshooting` section.
+          
+          If this endpoint returns ``HTTP 500`` often, review the 
+          :doc:`/troubleshooting` section.
 
    The load balancer must not return cached content.
 ---