Migrate old callout syntax

docs/infrastructure/configuration/peering/cluster-rippled-servers.md

@@ -45,7 +45,7 @@ If you run multiple [`rippled` servers](../../../concepts/networks-and-servers/i
 
         This defines specific peer servers to which this server should always attempt to maintain a direct peer-to-peer connection.
 
-        **Note:** If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol.
+        {% admonition type="info" name="Note" %}If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol.{% /admonition %}
 
     2. In the `[node_seed]` section, set the server's node seed to one of the `validation_seed` values you generated using the [validation_create method][] in step 2. Each server must use a unique node seed. For example:
 

docs/infrastructure/configuration/peering/configure-a-private-server.md

@@ -60,7 +60,7 @@ To set up a specific server as a private peer, complete the following steps:
     192.168.0.2 51235
     ```
 
-    **Note:** If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol.
+    {% admonition type="info" name="Note" %}If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol.{% /admonition %}
 
 4. If using proxies, cluster them with your private peer and each other.
 

docs/infrastructure/configuration/peering/manually-connect-to-a-specific-peer.md

@@ -10,7 +10,7 @@ labels:
 
 Use these steps to manually connect your server to a specific [peer](../../../concepts/networks-and-servers/peer-protocol.md) in the XRP Ledger network.
 
-**Tip:** If you want to make sure your server automatically connects to this server on startup and remains connected later, you may want to configure a [peer reservation](use-a-peer-reservation.md) for that peer.
+{% admonition type="success" name="Tip" %}If you want to make sure your server automatically connects to this server on startup and remains connected later, you may want to configure a [peer reservation](use-a-peer-reservation.md) for that peer.{% /admonition %}
 
 
 ## Prerequisites

docs/infrastructure/configuration/peering/set-max-number-of-peers.md

@@ -10,7 +10,7 @@ labels:
 
 The `rippled` server has a configurable soft maximum number of [peers](../../../concepts/networks-and-servers/peer-protocol.md) to connect to. The default maximum number of peers is **21**.
 
-**Note:** Internally, the server generates approximate quotas of incoming and outgoing peers. You can potentially go over the soft maximum if you are using [fixed peers, peer reservations](../../../concepts/networks-and-servers/peer-protocol.md#fixed-peers-and-peer-reservations), or if you manually connect to additional peers using the [connect method][].
+{% admonition type="info" name="Note" %}Internally, the server generates approximate quotas of incoming and outgoing peers. You can potentially go over the soft maximum if you are using [fixed peers, peer reservations](../../../concepts/networks-and-servers/peer-protocol.md#fixed-peers-and-peer-reservations), or if you manually connect to additional peers using the [connect method][].{% /admonition %}
 
 To change the maximum number of peers your server allows, complete the following steps:
 
@@ -33,7 +33,7 @@ To change the maximum number of peers your server allows, complete the following
 
     If the `[peers_max]` value is less than 10, the server still allows a hardcoded minimum of 10 outgoing peers so that it can maintain connectivity with the network. To block all outgoing peer connections, [configure the server as a private peer](../server-modes/run-rippled-as-a-validator.md#connect-using-proxies) instead.
 
-    **Caution:** The more peer servers you are connected to, the more network bandwidth your `rippled` server uses. You should only configure large numbers of peer servers if your `rippled` server has a good network connection and you can afford the costs you may incur for the bandwidth it uses.
+    {% admonition type="warning" name="Caution" %}The more peer servers you are connected to, the more network bandwidth your `rippled` server uses. You should only configure large numbers of peer servers if your `rippled` server has a good network connection and you can afford the costs you may incur for the bandwidth it uses.{% /admonition %}
 
 3. Restart the `rippled` server.
 

docs/infrastructure/configuration/peering/use-a-peer-reservation.md

@@ -36,7 +36,7 @@ The administrator of the stock server completes this step.
 
 If you have already configured your server with a permanent node key pair value, you can skip ahead to [step 2: Communicate your node public key to the peer's admin](#2-communicate-the-stock-servers-node-public-key). (For example, setting up a permanent node key pair for each server is part of the process of [setting up a server cluster](cluster-rippled-servers.md).)
 
-**Tip:** Setting up a permanent node key pair is optional, but makes it easier to keep the peer reservation set up if you need to erase your server's databases or move to a new machine. If you don't want to set up a permanent node key pair, you can use your server's automatically-generated node public key as reported in the `pubkey_node` field of the [server_info method][] response.
+{% admonition type="success" name="Tip" %}Setting up a permanent node key pair is optional, but makes it easier to keep the peer reservation set up if you need to erase your server's databases or move to a new machine. If you don't want to set up a permanent node key pair, you can use your server's automatically-generated node public key as reported in the `pubkey_node` field of the [server_info method][] response.{% /admonition %}
 
 1. Generate a new, random key pair using the [validation_create method][]. (Omit the `secret` value.)
 
@@ -76,7 +76,7 @@ If you have already configured your server with a permanent node key pair value,
     ssZkdwURFMBXenJPbrpE14b6noJSu
     ```
 
-    **Warning:** All servers should have unique `[node_seed]` values. If you copy your config file to another server, be sure to remove or change the `[node_seed]` value. Keep your `[node_seed]` secret; if a malicious actor gains access to this value, they could use it to impersonate your server in XRP Ledger peer-to-peer communications.
+    {% admonition type="danger" name="Warning" %}All servers should have unique `[node_seed]` values. If you copy your config file to another server, be sure to remove or change the `[node_seed]` value. Keep your `[node_seed]` secret; if a malicious actor gains access to this value, they could use it to impersonate your server in XRP Ledger peer-to-peer communications.{% /admonition %}
 
 4. Restart your `rippled` server:
 
@@ -107,7 +107,7 @@ Connecting to 127.0.0.1:5005
 }
 ```
 
-**Tip:** The description is an optional field that you can provide to add a human-readable note about who this reservation is for.
+{% admonition type="success" name="Tip" %}The description is an optional field that you can provide to add a human-readable note about who this reservation is for.{% /admonition %}
 
 ### 4. Communicate the hub server's current IP address and peer port
 
@@ -165,7 +165,7 @@ As a server administrator, you can manage the reservations your server has for o
 - Remove one of your reservations using the [peer_reservations_del method][].
 - Check which peers are currently connected and how much bandwidth they have used, using the [peers method][].
 
-**Tip:** Although there is no API method to immediately disconnect from an unwanted peer, you can use a software firewall such as `firewalld` to block an unwanted peer from connecting to your server. For examples, see the community-contributed [rbh script](https://github.com/gnanderson/rbh). <!-- SPELLING_IGNORE: rbh -->
+{% admonition type="success" name="Tip" %}Although there is no API method to immediately disconnect from an unwanted peer, you can use a software firewall such as `firewalld` to block an unwanted peer from connecting to your server. For examples, see the community-contributed [rbh script](https://github.com/gnanderson/rbh). <!-- SPELLING_IGNORE: rbh -->{% /admonition %}
 
 
 ## See Also