Skip to content

Commit 4350857

Browse files
committed
fixed two mispellings
1 parent b84b051 commit 4350857

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/connections/rate-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ Segment limits the number of both inbound and outbound requests in order to ensu
55

66
## Inbound Data Ingestion API Rate Limit
77

8-
Segment allows customer sources to send up to 60,000,000 events within any 10 minute period (an average of 100,000 events per second). If, without prior arrangement, Segment reserves the right to queue any events that exceeed this threshold, and process those at a rate that does not exceed 60,000,000 events in a 10 minute period.
8+
Segment allows customer sources to send up to 60,000,000 events within any 10 minute period (an average of 100,000 events per second). If, without prior arrangement, Segment reserves the right to queue any events that exceed this threshold, and process those at a rate that does not exceed 60,000,000 events in a 10 minute period.
99

1010
## Outbound Downstream Destination Rate Limits
1111

12-
Most destinations have their own rate limits that are outside of Segment's control. In some instances, Segment can inngest and attempt to deliver data faster than the downstream destination can accept that data.
12+
Most destinations have their own rate limits that are outside of Segment's control. In some instances, Segment can ingest and attempt to deliver data faster than the downstream destination can accept that data.
1313

1414
Outbound requests to a destination can also fail for other reasons that are outside of Segment's control. When requests to a downstream destination fail, Segment makes subsequent attempts to deliver the data.
1515

0 commit comments

Comments
 (0)