diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md
index ffa085d471..cbc51b3434 100644
--- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md
+++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md
@@ -236,9 +236,11 @@ To provide domain verification:
 
 1. Choose a domain name you own that you want to be publicly associated with your validator. You must run a public-facing HTTPS server on port 443 of that domain and you must have access to the private key file associated with that server's TLS certificate. (Note: [TLS was formerly called SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security).) As a precaution against DDoS attempts, your domain name should not resolve to the ip address of your validator.
 
-2. Share your validator's public key with the public, especially other `rippled` operators. For example, you can share your validator's public key on your website, on social media, in the [XRPChat community forum](https://www.xrpchat.com/), or in a press release.
+2. Serve an [`xrp-ledger.toml`](xrp-ledger-toml.html) file at your domain, and complete the [domain verification](xrp-ledger-toml.html#domain-verification) steps.
 
-3. Submit a request to have your validator listed in XRP Charts' [Validator Registry](https://xrpcharts.ripple.com/#/validators) using this [Google Form](https://docs.google.com/forms/d/e/1FAIpQLScszfq7rRLAfArSZtvitCyl-VFA9cNcdnXLFjURsdCQ3gHW7w/viewform). Having your validator listed in this registry provides another form of public verification that your validator and domain are owned by you. To complete the form, you'll need the following information:
+3. Share your validator's public key with the public, especially other `rippled` operators. For example, you can share your validator's public key on your website, on social media, in the [XRPChat community forum](https://www.xrpchat.com/), or in a press release.
+
+4. Submit a request to have your validator listed in XRP Charts' [Validator Registry](https://xrpcharts.ripple.com/#/validators) using this [Google Form](https://docs.google.com/forms/d/e/1FAIpQLScszfq7rRLAfArSZtvitCyl-VFA9cNcdnXLFjURsdCQ3gHW7w/viewform). Having your validator listed in this registry provides another form of public verification that your validator and domain are owned by you. To complete the form, you'll need the following information:
 
       1. Find your validator public key by running the following on the validator server.
 
@@ -266,7 +268,7 @@ To provide domain verification:
 
         Provide the value returned in the **Domain Signature** field of the Google Form.
 
-4. After submitting the completed Google Form, you'll receive an email from XRP Charts that tells you whether your domain verification succeeded or failed. If your domain verification succeeds, XRP Charts lists your validator and domain in its [Validator Registry](https://xrpcharts.ripple.com/#/validators).
+5. After submitting the completed Google Form, you'll receive an email from XRP Charts that tells you whether your domain verification succeeded or failed. If your domain verification succeeds, XRP Charts lists your validator and domain in its [Validator Registry](https://xrpcharts.ripple.com/#/validators).
 
 <!--{ ***TODO: For the future - add a new section or separate document: "Operating a Trusted Validator" -- things that you need to be aware of once your validator has been added to a UNL and is participating in consensus. We should tell the user what to expect once they are listed in a UNL. How to tell if your validator is participating in the consensus process? How to tell if something isn't right with your validator - warning signs that they should look out for? How to tell if your validator has fallen out of agreement - what is the acceptable vs unacceptable threshold? Maybe provide a script that will alert them when something is going wrong.*** }-->
 
diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md
new file mode 100644
index 0000000000..06759ad7e2
--- /dev/null
+++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md
@@ -0,0 +1,59 @@
+# Run rippled as a Wallet Server
+
+A wallet server is a multipurpose configuration for `rippled`. With a wallet server, you can submit transactions to the XRP Ledger, access ledger history, and use the latest [tools](https://xpring.io/) to integrate with XRP.
+
+
+A wallet server does all of the following:
+
+- Connects to a [network of peers](consensus-network.html)
+
+- Relays cryptographically signed [transactions](transaction-basics.html)
+
+- Maintains a local copy of the complete shared global [ledger](ledgers.html)
+
+- Participates in the [consensus process](consensus.html) as a validator
+
+
+## 1. Install `rippled`
+
+For more information, see [Install `rippled`](install-rippled.html).
+
+<!--{TODO: Include instructions on how to enable GRPC once rippled v 1.5.0 is released}-->
+
+## 2. Enable validation on your wallet server
+
+For more information, see [Enable validation on your `rippled` server](run-rippled-as-a-validator.html#3-enable-validation-on-your-rippled-server).
+
+    **Warning:** Validators should not be accessible to the public. Do not allow public websockets access to your wallet server or any other form of public access. 
+     
+## 3. Provide domain verification
+
+For more information, see [Provide domain verification](run-rippled-as-a-validator.html#6-provide-domain-verification).
+
+## Troubleshooting
+
+For more information, see [Troubleshooting `rippled`](troubleshoot-the-rippled-server.html)
+
+
+## See Also
+
+- **Concepts:**
+    - [XRP Ledger Overview](xrp-ledger-overview.html)
+    - [Consensus Network](consensus-network.html)
+    - [The `rippled` Server](the-rippled-server.html)
+- **Tutorials:**
+    - [Cluster rippled Servers](cluster-rippled-servers.html)
+    - [Install `rippled`](install-rippled.html)
+    - [Capacity Planning](capacity-planning.html)
+    - [XRP Ledger Businesses](xrp-ledger-businesses.html)
+- **References:**
+    - [Validator Keys Tool Guide](https://github.com/ripple/validator-keys-tool/blob/master/doc/validator-keys-tool-guide.md)
+    - [consensus_info method][]
+    - [validator_list_sites method][]
+    - [validators method][]
+
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}			
+{% include '_snippets/tx-type-links.md' %}			
+{% include '_snippets/rippled_versions.md' %}
diff --git a/dactyl-config.yml b/dactyl-config.yml
index 1bbaa0f92b..5de3cf318b 100644
--- a/dactyl-config.yml
+++ b/dactyl-config.yml
@@ -2374,6 +2374,16 @@ pages:
         targets:
             - en
 
+    -   md: tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md
+        html: run-rippled-as-a-wallet-server.html
+        funnel: Docs
+        doc_type: Tutorials
+        category: Manage the rippled Server
+        subcategory: Configuration
+        blurb: A multipurpose configuration for anyone integrating XRP. #TODO:translate
+        targets:
+            - en
+
     -   md: tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.ja.md
         html: run-rippled-as-a-validator.html
         funnel: Docs