Updated outdated alert boxes to the new format

Author: GeniusTimo

docs/resources/emoji.md

@@ -68,11 +68,13 @@ The `user` field of an app emoji object represents the team member that uploaded
 
 ###### Custom Emoji Examples
 
->info
->In `MESSAGE_REACTION_ADD`, `MESSAGE_REACTION_REMOVE` and `MESSAGE_REACTION_REMOVE_EMOJI` gateway events `animated` will be returned for animated emoji.
+:::info
+In `MESSAGE_REACTION_ADD`, `MESSAGE_REACTION_REMOVE` and `MESSAGE_REACTION_REMOVE_EMOJI` gateway events `animated` will be returned for animated emoji.
+:::
 
->info
->In `MESSAGE_REACTION_ADD` and `MESSAGE_REACTION_REMOVE` gateway events `name` may be `null` when custom emoji data is not available (for example, if it was deleted from the guild).
+:::info
+In `MESSAGE_REACTION_ADD` and `MESSAGE_REACTION_REMOVE` gateway events `name` may be `null` when custom emoji data is not available (for example, if it was deleted from the guild).
+:::
 
 ```json
 {

docs/topics/voice-connections.mdx

@@ -8,8 +8,9 @@ To ensure that you have the most up-to-date information, please use [version 8](
 
 Previously if the version query string `v` was omitted the voice gateway would default to version 1. That behavior is being deprecated, in the future you must present a voice gateway version or your voice connection will be rejected.
 
->warn
->Versions below 4 as well as the default version behaviour will be discontinued as of November 18th, 2024. Connections without a version or with a version less than version 4 will be rejected as of this date.
+:::warn
+Versions below 4 as well as the default version behaviour will be discontinued as of November 18th, 2024. Connections without a version or with a version less than version 4 will be rejected as of this date.
+:::
 
 ###### Gateway Versions
 
@@ -211,8 +212,9 @@ First, we open a UDP connection to the IP and port provided in the Ready payload
 
 Since September 2024, Discord is migrating voice and video in DMs, Group DMs, voice channels, and Go Live streams to use end-to-end encryption (E2EE).
 
->info
->You are not immediately required to support the E2EE protocol, as calls will automatically upgrade/downgrade to/from E2EE depending on the support of clients in the call. Non-E2EE connections to voice in DMs, Group DMs, voice channels, and Go Live streams will soon be deprecated and will be discontinued (after at least a six month deprecation window).
+:::info
+You are not immediately required to support the E2EE protocol, as calls will automatically upgrade/downgrade to/from E2EE depending on the support of clients in the call. Non-E2EE connections to voice in DMs, Group DMs, voice channels, and Go Live streams will soon be deprecated and will be discontinued (after at least a six month deprecation window).
+:::
 
 This section is a high-level overview of how to support Discord's audio & video end-to-end encryption (DAVE) protocol, centered around the voice gateway opcodes necessary for the protocol. The most thorough documentation on the DAVE protocol is found in the [Protocol Whitepaper](https://daveprotocol.com). You may additionally be able to leverage or refer to our open-source library [libdave](https://github.com/discord/libdave) to assist your implementation. The exact format of the DAVE protocol opcodes is detailed in the [Voice Gateway Opcodes section of the protocol whitepaper](https://daveprotocol.com/#voice-gateway-opcodes).
 
@@ -236,8 +238,9 @@ Include the highest DAVE protocol version you support in [Opcode 0 Identify](/do
 
 The voice gateway specifies the initial protocol version in [Opcode 4 Session Description](/docs/topics/opcodes-and-status-codes#voice) under `dave_protocol_version`. This may be any non-discontinued protocol version equal to or less than your supported protocol version.
 
->warn
->Clients must retain backwards-compatibility of any non-discontinued DAVE protocol versions. The voice gateway selects the lowest shared protocol version for the call.
+:::warn
+Clients must retain backwards-compatibility of any non-discontinued DAVE protocol versions. The voice gateway selects the lowest shared protocol version for the call.
+:::
 
 ### Protocol Transitions
 
@@ -397,11 +400,13 @@ Voice data sent to discord should be encoded with [Opus](https://www.opus-codec.
 | XSalsa20 Poly1305 Suffix           | xsalsa20_poly1305_suffix        | 24 random bytes                                       | Deprecated            |
 | XSalsa20 Poly1305 Lite             | xsalsa20_poly1305_lite          | 32-bit incremental integer value, appended to payload | Deprecated            |
 
->warn 
->The deprecated encryption modes above will be discontinued as of November 18th, 2024. As of this date the voice gateway will not allow you to connect with one of the deprecated encryption modes.
+:::warn 
+The deprecated encryption modes above will be discontinued as of November 18th, 2024. As of this date the voice gateway will not allow you to connect with one of the deprecated encryption modes.
+:::
 
->warn
->The nonce has to be stripped from the payload before encrypting and before decrypting the audio data
+:::warn
+The nonce has to be stripped from the payload before encrypting and before decrypting the audio data
+:::
 
 The RTP size variants determine the unencrypted size of the RTP header in [the same way as SRTP](https://tools.ietf.org/html/rfc3711#section-3.1), which considers CSRCs and (optionally) the extension preamble to be part of the unencrypted header. The deprecated variants use a fixed size unencrypted header for RTP.