Merge pull request #5537 from segmentio/fix-rate-limits

Rate limits cleanup [DOC-742]

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
 
-Within a ten minute period, if any sources (in aggregate) send more than 12 million events (average of 20,000 events per second) without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that does not exceed 12 million events in a ten minute period.
+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.
 
 > 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

@@ -16,7 +16,8 @@ Authentication uses HTTP Basic Auth, which involves a `username:password` that i
 
 In practice that means taking a Segment source **Write Key**,`'abc123'`, as the username, adding a colon, and then the password field is left empty. After base64 encoding `'abc123:'` becomes `'YWJjMTIzOg=='`; and this is passed in the authorization header like so: `'Authorization: Basic YWJjMTIzOg=='`.
 
-**Note:** Encoding the write key without a colon may work due to backward compatibility, but this may not always be the case, so it's important to include the colon before encoding.
+> info ""
+> Include a colon before encoding. While encoding the write key without a colon might work due to backward compatibility, this won't always be the case.  
 
 ### Content-Type
 
@@ -35,14 +36,14 @@ Common reasons events are not accepted by Segment include:
 
 Segment welcomes feedback on API responses and error messages. [Reach out to support](https://segment.com/help/contact/){:target="_blank"} with any requests or suggestions you may have.
 
-## Rate Limits
+## 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. 
 
 > 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.
+> 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. 
 
-## Max Request Size
+## Max request size
 
 There is a maximum of `32KB` per normal API request.  The `batch` API endpoint accepts a maximum of `500KB` per request, with a limit of `32KB` per event in the batch.  If you are sending data from a server source, Segment's API responds with `400 Bad Request` if these limits are exceeded.