Skip to content

Commit a89a870

Browse files
csviriCopilot
andauthored
Update docs/content/en/docs/documentation/rate-limiting.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent de38d61 commit a89a870

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/content/en/docs/documentation/rate-limiting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ weight: 47
44
---
55

66
It is possible to rate limit reconciliation on a per-resource basis. The rate limit takes
7-
precedence over retry/re-schedule configurations: for example, even if retry would re-schedule a reconciliation
7+
precedence over retry/reschedule configurations: for example, even if a retry would reschedule a reconciliation
88
but this request would make the resource go over its rate limit, the next
99
reconciliation will be postponed according to the rate limiting rules. Note that the
10-
reconciliation is never canceled, it will just be executed as early as possible based on rate
10+
reconciliation is never cancelled, it will just be executed as early as possible based on rate
1111
limitations.
1212

1313
Rate limiting is by default turned **off**, since correct configuration depends on the reconciler

0 commit comments

Comments
 (0)