From ea321515773fa5ecdb1677859c6a5db25aaf55c0 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Wed, 30 Oct 2024 16:51:45 +0100 Subject: [PATCH] fix: Typo in expected features for SDKs --- develop-docs/sdk/expected-features/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/expected-features/index.mdx b/develop-docs/sdk/expected-features/index.mdx index 4e2faac441aff..b15050d959162 100644 --- a/develop-docs/sdk/expected-features/index.mdx +++ b/develop-docs/sdk/expected-features/index.mdx @@ -210,7 +210,7 @@ Consider having the SDK retry sending events once the device is back online, whe Once the device is back online, the SDK is likely going to empty its disk queue in a quick burst of requests. This can trigger different abuse filters in Sentry. To account for that, it's considered to add a small delay between cached event captures. A recommended value is 100 milliseconds. -If the SDK is being [rate-limited](/sdk/expected-features/rate-limiting/), which causes the SDK to drop any event that reaches its HTTP transport, cosider stop consuming the disk cache until the `Retry-After` timeout is reached or the app restarts. +If the SDK is being [rate-limited](/sdk/expected-features/rate-limiting/), which causes the SDK to drop any event that reaches its HTTP transport, consider stop consuming the disk cache until the `Retry-After` timeout is reached or the app restarts. #### Example implementations