diff --git a/content/use-cases/contribute-code-to-rippled.md b/content/use-cases/contribute-code-to-rippled.md
index 2f2963496c..745455aff3 100644
--- a/content/use-cases/contribute-code-to-rippled.md
+++ b/content/use-cases/contribute-code-to-rippled.md
@@ -14,30 +14,30 @@ Want to contribute code or a bug report to help improve `rippled`, the core peer
{{n.next()}}
-## [Set up and run a `rippled` server](xxxxx.html)
+## [Set up and run a `rippled` server](manage-the-rippled-server.html)
Set up and run a `rippled` server to understand the developer experience and functionality of the core peer-to-peer server that manages the XRP Ledger. Anyone can run their own `rippled` server that follows the network and keeps a complete copy of the XRP Ledger.
{{n.next()}}
-## [Try out XRP Ledger integration tools](xxxxx.html)
+## [Try out XRP Ledger integration tools](get-started-with-the-rippled-api.html)
Take a look at the various tools provided to help developers integrate with the XRP Ledger. From WebSocket and JSON-RPC API endpoints to the `ripple-lib` JavaScript library, take a look at the modes of integration offered to the developer community.
{{n.next()}}
-## [Get a sandbox XRP Ledger account](xxxxx.html)
+## [Get a sandbox XRP Ledger account](xrp-test-net-faucet.html)
Use the XRP Ledger Test Net to get a sandbox account. Connect your `rippled server` to the Test Net to make test calls and get to know the XRP Ledger.
{{n.next()}}
-## [Set up your development environment](xxxxx.html)
+## Set up your development environment
-A `rippled` development environment has a C++ compiler, access to the necessary libraries to compile `rippled` (such as Boost), and an editor for making changes to the source files. See the `rippled` repository for the latest recommendations of each. You should also create your own fork of the `rippled` repository on GitHub so you can contribute pull requests to the official repo.
+A `rippled` development environment has a C++ compiler, access to the necessary libraries to compile `rippled` (such as Boost), and an editor for making changes to the source files. See the `rippled` repository for the latest recommendations of each. You should also create your own fork of the `rippled` repository on GitHub so you can contribute pull requests to the official repo.
{{n.next()}}
diff --git a/content/use-cases/list-xrp-in-your-exchange.md b/content/use-cases/list-xrp-in-your-exchange.md
index d32b95f2d4..927b8bf322 100644
--- a/content/use-cases/list-xrp-in-your-exchange.md
+++ b/content/use-cases/list-xrp-in-your-exchange.md
@@ -6,7 +6,7 @@ Does your exchange want to list XRP, enabling your users to deposit, trade, and
{{n.next()}}
-## [Meet prerequisites for listing XRP](Listing XRP as an Exchange > Prerequisites for Supporting XRP.html)
+## [Meet prerequisites for listing XRP](list-xrp-as-an-exchange.html#prerequisites-for-supporting-xrp)
Put in place the foundation and operational processes needed to efficiently and securely list XRP in your exchange.
@@ -15,7 +15,7 @@ This includes creating and securing XRP Ledger accounts, implementing internal b
{{n.next()}}
-## [Set up and run a `rippled` server](Manage the rippled Server.html)
+## [Set up and run a `rippled` server](manage-the-rippled-server.html)
`rippled` is the core peer-to-peer server that manages the XRP Ledger.
@@ -28,7 +28,7 @@ You can start out running one `rippled` server to support development and explor
{{n.next()}}
-## [Try out XRP Ledger integration tools](Get Started with the rippled API.html)
+## [Try out XRP Ledger integration tools](get-started-with-the-rippled-api.html)
Take a look at the various tools provided to help you integrate with the XRP Ledger.
@@ -37,14 +37,14 @@ From WebSocket and JSON-RPC API endpoints to the RippleAPI JavaScript library, f
{{n.next()}}
-## [Get a sandbox XRP Ledger account](XRP Ledger Test Net.html)
+## [Get a sandbox XRP Ledger account](xrp-test-net-faucet.html)
Use the XRP Ledger Test Net to get a sandbox account. Connect your `rippled` server to the Test Net to make test calls and get to know the XRP Ledger. Once you’re ready to transact in real XRP, you can switch over to transacting on the live XRP Ledger.
{{n.next()}}
-## [Understand and code integrations to support the flow of funds](Listing XPR as an Exchange > Flow of Funds.html)
+## [Understand and code integrations to support the flow of funds](list-xrp-as-an-exchange.html#flow-of-funds)
To support listing XRP, code integrations with the XRP Ledger to deposit XRP into your exchange, trade XRP on the exchange, rebalance XRP holding, and withdraw XRP from your exchange.
@@ -52,7 +52,7 @@ To support listing XRP, code integrations with the XRP Ledger to deposit XRP int
### Related Tasks
- [Contribute Code to `rippled`](contribute-code-to-rippled.html)
-- [Subscribe to XRP Ledger Updates](x)
-- [Capacity Planning](x)
-- [Look Up an XRP Ledger Account’s Transaction History](x)
-- [Implement Destination Tags](x)
+- [Subscribe to XRP Ledger Updates](subscription-methods.html)
+- [Capacity Planning](capacity-planning.html)
+- [Look Up an XRP Ledger Account’s Transaction History](tx_history.html)
+
diff --git a/content/use-cases/run-a-rippled-validator.md b/content/use-cases/run-a-rippled-validator.md
index d620cf3830..adeae83d90 100644
--- a/content/use-cases/run-a-rippled-validator.md
+++ b/content/use-cases/run-a-rippled-validator.md
@@ -8,7 +8,7 @@ Each `rippled` server (not running in stand-alone mode) connects to a network of
{{n.next()}}
-## [Understand what it means to run a validator](Manage the rippled Server > Reasons to Run a Validator - includes Properties of a Good Validator.html)
+## [Understand what it means to run a validator](the-rippled-server.html#reasons-to-run-a-validator)
If you or your organization relies on the XRP Ledger, it is in your interest to run a validator to participate in the consensus process and provide a trusted validator that supports the ongoing decentralization of the XRP Ledger.
@@ -21,7 +21,7 @@ Despite that, it is important to note that every validator contributes to the lo
{{n.next()}}
-## [Set up and run a `rippled` server](Manage the rippled Server.html)
+## [Set up and run a `rippled` server](manage-the-rippled-server.html)
Install and run a `rippled` server. Anyone can run their own `rippled` server that follows the network and keeps a complete copy of the XRP Ledger.
@@ -30,21 +30,21 @@ For configuration guidance and network and hardware requirements, see [Capacity
{{n.next()}}
-## [Enable validation on your rippled server](Manage the rippled server > Run a Validator.html)
+## [Enable validation on your rippled server](run-rippled-as-a-validator.html)
To configure your `rippled` server to run in validator mode, generate a validator key pair and add it to your `rippled.cfg` file.
{{n.next()}}
-## [Set up a stock rippled server as a proxy](Manage the rippled server > Run a Validator > Public-Facing Server.html)
+## [Set up a stock rippled server as a proxy](run-rippled-as-a-validator.html#public-facing-server)
To protect a production validator from DDoS attacks, you can use a stock `rippled` server as a proxy between the validator and the outside network.
{{n.next()}}
-## [Associate your validator with a web domain you control](Manage the rippled server > Run a Validator > Domain Verification.html)
+## [Associate your validator with a web domain you control](run-rippled-as-a-validator.html#domain-verification)
Network participants are unlikely to trust a validator without knowing who is operating it. To address this concern, associate your validator with a web domain you control.
You may also wish to have your validator listed with one or more validator tracking services, such as the XRP Charts Validator Registry .