Included Decentralized Domain Verification instructions

content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md

@@ -210,9 +210,11 @@ To provide domain verification:
 
 1. Choose a domain name you own that you want to be publicly associated with your wallet server. 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 wallet server.
 
-2. Share your wallet server's validator public key with the public, especially other `rippled` operators. For example, you can share your wallet server's validator 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](https://xrpl.org/xrp-ledger-toml.html#domain-verification) steps.
 
-3. Submit a request to have your wallet server listed in XRP Charts' [Validator Registry](https://xrpcharts.ripple.com/#/validators) as a validator using this [Google Form](https://docs.google.com/forms/d/e/1FAIpQLScszfq7rRLAfArSZtvitCyl-VFA9cNcdnXLFjURsdCQ3gHW7w/viewform). Having your wallet server listed as a validator in this registry provides another form of public verification that your wallet server and domain are owned by you. To complete the form, you'll need the following information:
+3. Share your wallet server's validator public key with the public, especially other `rippled` operators. For example, you can share your wallet server's validator 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 wallet server listed in XRP Charts' [Validator Registry](https://xrpcharts.ripple.com/#/validators) as a validator using this [Google Form](https://docs.google.com/forms/d/e/1FAIpQLScszfq7rRLAfArSZtvitCyl-VFA9cNcdnXLFjURsdCQ3gHW7w/viewform). Having your wallet server listed as a validator in this registry provides another form of public verification that your wallet server 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 wallet server.
 
@@ -240,7 +242,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 wallet server 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 wallet server 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.*** }-->