DOP-1186: admonition :class: important -> .. important::

schmalliso · schmalliso · commit ee732bd05e2c · 2020-08-11T14:06:13.000-04:00
diff --git a/source/administration/analyzing-mongodb-performance.txt b/source/administration/analyzing-mongodb-performance.txt
@@ -156,8 +156,8 @@ processes run with FTDC on by default. For more information on MongoDB
 Support options, visit
 `Getting Started With MongoDB Support <https://www.mongodb.com/support/get-started?tck=docs_server>`_.
 
-.. admonition:: FTDC Privacy
-   :class: important
+.. important:: FTDC Privacy
+
 
    FTDC data files are compressed and not human-readable. MongoDB Inc.
    engineers cannot access FTDC data without explicit permission
diff --git a/source/core/geohaystack.txt b/source/core/geohaystack.txt
@@ -12,8 +12,8 @@
    :depth: 1
    :class: singlecol
 
-.. admonition:: Deprecation
-   :class: important
+.. important:: Deprecation
+
 
    .. include:: /includes/extracts/4.4-changes-geo-deprecation.rst
 
diff --git a/source/core/index-unique.txt b/source/core/index-unique.txt
@@ -253,8 +253,8 @@ For a ranged sharded collection, only the following indexes can be
   enforces the uniqueness constraint per shard **if** the ``_id`` field
   is **not** the shard key or the prefix of the shard key.
 
-  .. admonition:: Uniqueness and the ``_id`` Index
-     :class: important
+  .. important:: Uniqueness and the ``_id`` Index
+
 
      If the ``_id`` field is not the shard key or the prefix of the
      shard key, ``_id`` index only enforces the uniqueness constraint
diff --git a/source/core/sharding-shard-key.txt b/source/core/sharding-shard-key.txt
@@ -154,8 +154,8 @@ For a ranged sharded collection, only the following indexes can be
      enforces the uniqueness constraint per shard **if** the ``_id`` field
      is **not** the shard key or the prefix of the shard key.
 
-     .. admonition:: Uniqueness and the ``_id`` Index
-        :class: important
+     .. important:: Uniqueness and the ``_id`` Index
+
 
         If the ``_id`` field is not the shard key or the prefix of the
         shard key, ``_id`` index only enforces the uniqueness constraint
diff --git a/source/includes/extracts-projection.yaml b/source/includes/extracts-projection.yaml
@@ -287,8 +287,8 @@ content: |
 ref: projection-language-consistency-admonition
 content: |
 
-   .. admonition:: Language Consistency
-      :class: important
+   .. important:: Language Consistency
+
 
       Starting in MongoDB 4.4, as part of making
       :method:`~db.collection.find` and
diff --git a/source/includes/fact-mongo-shell-method.rst b/source/includes/fact-mongo-shell-method.rst
@@ -1,5 +1,5 @@
-.. admonition:: ``mongo`` Shell Method
-   :class: important
+.. important:: ``mongo`` Shell Method
+
 
    This page documents the :binary:`~bin.mongo` shell method, and does
    *not* refer to the MongoDB Node.js driver (or any other driver)
diff --git a/source/includes/fact-rs-status-init-sync-availability.rst b/source/includes/fact-rs-status-init-sync-availability.rst
@@ -1,5 +1,5 @@
-.. admonition:: Availability
-   :class: important
+.. important:: Availability
+
 
    Starting in MongoDB 4.2.1,
    :data:`replSetGetStatus.initialSyncStatus` metrics are only
diff --git a/source/reference/command/geoSearch.txt b/source/reference/command/geoSearch.txt
@@ -12,8 +12,8 @@ geoSearch
 
 .. dbcommand:: geoSearch
 
-   .. admonition:: Deprecation
-      :class: important
+   .. important:: Deprecation
+
 
       .. include:: /includes/extracts/4.4-changes-geo-deprecation.rst
 
diff --git a/source/reference/method/db.collection.findOne.txt b/source/reference/method/db.collection.findOne.txt
@@ -81,8 +81,8 @@ Client Disconnection
 Projection
 ~~~~~~~~~~
 
-.. admonition:: Language Consistency
-   :class: important
+.. important:: Language Consistency
+
 
    Starting in MongoDB 4.4, as part of making
    :method:`~db.collection.find` and
diff --git a/source/reference/mongodb-extended-json-v1.txt b/source/reference/mongodb-extended-json-v1.txt
@@ -11,8 +11,8 @@ MongoDB Extended JSON (v1)
    :class: singlecol
 
 
-.. admonition:: Disambiguation
-   :class: important
+.. important:: Disambiguation
+
 
    The following page discusses MongoDB Extended JSON v1 (Legacy
    extended JSON). For discussion on MongoDB Extended JSON v2, see
diff --git a/source/reference/mongodb-extended-json.txt b/source/reference/mongodb-extended-json.txt
@@ -10,8 +10,8 @@ MongoDB Extended JSON (v2)
    :depth: 1
    :class: singlecol
 
-.. admonition:: Disambiguation
-   :class: important
+.. important:: Disambiguation
+
 
    The following page discusses MongoDB Extended JSON v2. For
    discussion on the Legacy MongoDB Extended JSON v1, see
diff --git a/source/release-notes/4.0-upgrade-replica-set.txt b/source/release-notes/4.0-upgrade-replica-set.txt
@@ -70,8 +70,8 @@ MongoDB 4.0 introduces new hex-encoded string change stream
 
 .. include:: /includes/extracts/changestream-resume-token-versions-4.0.rst
 
-.. admonition:: When upgrading from MongoDB 3.6 to MongoDB 4.0.7 or greater
-   :class: important
+.. important:: When upgrading from MongoDB 3.6 to MongoDB 4.0.7 or greater
+
 
    When upgrading from MongoDB 3.6 to MongoDB 4.0.7 or later, a client
    may try to resume change streams using the new ``v1`` resume token
diff --git a/source/release-notes/4.0-upgrade-sharded-cluster.txt b/source/release-notes/4.0-upgrade-sharded-cluster.txt
@@ -68,8 +68,8 @@ MongoDB 4.0 introduces new hex-encoded string change stream
 
 .. include:: /includes/extracts/changestream-resume-token-versions-4.0.rst
 
-.. admonition:: When upgrading from MongoDB 3.6 to MongoDB 4.0.7
-   :class: important
+.. important:: When upgrading from MongoDB 3.6 to MongoDB 4.0.7
+
 
    When upgrading from MongoDB 3.6 to MongoDB 4.0.7 or later, the
    upgraded sharded cluster members continue to produce ``v0`` token
diff --git a/source/release-notes/4.2-upgrade-replica-set.txt b/source/release-notes/4.2-upgrade-replica-set.txt
@@ -51,8 +51,8 @@ version 4.0.7.
 
 .. include:: /includes/extracts/changestream-resume-token-versions-4.2-greater.rst
 
-.. admonition:: When upgrading from MongoDB 4.0.6 or earlier to MongoDB |newversion|
-   :class: important
+.. important:: When upgrading from MongoDB 4.0.6 or earlier to MongoDB |newversion|
+
 
    During the upgrade process, a client may try to resume change
    streams using the new ``v1`` resume token when connected to a member
diff --git a/source/tutorial/build-a-geohaystack-index.txt b/source/tutorial/build-a-geohaystack-index.txt
@@ -12,8 +12,8 @@ Create a Haystack Index
    :depth: 1
    :class: singlecol
 
-.. admonition:: Deprecation
-   :class: important
+.. important:: Deprecation
+
 
    .. include:: /includes/extracts/4.4-changes-geo-deprecation.rst
 
diff --git a/source/tutorial/query-a-geohaystack-index.txt b/source/tutorial/query-a-geohaystack-index.txt
@@ -12,8 +12,8 @@ Query a Haystack Index
    :depth: 1
    :class: singlecol
 
-.. admonition:: Deprecation
-   :class: important
+.. important:: Deprecation
+
 
    .. include:: /includes/extracts/4.4-changes-geo-deprecation.rst
    
