Apply suggestions from code review

Author: forstisabella

src/connections/destinations/catalog/repeater/index.md

@@ -26,9 +26,13 @@ You can do this for as many sources as you need.
 
 Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.
 
-## Replays with a Repeater
+## Replays with a Repeater destination
 
-Replays can affect your MTU count when using a Repeater destination. Notify your team before initiating a Replay if you’re using a Repeater destination. There are edge cases where the repeater would count towards MTUs, specifically when replaying historical data from the source connected to feed data into that Repeater destination. This is because userIds/anonymousIds would not have been seen by the source the Repeater sends data to. The API plans count by events sent through the pipeline; the repeater resends an event through the entire pipeline [Source → Repeater → Source → Destinations] so one event is sent through twice, and would increase the throughput count.
+Running a Replay on a Repeater destination might count toward your MTUs, especially if you are replaying historical data from the source that flows data into your Repeater destination. 
+
+Because the API plans count by events sent through the pipeline and the Repeater destination resends an event through the entire pipeline, one event might flow through your source twice which increases the throughput count.
+
+Segment recommends that you notify your team before initiating a Replay if you’re using a Repeater destination. 
 
 ## Repeater FAQ