Rate limits clarification

Author: rchinn1

src/connections/rate-limits.md

@@ -9,7 +9,7 @@ Events ingested by Segment have a limit of **10,000** properties per individual
 
 ## Inbound data ingestion API rate limit
 
-If any sources send more than 20,000 events per second without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed this limit.
+If any sources send more than 20,000 events per second in a workspace without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed this limit.
 
 > warning "Engage rate limit"
 > Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more.

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -38,7 +38,7 @@ Segment welcomes feedback on API responses and error messages. [Reach out to sup
 
 ## Rate limits
 
-Segment recommends you to not exceed 20,000 requests per second with the HTTP API. For [`batch` requests](#batch), there's a limit of 500 KB per request. 
+For each workspace, Segment recommends you to not exceed 20,000 requests per second with the HTTP API. If you exceed this, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed the limit. For [`batch` requests](#batch), there's a limit of 500 KB per request. 
 
 > warning "Engage rate limit"
 > Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more.