(DOCSP-12280): Convert generic admonitions to named admonitions

Author: nlarew

source/android/access-custom-user-data.txt

@@ -85,8 +85,7 @@ method on the ``User`` object of a logged in user:
             }
          });
 
-.. admonition:: Custom Data May Be Stale
-   :class: warning
+.. warning:: Custom Data May Be Stale
 
    {+backend+} does not dynamically update the value of
    :java-sdk:`User.customData() <io/realm/mongodb/User.html#getCustomData-->`

source/android/collections.txt

@@ -78,8 +78,7 @@ collection in your view class, then read the results
 collection as needed without having to refresh it or
 validate that it is up-to-date.
 
-.. admonition:: Indexes may change
-   :class: important
+.. important:: Indexes may change
 
    Since results update themselves automatically, do not
    store the positional index of an object in the collection
@@ -159,8 +158,7 @@ are determined by a query.
 
 .. _android-collection-type-for-implicit-inverse-relationships:
 
-.. admonition:: Inverse one-to-many relationship property exception
-   :class: note
+.. note:: Inverse one-to-many relationship property exception
 
    Since {+client-database+} automatically determines the contents of
    :ref:`implicit inverse relationship

source/android/embedded-objects.txt

@@ -29,8 +29,7 @@ exist as an independent Realm object. Realm automatically deletes
 embedded objects if their parent object is deleted or when overwritten
 by a new embedded object instance.
 
-.. admonition:: Realm Uses Cascading Deletes for Embedded Objects
-   :class: note
+.. note:: Realm Uses Cascading Deletes for Embedded Objects
 
    When you delete a Realm object, Realm automatically deletes any
    embedded objects referenced by that object. Any objects that your

source/android/init-realmclient.txt

@@ -43,8 +43,7 @@ Pass the {+app+} ID for your {+app+}, which you can find in the {+ui+}.
             Realm.init(this) // `this` is a Context, typically an Application or Activity
             val app: App = App(AppConfiguration.Builder(appID).build())
 
-.. admonition:: Initialize the App before Creating an Instance
-   :class: important
+.. important:: Initialize the App before Creating an Instance
 
    You must initialize your {+service-short+} app connection with
    ``Realm.init()`` before creating any instance of an ``App``.

source/android/install.txt

@@ -36,8 +36,7 @@ Installation
 {+service+} supports the Gradle build system. Follow these steps
 to add the {+service+} Android SDK to your project.
 
-.. admonition:: A note on ProGuard
-   :class: note
+.. note:: A note on ProGuard
 
    Because {+service+} provides a ProGuard configuration as part
    of the {+service+} library, you do not need to add any

source/android/notifications.txt

@@ -101,8 +101,7 @@ indices:
 - The indices of the objects that were inserted.
 - The indices of the objects that were modified.
 
-.. admonition:: Order Matters
-   :class: important
+.. important:: Order Matters
 
    In collection notification handlers, always apply changes
    in the following order: deletions, insertions, then

source/android/query-engine.txt

@@ -40,8 +40,7 @@ An **expression** consists of one of the following:
 - An operator and up to two argument expression(s).
 - A literal string, number, or date.
 
-.. admonition:: About the examples on this page
-   :class: note
+.. note:: About the examples on this page
 
    The examples in this page use a simple data set for a
    task list app. The two Realm object types are ``Project``

source/android/quick-start.txt

@@ -22,8 +22,7 @@ integrated into your app. Before you begin, ensure you have:
 - :ref:`Enabled {+sync+} <enable-sync>`
 - :ref:`Installed the Android SDK <android-install>`
 
-.. admonition:: Check Out the Tutorial
-   :class: note
+.. note:: Check Out the Tutorial
 
    This page contains only the essential information that you need to set up a
    MongoDB Realm application. If you prefer to follow a guided tutorial that
@@ -85,8 +84,7 @@ access your {+app+} using your {+app+} ID. You can find your {+app+} ID in the
          val app: App = App(AppConfiguration.Builder(appID)
                .build())
 
-.. admonition:: Android Studio Errors?
-   :class: note
+.. note:: Android Studio Errors?
 
    If Android Studio does not recognize the ``Realm``, ``App``, or
    ``AppConfiguration`` types, there could be a problem with the

source/android/reads.txt

@@ -41,8 +41,7 @@ All query, filter, and sort operations return a
 collections are live, meaning they always contain the latest
 results of the associated query.
 
-.. admonition:: About the examples on this page
-   :class: note
+.. note:: About the examples on this page
 
    The examples on this page use the data model of a project
    management app that has two {+service-short+} object types: ``Project``
@@ -245,4 +244,3 @@ Summary
 - To read from {+client-database+}, first get all objects of a certain type from the {+realm+}, then filter using the query engine, then (optionally) sort the results.
 - When you read, the results are not copies. Instead, through memory mapping, results point directly to the version on disk.
 - Queries are lazily-evaluated.
-

source/android/realms.txt

@@ -112,8 +112,7 @@ in the {+realm+} configuration when you open a {+realm+}. If a client
 application does not specify a version number when it opens a {+realm+} then
 the {+realm+} defaults to version ``0``.
 
-.. admonition:: Increment Versions Monotonically
-   :class: important
+.. important:: Increment Versions Monotonically
 
    :ref:`Migrations <android-client-migrations>` must update
    a {+realm+} to a higher schema version.

source/android/sync-data.txt

@@ -64,8 +64,7 @@ The syntax to :ref:`read <android-realm-database-reads>`, :ref:`write
 synced {+realm+} is identical to the syntax for non-synced {+realms+}. While you work with
 local data, a background thread efficiently integrates, uploads, and downloads changesets.
 
-.. admonition:: When Using Sync, Avoid Writes on the Main Thread
-   :class: important
+.. important:: When Using Sync, Avoid Writes on the Main Thread
 
    The fact that {+service-short+} performs sync integrations on a background thread means
    that if you write to your {+realm+} on the main thread, there's a small chance your UI

source/android/threading.txt

@@ -175,8 +175,7 @@ spawned them stays open. Therefore, avoid closing the live
 {+realm+} until all threads are done with the frozen objects.
 You can close frozen {+realm+} before the live {+realm+} is closed.
 
-.. admonition:: On caching frozen objects
-   :class: important
+.. important:: On caching frozen objects
 
    Caching too many frozen objects can have a negative
    impact on the {+realm+} file size. "Too many" depends on your
@@ -243,8 +242,7 @@ relevant part of the tree. Likewise, the {+realm+}'s root
 pointer will point to the original version until the new
 version is guaranteed to be valid.
 
-.. admonition:: Diagram
-   :class: note
+.. note:: Diagram
 
    The following diagram illustrates the commit process:
 

source/android/writes.txt

@@ -28,9 +28,8 @@ words, a transaction is *all or nothing*: either all of the
 operations in the transaction succeed or none of the
 operations in the transaction take effect.
 
-.. admonition:: Remember
-   :class: note
-
+.. note::
+   
    All writes must happen in a transaction.
 
 A {+realm+} allows only one open transaction at a time. {+client-database+}
@@ -73,8 +72,7 @@ the code in the callback throws an exception when {+client-database+} runs
 it, {+client-database+} cancels the transaction. Otherwise, {+client-database+} commits
 the transaction immediately after the callback.
 
-.. admonition:: Concurrency Concerns
-   :class: important
+.. important:: Concurrency Concerns
 
    Since transactions block each other, it is best to avoid
    opening transactions on both the UI thread and a
@@ -260,8 +258,7 @@ transaction.
 With the Java SDK, call ``deleteFromRealm()`` on the
 instance itself.
 
-.. admonition:: Do not use objects after delete
-   :class: important
+.. important:: Do not use objects after delete
 
    {+client-database+} throws an error if you try to use an object after
    it has been deleted.

source/authentication.txt

@@ -62,8 +62,7 @@ accepts JSON web tokens signed by the external system and
 the :doc:`Custom Function </authentication/custom-function>`
 provider allows you to define custom logic in a :term:`{+service-short+} Function`.
 
-.. admonition:: User Authentication is Required
-   :class: important
+.. important:: User Authentication is Required
 
    Every application must have at least one authentication provider
    configured and enabled before any client application can successfully
@@ -86,8 +85,7 @@ allows you to associate each user with :doc:`custom data
 </users/enable-custom-user-data>` stored in a collection
 of your :term:`linked {+atlas+} data source <data source>`.
 
-.. admonition:: Link Multiple Identities to One User Account
-   :class: note
+.. note:: Link Multiple Identities to One User Account
 
    When a user authenticates with a provider for the first
    time, {+backend+} creates a new account and associates the
@@ -156,8 +154,7 @@ to circumvent rules and queries that need :doc:`unrestricted
 access </mongodb/service-limitations>` to MongoDB
 CRUD and aggregation operations.
 
-.. admonition:: Security Warning
-   :class: important
+.. important:: Security Warning
 
    Rules do not apply to the system user, which means that
    Functions and webhooks that run as the :term:`system user`

source/authentication/anonymous.txt

@@ -45,8 +45,7 @@ different authentication provider. See :doc:`linking
 </authentication/linking>` for more information on how to accomplish
 this.
 
-.. admonition:: Anonymous user expiration
-   :class: important
+.. important:: Anonymous user expiration
 
    {+service-short+} may delete an Anonymous user object that is 90 days old (or
    older). When an account is deleted, it is not recoverable and any

source/authentication/custom-function.txt

@@ -30,8 +30,7 @@ with the Custom Function provider. You can use the function to
 coordinate with an external authentication system and/or use data that
 you store in MongoDB to identify and authenticate users.
 
-.. admonition:: Validate and Authenticate Custom Function Users
-   :class: important
+.. important:: Validate and Authenticate Custom Function Users
 
    {+service-short+} does not perform any data validation or authentication
    checks for the Custom Function provider. Make sure that you validate

source/authentication/email-password.txt

@@ -127,8 +127,7 @@ confirmation email:
   if omitted, {+service-short+} uses a default subject line instead. Custom email
   confirmation subjects can contain a maximum of 256 characters.
 
-.. admonition:: Use Deep Links in Mobile Apps
-   :class: note
+.. note:: Use Deep Links in Mobile Apps
 
    Mobile applications can handle email confirmation directly in the app
    by configuring `deep linking <https://developer.android.com/training/app-links/deep-linking.html>`_
@@ -303,8 +302,7 @@ password reset email:
   subject line instead. Custom password reset subjects can contain a
   maximum of 256 characters.
 
-.. admonition:: Use Deep Links in Mobile Apps
-   :class: note
+.. note:: Use Deep Links in Mobile Apps
 
    Mobile applications can handle password resets directly in the app
    by configuring `deep linking

source/billing.txt

@@ -31,8 +31,7 @@ how much you pay each month:
 - :ref:`Data Transfer <billing-data-transfer>`, which measures the amount of
   data that {+service+} sends to external services and client applications.
 
-.. admonition:: Track Your Usage
-   :class: note
+.. note:: Track Your Usage
 
    You can track an application's usage for the current month from the
    application dashboard in the {+ui+}.
@@ -111,8 +110,7 @@ types of request:
 hours of :ref:`compute <billing-compute>` **or** 10,000 hours of :ref:`sync
 <billing-sync>` runtime (whichever occurs first)
 
-.. admonition:: Estimate Your Usage
-   :class: admonition-example
+.. example:: Estimate Your Usage
 
    Consider answering the following questions to help estimate the number of
    requests that your application will receive each month.
@@ -154,8 +152,7 @@ and increases by 1 for every 32MB of memory that a given request uses.
 hours of :ref:`compute <billing-compute>` **or** 10,000 hours of :ref:`sync
 <billing-sync>` runtime (whichever occurs first)
 
-.. admonition:: Estimate Your Usage
-   :class: admonition-example
+.. example:: Estimate Your Usage
 
    Consider answering the following questions to help estimate the amount of
    compute time that your application will use each month.
@@ -192,8 +189,7 @@ millisecond of sync runtime per user.
 hours of :ref:`compute <billing-compute>` **or** 10,000 hours of :ref:`sync
 <billing-sync>` runtime (whichever occurs first)
 
-.. admonition:: Estimate Your Usage
-   :class: admonition-example
+.. example:: Estimate Your Usage
 
    Consider answering the following questions to help estimate the amount of
    sync time that your application will use each month.
@@ -218,14 +214,12 @@ set rate for each gigabyte of data egress.
 
 **Free Tier Threshold:** 10GB
 
-.. admonition:: MongoDB Atlas Data Transfer
-   :class: note
+.. note:: MongoDB Atlas Data Transfer
 
    {+service+} does not bill for data transfer to and from a linked
    MongoDB Atlas data source.
 
-.. admonition:: Estimate Your Usage
-   :class: admonition-example
+.. example:: Estimate Your Usage
 
    Consider answering the following questions to help estimate the amount of
    data that your application will transfer each month.
@@ -293,8 +287,7 @@ one month:
    * - **TOTAL**
      - $55.60 (requests) + $0.33 (sync) + $3.98 (data transfer) = **$59.91 / month**
 
-.. admonition:: Free Tier Usage
-   :class: note
+.. note:: Free Tier Usage
 
    The way that free tier usage affects your bill depends on your consumption
    each month. For this example, we assume that all requests and activity are
@@ -367,8 +360,7 @@ one month:
    * - **TOTAL**
      - $0.44 (requests) + $0.47 (compute) + $0 (data transfer) = **$0.91 / month**
 
-.. admonition:: Free Tier Usage
-   :class: note
+.. note:: Free Tier Usage
 
    The way that free tier usage affects your bill depends on your consumption
    each month. For this example, we assume that all requests and activity are
@@ -444,8 +436,7 @@ restaurants. The app has the following usage:
    * - **TOTAL**
      - $0.48 (requests) + $0.34 (compute) + $0 (data transfer) = **$0.82 / month**
 
-.. admonition:: Free Tier Usage
-   :class: note
+.. note:: Free Tier Usage
 
    The way that free tier usage affects your bill depends on your consumption
    each month. For this example, we assume that all requests and activity are

source/dotnet/collections.txt

@@ -77,8 +77,7 @@ collection in your view class, then read the results
 collection as needed without having to refresh it or
 validate that it is up-to-date.
 
-.. admonition:: Indexes may change
-   :class: important
+.. important:: Indexes may change
 
    Since results update themselves automatically, do not
    store the positional index of an object in the collection
@@ -158,8 +157,7 @@ are determined by a query.
 
 .. _dotnet-collection-type-for-implicit-inverse-relationships:
 
-.. admonition:: Inverse one-to-many relationship property exception
-   :class: note
+.. note:: Inverse one-to-many relationship property exception
 
    Since {+client-database+} automatically determines the contents of
    :ref:`implicit inverse relationship

source/dotnet/notifications.txt

@@ -94,8 +94,7 @@ indices:
 - The indices of the objects that were inserted.
 - The indices of the objects that were modified.
 
-.. admonition:: Order Matters
-   :class: important
+.. important:: Order Matters
 
    In collection notification handlers, always apply changes
    in the following order: deletions, insertions, then

source/dotnet/query-engine.txt

@@ -40,8 +40,7 @@ An **expression** consists of one of the following:
 - An operator and up to two argument expression(s).
 - A literal string, number, or date.
 
-.. admonition:: About the examples on this page
-   :class: note
+.. note:: About the examples on this page
 
    The examples in this page use a simple data set for a
    task list app. The two Realm object types are ``Project``

source/dotnet/reads.txt

@@ -41,8 +41,7 @@ All query, filter, and sort operations return a
 collections are live, meaning they always contain the latest
 results of the associated query.
 
-.. admonition:: About the examples on this page
-   :class: note
+.. note:: About the examples on this page
 
    The examples on this page use the data model of a project
    management app that has two {+service-short+} object types: ``Project``
@@ -221,4 +220,3 @@ Summary
 - To read from {+client-database+}, first get all objects of a certain type from the {+realm+}, then filter using the query engine, then (optionally) sort the results.
 - When you read, the results are not copies. Instead, through memory mapping, results point directly to the version on disk.
 - Queries are lazily-evaluated.
-