Skip to content

Commit 29e225c

Browse files
authored
Apply suggestions from code review
1 parent 4eb4e9f commit 29e225c

File tree

1 file changed

+3
-3
lines changed
  • src/connections/destinations/catalog/iterable

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -128,11 +128,11 @@ Iterable supports sending push notification events to Segment. These events are
128128
They support the following events:
129129
`Push Delivered`, `Push Bounced`, `Mobile App Uninstalled`, `Push Opened`
130130

131-
## High Retry Rate
131+
## High retry rate
132132

133-
If you are experiencing a large amount of retries within your destinations that are connected to your HTTP API source, this could be due to a related Etimedout errors. The errors seem to be Etimedout errors, in general, these are relatively normal intermittent problems that can come about when HTTP requests are made from server to server.
133+
If you're experiencing a large amount of retries within your destinations that are connected to your HTTP API source, this could be due to Etimedout errors. Etimedout errors are intermittent problems that can come about when HTTP requests are made from server to server.
134134

135-
The Etimedout error is the result of an HTTP response not being received in a specific timeframe. Read more about how Segment retries events to destinations [here](/docs/connections/destinations/#retries-between-segment-and-destinations).
135+
The Etimedout error is the result of an HTTP response not being received in a specific timeframe. [Learn more](/docs/connections/destinations/#retries-between-segment-and-destinations) about how Segment retries events to destinations.
136136

137137

138138
## Using Iterable with Engage

0 commit comments

Comments
 (0)