Rename rippled server category/concept

2025-11-28 15:45:50 +00:00 · 2022-06-28 03:24:01 -07:00
parent 9cfebc798e
commit a91a2dd4e0
90 changed files with 149 additions and 142 deletions
--- a/content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md
@@ -7,7 +7,7 @@ labels:
 ---
 # Cluster rippled Servers

-If you run multiple [`rippled` servers](the-rippled-server.html) in the same data center, you can configure them in a [cluster](clustering.html) to maximize efficiency. To configure clustering:
+If you run multiple [`rippled` servers](xrpl-servers.html) in the same data center, you can configure them in a [cluster](clustering.html) to maximize efficiency. To configure clustering:

 1. For each of your servers, note the IP address of the server.

--- a/content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md
@@ -8,7 +8,7 @@ labels:
 ---
 # Configure the Peer Crawler

-By default, [`rippled` servers](the-rippled-server.html) provide statistics publicly to anyone who asks using the [peer crawler API](peer-crawler.html), to make it easier to track the health and topology of [the XRP Ledger's peer-to-peer network](consensus-network.html). You can configure your server to provide more or less information, or to reject peer crawler requests entirely. [New in: rippled 1.2.0][]
+By default, [`rippled` servers](xrpl-servers.html) provide statistics publicly to anyone who asks using the [peer crawler API](peer-crawler.html), to make it easier to track the health and topology of [the XRP Ledger's peer-to-peer network](consensus-network.html). You can configure your server to provide more or less information, or to reject peer crawler requests entirely. [New in: rippled 1.2.0][]

 This document contains steps for two options:

--- a/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.ja.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.ja.md
@@ -50,7 +50,7 @@ $ sudo firewall-cmd --add-forward-port=port=51235:proto=tcp:toport=51235

 - **コンセプト:**
  - [ピアプロトコル](peer-protocol.html)
-  - [`rippled`サーバー](the-rippled-server.html)
+  - [`rippled`サーバー](xrpl-servers.html)
 - **チュートリアル:**
  - [容量の計画](capacity-planning.html)
  - [`rippled`サーバーのトラブルシューティング](troubleshoot-the-rippled-server.html)
--- a/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md
@@ -68,7 +68,7 @@ If you are using a hosting service with a virtual firewall (for example, [AWS Se

 - **Concepts:**
    - [Peer Protocol](peer-protocol.html)
-    - [The `rippled` Server](the-rippled-server.html)
+    - [The `rippled` Server](xrpl-servers.html)
 - **Tutorials:**
    - [Capacity Planning](capacity-planning.html)
    - [Troubleshoot the `rippled` Server](troubleshoot-the-rippled-server.html)
--- a/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.ja.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.ja.md
@@ -63,7 +63,7 @@ rippled connect 169.54.2.151 51235

 - **コンセプト:**
  - [ピアプロトコル](peer-protocol.html)
-  - [`rippled`サーバー](the-rippled-server.html)
+  - [`rippled`サーバー](xrpl-servers.html)
 - **チュートリアル:**
  - [容量の計画](capacity-planning.html)
  - [`rippled`サーバーのトラブルシューティング](troubleshoot-the-rippled-server.html)
--- a/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md
@@ -63,7 +63,7 @@ rippled connect 169.54.2.151 51235

 - **Concepts:**
    - [Peer Protocol](peer-protocol.html)
-    - [The `rippled` Server](the-rippled-server.html)
+    - [The `rippled` Server](xrpl-servers.html)
 - **Tutorials:**
    - [Capacity Planning](capacity-planning.html)
    - [Troubleshoot the `rippled` Server](troubleshoot-the-rippled-server.html)
--- a/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.ja.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.ja.md
@@ -39,7 +39,7 @@ labels:

 - **コンセプト:**
  - [ピアプロトコル](peer-protocol.html)
-  - [`rippled`サーバー](the-rippled-server.html)
+  - [`rippled`サーバー](xrpl-servers.html)
 - **チュートリアル:**
  - [容量の計画](capacity-planning.html)
  - [`rippled`サーバーのトラブルシューティング](troubleshoot-the-rippled-server.html)
--- a/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md
+++ b/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md
@@ -39,7 +39,7 @@ To change the maximum number of peers your server allows, complete the following

 - **Concepts:**
    - [Peer Protocol](peer-protocol.html)
-    - [The `rippled` Server](the-rippled-server.html)
+    - [The `rippled` Server](xrpl-servers.html)
 - **Tutorials:**
    - [Capacity Planning](capacity-planning.html)
    - [Troubleshoot the `rippled` Server](troubleshoot-the-rippled-server.html)