Updated admonitions

Author: anthonydiscord

docs/components/overview.mdx

@@ -19,8 +19,9 @@ All components are customizable and can be organized using layout components to
 
 To use components, messages must be sent with the `IS_COMPONENTS_V2` flag (`1<<15`). Note that using this flag disables traditional content and embeds - all content must be sent as components instead.
 
-> info
-> [Legacy message component behavior](/docs/components/reference#legacy-message-component-behavior) will **not** be deprecated and will continue to be available to your apps on a message-by-message basis. However, we recommend using the new components for new projects and features.
+:::info
+[Legacy message component behavior](/docs/components/reference#legacy-message-component-behavior) will **not** be deprecated and will continue to be available to your apps on a message-by-message basis. However, we recommend using the new components for new projects and features.
+:::
 
 <Container>
   <Card title="Using Message Components" link="/docs/components/using-message-components" icon="ChatDotsIcon">

docs/components/reference.mdx

@@ -16,8 +16,9 @@ To use these components, you need to send the [message flag](/docs/resources/mes
 - Attachments won't show by default - they must be exposed through components
 - The `poll` and `stickers` fields are disabled
 
-> info
-> [Legacy component behavior](/docs/components/reference#legacy-message-component-behavior) will continue to work but provide less flexibility and control over the message layout.
+:::info
+[Legacy component behavior](/docs/components/reference#legacy-message-component-behavior) will continue to work but provide less flexibility and control over the message layout.
+:::
 
 For a practical guide on implementing these components, see our [Using Message Components](/docs/components/using-message-components) and [Using Modal Components](/docs/components/using-modal-components) documentation.
 
@@ -485,8 +486,9 @@ String Selects must be placed inside an [Action Row](/docs/components/reference#
 
 The `resolved` object is included in interaction payloads for user, role, mentionable, and channel select menu components. `resolved` contains a nested object with additional details about the selected options with the key of the resource type—`users`, `roles`, `channels`, and `members`.
 
-> info
-> `members` and `users` may both be present in the `resolved` object when a user is selected (in either a [user select](/docs/components/reference#user-select) or [mentionable select](/docs/components/reference#mentionable-select)).
+:::info
+`members` and `users` may both be present in the `resolved` object when a user is selected (in either a [user select](/docs/components/reference#user-select) or [mentionable select](/docs/components/reference#mentionable-select)).
+:::
 
 ###### Example Resolved Object
 
@@ -823,8 +825,9 @@ A Section is a top-level layout component that allows you to join text contextua
 
 Sections are only available in messages.
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::
 
 ###### Section Structure
 
@@ -835,8 +838,9 @@ Sections are only available in messages.
 | components | array of [text display components](/docs/components/reference#text-display)                                           | One to three text components                                                                      |
 | accessory  | [thumbnail component](/docs/components/reference#thumbnail) or [button components](/docs/components/reference#button) | A thumbnail or a button component, with a future possibility of adding more compatible components |
 
-> info
-> Don't hardcode `components` to contain only text components. We may add other components in the future. Similarly, `accessory` may be expanded to include other components in the future.
+:::info
+Don't hardcode `components` to contain only text components. We may add other components in the future. Similarly, `accessory` may be expanded to include other components in the future.
+:::
 
 ###### Example
 
@@ -876,8 +880,9 @@ A Text Display is a top-level content component that allows you to add text to y
 
 Text Displays are only available in messages.
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::
 
 ###### Text Display Structure
 
@@ -906,8 +911,9 @@ A Thumbnail is a content component that is a small image only usable as an acces
 
 Thumbnails are only available in messages as an accessory in a [section](/docs/components/reference#section).
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2), which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2), which can be activated on a per-message basis.
+:::
 
 ###### Thumbnail Structure
 
@@ -929,8 +935,9 @@ A Media Gallery is a top-level content component that allows you to display 1-10
 
 Media Galleries are only available in messages.
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::
 
 ###### Media Gallery Structure
 
@@ -982,8 +989,9 @@ Media Galleries are only available in messages.
 
 A File is a top-level component that allows you to display an uploaded file as an attachment to the message and reference it in the component. This is similar to the `embeds` field of a message but allows you to control the layout of your message by using this anywhere as a component. Files are only available in messages.
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::
 
 ###### File Structure
 
@@ -1033,8 +1041,9 @@ A Separator is a top-level layout component that adds vertical padding and visua
 
 Separators are only available in messages.
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::
 
 ###### Separator Structure
 
@@ -1073,8 +1082,9 @@ A Container is a top-level layout component that holds up to 10 components. Cont
 
 Containers are only available in messages.
 
-> info
-> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::info
+To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
+:::
 
 ###### Container Structure
 

docs/components/using-modal-components.mdx

@@ -8,8 +8,9 @@ sidebar_label: Using Modal Components
 
 Modal components are a great way to collect freeform information from your users. 
 
-> info
-> Currently, only [Text Input](/docs/components/reference#text-input) fields are supported in a modal, and each one must be placed in an [Action Row](/docs/components/reference#action-row).
+:::info
+Currently, only [Text Input](/docs/components/reference#text-input) fields are supported in a modal, and each one must be placed in an [Action Row](/docs/components/reference#action-row).
+:::
 
 ### Prerequisites