Fix configure-peering links

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](xrpl-servers.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 in the same data center, you can configure them in a cluster to maximize efficiency. To configure clustering:
 
 1. For each of your servers, note the IP address of the server.
 
@@ -40,7 +40,7 @@ If you run multiple [`rippled` servers](xrpl-servers.html) in the same data cent
 
         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](peer-protocol.html). [New in: rippled 1.6.0][]
+        **Note:** If you omit the port number, the server uses port 2459, the IANA-assigned port for the [XRP Ledger protocol](peer-protocol.html).
 
     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:
 

content/tutorials/manage-the-rippled-server/configure-peering/configure-a-private-server.md

@@ -8,13 +8,13 @@ labels:
 ---
 # Configure a Private Server
 
-A [private server](peer-protocol.html#private-peers) is a `rippled` server that connects to the network only through specific, trusted peers instead of connecting directly to discovered peers in the open peer-to-peer network. This kind of configuration is an optional precaution most commonly recommended for [validators](run-rippled-as-a-validator.html), but it can be useful for other specific purposes.
+A private server is a `rippled` server that connects to the network only through specific, trusted peers instead of connecting directly to discovered peers in the open peer-to-peer network. This kind of configuration is an optional precaution most commonly recommended for validators, but it can be useful for other specific purposes.
 
 ## Prerequisites
 
 To use a private server, you must meet the following requirements:
 
-- You must have [`rippled` installed](install-rippled.html) and updated to the latest version, but not running yet.
+- You must have `rippled` installed and updated to the latest version, but not running yet.
 - You must decide whether to connect through **proxies** you run yourself, or through **public hubs**. For a comparison of these options, see [Pros and Cons of Peering Configurations](peer-protocol.html#pros-and-cons-of-peering-configurations).
     - If you are using proxies, you must have additional machines with `rippled` installed and running to use as the proxies. These servers must be able to connect to the outside network and to your private server.
     - For either configuration, you must know the IP addresses and ports of the peers you intend to connect to.
@@ -52,13 +52,13 @@ To set up a specific server as a private peer, complete the following steps:
         192.168.0.1 51235
         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](peer-protocol.html). [New in: rippled 1.6.0][]
+    **Note:** If you omit the port number, the server uses port 2459, the IANA-assigned port for the XRP Ledger protocol.
 
 4. If using proxies, cluster them with your private peer and each other.
 
     If you are using public hubs, skip this step.
 
-    If you are using proxies, [configure the proxies as a cluster](cluster-rippled-servers.html) that includes your private peer. Each member of the cluster should have an `[ips_fixed]` stanza that lists each _other_ member of the cluster. However, **only the private server** should have a `[peer_private]` stanza.
+    If you are using proxies, configure the proxies as a cluster that includes your private peer. Each member of the cluster should have an `[ips_fixed]` stanza that lists each _other_ member of the cluster. However, **only the private server** should have a `[peer_private]` stanza.
 
     Restart `rippled` on the proxies one-by-one. On each proxy server:
 
@@ -75,7 +75,7 @@ To set up a specific server as a private peer, complete the following steps:
 
 ## Next Steps
 
-As an additional precaution, you should configure your firewall to block incoming connections to your private server from servers that are not your specific peers. If you are running proxy servers, [forward peer ports](forward-ports-for-peering.html) through your firewall to the proxies, but **not** to the private peer. The exact details of how to configure this depend on what firewall you use.
+As an additional precaution, you should configure your firewall to block incoming connections to your private server from servers that are not your specific peers. If you are running proxy servers, forward peer ports through your firewall to the proxies, but **not** to the private peer. The exact details of how to configure this depend on what firewall you use.
 
 Be sure the firewall **does not block** outgoing HTTP connections on port 80. The default configuration uses this port to download the latest recommended validator list from **vl.ripple.com**. Without a validator list, the server does not know which validators to trust and cannot recognize when the network reaches a consensus.
 

content/tutorials/manage-the-rippled-server/configure-peering/configure-peering.md

@@ -10,4 +10,4 @@ labels:
 
 The XRP Ledger's peer-to-peer protocol automatically manages peer connections in most cases. In some cases, you may want to manually adjust which peers your server connects to, to maximize your server's availability and connectivity with the rest of the network.
 
-If you run multiple servers in the same datacenter, you may want [to cluster them](cluster-rippled-servers.html) to improve efficiency. You can use reserved peer slots for servers you don't run but want to stay connected to, such as important hubs in the topology of the peer-to-peer network. For other peers, the server can automatically find peers and manage its connections, although you may occasionally want to intervene to block a peer that's behaving undesirably.
+If you run multiple servers in the same datacenter, you may want to cluster them to improve efficiency. You can use reserved peer slots for servers you don't run but want to stay connected to, such as important hubs in the topology of the peer-to-peer network. For other peers, the server can automatically find peers and manage its connections, although you may occasionally want to intervene to block a peer that's behaving undesirably.

content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md

@@ -8,12 +8,12 @@ labels:
 ---
 # Configure the Peer Crawler
 
-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][]
+By default, `rippled` servers provide statistics publicly to anyone who asks using the peer crawler API, to make it easier to track the health and topology of the XRP Ledger's peer-to-peer network. You can configure your server to provide more or less information, or to reject peer crawler requests entirely.
 
 This document contains steps for two options:
 
-- [Change the Information Reported by the Peer Crawler](#change-the-information-reported-by-the-peer-crawler)
+- Change the Information Reported by the Peer Crawler
-- [Disable the Peer Crawler](#disable-the-peer-crawler)
+- Disable the Peer Crawler
 
 ## Change the Information Reported by the Peer Crawler
 
@@ -33,7 +33,7 @@ To configure how much information your server provides in response to peer crawl
         counts = 0
         unl = 1
 
-    The fields in this stanza control which fields the server returns in the [peer crawler response](peer-crawler.html#response-format). The names of the config fields match the fields of the API response. A setting with a value of `1` means to include the field in the response. A value of `0` means to omit that field from the response. This example shows the default values for each setting.
+    The fields in this stanza control which fields the server returns in the peer crawler response. The names of the config fields match the fields of the API response. A setting with a value of `1` means to include the field in the response. A value of `0` means to omit that field from the response. This example shows the default values for each setting.
 
 3. After saving the changes to the config file, restart your `rippled` server to apply the updated configuration:
 

content/tutorials/manage-the-rippled-server/configure-peering/enable-link-compression.md

@@ -7,7 +7,7 @@ labels:
 ---
 # Enable Link Compression
 
-The `rippled` server can save bandwidth by compressing its [peer-to-peer communications](peer-protocol.html), at a cost of greater CPU usage. If you enable link compression, the server automatically compresses communications with peer servers that also have link compression enabled. [New in: rippled 1.6.0][]
+The `rippled` server can save bandwidth by compressing its peer-to-peer communications, at a cost of greater CPU usage. If you enable link compression, the server automatically compresses communications with peer servers that also have link compression enabled.
 
 ## Steps
 

content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md

@@ -7,7 +7,7 @@ labels:
 ---
 # Forward Ports for Peering
 
-Servers in the XRP Ledger peer-to-peer network communicate over the [peer protocol](peer-protocol.html). For the best combination of security and connectivity to the rest of the network, you should use a firewall to protect your server from most ports, but open or forward the peer protocol port.
+Servers in the XRP Ledger peer-to-peer network communicate over the peer protocol. For the best combination of security and connectivity to the rest of the network, you should use a firewall to protect your server from most ports, but open or forward the peer protocol port.
 
 While your `rippled` server is running, you can check to see how many peers you have by running the [server_info method][]. The `peers` field of the `info` object shows how many peers are currently connected to your server. If this number is exactly 10 or 11, that usually means your firewall is blocking incoming connections.
 

content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md

@@ -7,17 +7,17 @@ labels:
 ---
 # Manually Connect to a Specific Peer
 
-Use these steps to manually connect your server to a specific [peer](peer-protocol.html) in the XRP Ledger network.
+Use these steps to manually connect your server to a specific peer 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.html) for that peer.
+**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 for that peer.
 
 
 ## Prerequisites
 
 - You must know the IP address of the peer you want to connect to.
-- You must know what port the peer you want to connect to uses for the XRP Ledger [peer protocol](peer-protocol.html). The default config file uses port 51235.
+- You must know what port the peer you want to connect to uses for the XRP Ledger peer protocol. The default config file uses port 51235.
-- You must have a network connection from your server to the peer. For example, the peer server must [forward the appropriate port through its firewall](forward-ports-for-peering.html).
+- You must have a network connection from your server to the peer. For example, the peer server must forward the appropriate port through its firewall.
-- The peer server must have available peer slots. If the peer is already at its maximum number of peers, you can ask the peer server's operator to add a [peer reservation](use-a-peer-reservation.html) for your server.
+- The peer server must have available peer slots. If the peer is already at its maximum number of peers, you can ask the peer server's operator to add a peer reservation for your server.
 
 ## Steps
 

content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md

@@ -7,9 +7,9 @@ labels:
 ---
 # Set Maximum Number of Peers
 
-The `rippled` server has a configurable soft maximum number of [peers](peer-protocol.html) to connect to. The default maximum number of peers is **21**.
+The `rippled` server has a configurable soft maximum number of [peers](peer-protocol.html) 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](peer-protocol.html#fixed-peers-and-peer-reservations), or if you manually connect to additional peers using the [connect method][].
+**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, or if you manually connect to additional peers using the [connect method][].
 
 To change the maximum number of peers your server allows, complete the following steps:
 
@@ -26,7 +26,7 @@ To change the maximum number of peers your server allows, complete the following
 
     The only content of the stanza should be an integer indicating the total number of peers to allow. By default, the server attempts to maintain a ratio of about 85% incoming and 15% outgoing peers, but with a minimum of 10 outgoing peers, so any value less than 68 won't increase the number of outgoing peer connections your server makes.
 
-    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](run-rippled-as-a-validator.html#connect-using-proxies) instead.
+    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 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.
 

content/tutorials/manage-the-rippled-server/configure-peering/use-a-peer-reservation.md

@@ -9,7 +9,7 @@ labels:
 
 A [peer reservation][] is a setting that makes a `rippled` server always accept connections from a peer matching the reservation. This page describes how to use peer reservations to keep a consistent peer-to-peer connection between two servers, with the cooperation of the administrators of both servers.
 
-Peer reservations are most useful when the two servers are run by different parties, and the server that receives the incoming connection is a [hub server](rippled-server-modes.html#public-hubs) with many peers. For clarity, these instructions use the following terms:
+Peer reservations are most useful when the two servers are run by different parties, and the server that receives the incoming connection is a hub server with many peers. For clarity, these instructions use the following terms:
 
 - The server making the outgoing connection is the **stock server**. This server _uses_ the peer reservation on the hub server.
 - The server receiving the incoming connection is the **hub server**. The administrator _adds_ the peer reservation to this server.
@@ -20,10 +20,10 @@ However, you can use these instructions to set up a peer reservation regardless
 
 To complete these steps, you must meet the following prerequisites:
 
-- The administrators both servers must have `rippled` [installed](install-rippled.html) and running.
+- The administrators both servers must have `rippled` installed and running.
 - The administrators of both servers must agree to cooperate and must be able to communicate. A public communications channel is fine because you don't need to share any secret information.
 - The hub server must be able to receive incoming peer connections. For instructions on how to configure a firewall to allow this, see [Forward Ports for Peering](forward-ports-for-peering.html).
-- Both servers must be configured to sync with the same [XRP Ledger network](parallel-networks.html), such as the production XRP Ledger, the Testnet, or the Devnet.
+- Both servers must be configured to sync with the same XRP Ledger network, such as the production XRP Ledger, the Testnet, or the Devnet.
 
 ## Steps
 
@@ -33,7 +33,7 @@ To use a peer reservation, complete the following steps:
 
 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.html).)
+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.)
 
 **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.
 

content/tutorials/manage-the-rippled-server/installation/build-run-rippled-in-reporting-mode.md

@@ -9,7 +9,7 @@ top_nav_grouping: Popular Pages
 ---
 # Build and Run `rippled` in Reporting Mode
 
-[Reporting mode](rippled-server-modes.html) is a mode of the XRP Ledger core server specialized for serving [HTTP and WebSocket APIs](http-websocket-apis.html).
+Reporting mode is a mode of the XRP Ledger core server specialized for serving HTTP and WebSocket APIs.
 
 In reporting mode, the server does not connect to the peer-to-peer network. Instead, it uses gRPC to get validated data from one or more trusted servers that are connected to the P2P network. 
 
@@ -35,7 +35,7 @@ Multiple reporting mode servers can share access to the same network accessible
 
     **Note:** If you choose to use Cassandra as the database, the disk requirements for `rippled` will be lower as the data will not be stored on your local disk.  
 
-2. In order to run reporting mode, you also need to run one or more `rippled` servers in [P2P mode](install-rippled.html). Ensure that you have at least one `rippled` server running in P2P mode. 
+2. In order to run reporting mode, you also need to run one or more `rippled` servers in P2P mode. Ensure that you have at least one `rippled` server running in P2P mode. 
 
 3. A compatible version of CMake must be installed.