small edit [netlify-ignore]

Author: markzegarelli

src/guides/usage-and-billing/mtus-and-throughput.md

@@ -64,9 +64,9 @@ This is in contrast to "Objects" which represent a single thing that persists ov
 
 ## How is object throughput calculated?
 
-[Object Cloud Sources](/docs/connections/sources/about-cloud-sources/#object-cloud-app-sources) retrieve records from integration partners on a scheduled basis. These records are then processed prior to being written out to connected [Storage Destinations](/docs/connections/storage/). Segment counts one throughput for each record retrieved from a Cloud Source.
+[Object Cloud Sources](/docs/connections/sources/about-cloud-sources/#object-cloud-app-sources) retrieve records from integration partners on a scheduled basis. Segment processes these records before writing them out to connected [Storage Destinations](/docs/connections/storage/). Segment counts one throughput for each record retrieved from a Cloud Source.
 
-Depending on the capabilities of the partner's API, Segment may need to retrieve all available records and then deduplicate them prior to writing them out to a connected storage destination. In such cases, throughput will still be counted for all records retrieved, even if the same records are retrieved multiple times in a given billing period. If you are experiencing overages due to high object throughput, please contact [email protected] to request a less frequent sync cadence.
+Depending on the capabilities of the partner's API, Segment may need to retrieve all available records and then deduplicate them prior to writing them out to a connected storage destination. In such cases, throughput is still counted for all retrieved records, even if the same records are retrieved multiple times in a given billing period. If you experience overages due to high object throughput, contact [[email protected]](mailto:[email protected]) to request a less frequent sync cadence.
 
 ## MTUs, object throughput, and Cloud sources