Peer crawler: copy edits per reviews

content/concepts/the-rippled-server/peer-protocol.md

@@ -13,7 +13,7 @@ To establish a peer-to-peer connection, one server connects to another via HTTPS
 
 ## Peer Protocol Port
 
-To participate in the XRP Ledger, `rippled` servers connects to arbitrary peers using the peer protocol. (All peers are treated as untrusted, unless they are [clustered](clustering.html) with the current server.)
+To participate in the XRP Ledger, `rippled` servers connect to arbitrary peers using the peer protocol. (All peers are treated as untrusted, unless they are [clustered](clustering.html) with the current server.)
 
 Ideally, the server should be able to send _and_ receive connections on the peer port. You should forward the port used for the peer protocol through your firewall to the `rippled` server. The [default `rippled` configuration file](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) listens for incoming peer protocol connections on port 51235 on all network interfaces. You can change the port used by editing the appropriate stanza in your `rippled.cfg` file.
 

content/references/data-api.md

@@ -5231,7 +5231,7 @@ Volume objects represent the total volumes of money moved, in either payments or
 [Server Object]: #server-objects
 [Server Objects]: #server-objects
 
-A "Server Object" describes one `rippled` server in the XRP Ledger peer-to-peer network. Server objects are returned by the [Get Topology](#get-topology), [Get Toplogy Nodes](#get-topology-nodes), and [Get Topology Node](#get-topology-node) methods. The Data API collects reported network topology approximately every 30 seconds using the [peer crawler](peer-protocol.html#peer-crawler).
+A "Server Object" describes one `rippled` server in the XRP Ledger peer-to-peer network. Server objects are returned by the [Get Topology](#get-topology), [Get Toplogy Nodes](#get-topology-nodes), and [Get Topology Node](#get-topology-node) methods. The Data API collects reported network topology approximately every 30 seconds using the [peer crawler](peer-crawler.html).
 
 Server objects have the following fields, with some only appearing if the request specified a verbose response:
 

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

@@ -5,7 +5,7 @@ By default, `rippled` servers provide statistics publicly to anyone who asks usi
 This document contains steps for two options:
 
 - [Change the Information Reported by the Peer Crawler](#change-the-information-reported-by-the-peer-crawler)
-- [Disabling the Peer Crawler](#disabling-the-peer-crawler)
+- [Disable the Peer Crawler](#disable-the-peer-crawler)
 
 ## Change the Information Reported by the Peer Crawler
 
@@ -32,7 +32,7 @@ To configure how much information your server provides in response to peer crawl
         systemctl restart rippled
 
 
-## Disabling the Peer Crawler
+## Disable the Peer Crawler
 
 To disable the peer crawler API on your server, so it does not respond to peer crawler requests at all, complete the following steps:
 

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

@@ -162,7 +162,7 @@ To help protect a validator from [DDoS](https://en.wikipedia.org/wiki/Denial-of-
 
         $ sudo systemctl restart rippled.service
 
-7. Use the [Peer Crawler](peer-protocol.html#peer-crawler) endpoint on one of your stock `rippled` servers. The response should not include your validator. This verifies that your validator's `[peer_private]` configuration is working. One of the effects of enabling `[peer_private]` on your validator is that your validator's peers do not include it in their Peer Crawler results.
+7. Use the [Peer Crawler](peer-crawler.html) endpoint on one of your stock `rippled` servers. The response should not include your validator. This verifies that your validator's `[peer_private]` configuration is working. One of the effects of enabling `[peer_private]` on your validator is that your validator's peers do not include it in their Peer Crawler results.