Convert admonishments from <Callout /> to standard ::: format

Author: briandoyle81

docs/language/accounts/contracts.mdx

@@ -264,15 +264,17 @@ then the function aborts the program.
 
 When the update succeeded, the function returns the [deployed contract](#deployed-contract).
 
-<Callout type="info">
+:::warning
+
 The `update` function does **not** run the initializer of the contract again.
 
 Updating a contract does **not** change the contract instance and its existing stored data.
 A contract update only changes the code a contract.
 
 Is only possible to update contracts in ways that keep data consistency.
 [Certain restrictions apply](../contract-updatability.md).
-</Callout>
+
+:::
 
 For example, assuming that a contract named `Test` is already deployed to the account,
 and it should be updated with the following contract code:

docs/language/accounts/inbox.mdx

@@ -94,9 +94,11 @@ the function returns `nil`.
 If the borrow type of the capability is not a subtype of the provided type argument,
 the program aborts.
 
-<Callout type="info">
+:::tip
+
 It is only possible to claim a capability once.
-</Callout>
+
+:::
 
 Calling function `claim` function emits an event, `InboxValueClaimed`,
 that includes the address of both the provider and the recipient,

docs/language/accounts/keys.mdx

@@ -120,10 +120,12 @@ For each key of the account, the `forEach` function calls the given callback, pa
 When the callback function returns `true` the iteration continues,
 and when it returns `false`, iteration stops.
 
-<Callout type="warning">
-    The `keys.get` and `keys.forEach` functions include revoked keys,
-    which have the `isRevoked` field set to `true`.
-</Callout>
+:::warning
+
+The `keys.get` and `keys.forEach` functions include revoked keys,
+which have the `isRevoked` field set to `true`.
+
+:::
 
 ```cadence
 access(all)

docs/language/accounts/storage.mdx

@@ -419,14 +419,17 @@ If the callback function returns `false`, the iteration function stops.
 The specific order in which the objects are iterated over is undefined,
 as is the behavior when a path is added or removed from storage.
 
-<Callout type="info">
-    The iteration functions skip broken objects.
+:::warning
 
-    An object could be broken due to invalid types associated with the stored value.
-    For example, the contract for the stored object might have syntactic or semantic errors.
-</Callout>
+The iteration functions skip broken objects.
+
+An object could be broken due to invalid types associated with the stored value.
+For example, the contract for the stored object might have syntactic or semantic errors.
+
+:::
+
+:::warning
 
-<Callout type="warning">
 The order of iteration is undefined. Do not rely on any particular behavior.
 
 Saving an object to a path or loading an object from storage during iteration
@@ -458,7 +461,7 @@ account.storage.forEachStored(fun (path: StoragePath, type: Type): Bool {
 })
 ```
 
-</Callout>
+:::
 
 ## Storage limit
 

docs/language/built-in-functions.mdx

@@ -61,13 +61,13 @@ and [FLIP120](https://github.com/onflow/flips/pull/120) for more details.
 
 Nevertheless, developers need to be mindful to use `revertibleRandom()` correctly:
 
-<Callout type="warning">
+:::warning
 
 A transaction can atomically revert all its action.
 It is possible for a transaction submitted by an untrusted party
 to post-select favorable results and revert the transaction for unfavorable results.
 
-</Callout>
+:::
 
 The function usage remains safe when called by a trusted party that does not
 perform post-selection on the returned random numbers.

docs/language/glossary.mdx

@@ -4,9 +4,11 @@ sidebar_position: 32
 ---
 
 
-<Callout type="info">
+:::tip
+
 Tip: <kbd>CTRL</kbd>/<kbd>⌘</kbd> + <kbd>F</kbd> and type in the symbol or operator you want to look up.
-</Callout>
+
+:::
 
 ## `&` (ampersand)
 

docs/language/interfaces.mdx

@@ -458,11 +458,11 @@ shape.area  // is `54`
 
 ## Interface Nesting
 
-<Callout type="info">
+:::warning[🚧 Status]
 
-🚧 Status: Currently only contracts and contract interfaces support nested interfaces.
+Currently only contracts and contract interfaces support nested interfaces.
 
-</Callout>
+:::
 
 Interfaces can be arbitrarily nested.
 Declaring an interface inside another does not require implementing types

docs/language/references.mdx

@@ -414,9 +414,11 @@ let r2 <- r
 ref.id = 2
 ```
 
-<Callout type="info">
+:::tip
+
 Invalidations of storage references are not statically caught, but only at run-time.
-</Callout>
+
+:::
 
 ## Dereferencing values
 

docs/language/resources.mdx

@@ -604,11 +604,13 @@ id2 != id3  // true
 id3 != id1  // true
 ```
 
-<Callout type="warning">
+:::warning
+
 The details of how the identifiers are generated is an implementation detail.
 
 Do not rely on or assume any particular behaviour in Cadence programs.
-</Callout>
+
+:::
 
 ## Resource Owner
 

docs/language/values-and-types.mdx

@@ -246,12 +246,12 @@ All integer types support the following functions:
 
 ## Fixed-Point Numbers
 
-<Callout type="info">
+:::warning[🚧 Status]
 
-🚧 Status: Currently only the 64-bit wide `Fix64` and `UFix64` types are available.
+Currently only the 64-bit wide `Fix64` and `UFix64` types are available.
 More fixed-point number types will be added in a future release.
 
-</Callout>
+:::
 
 Fixed-point numbers are useful for representing fractional values.
 They have a fixed number of digits after decimal point.