From 7df7cf23bc689af9c3eb1f68f76981fba3867996 Mon Sep 17 00:00:00 2001 From: Jacob Hoffman-Andrews Date: Tue, 10 Dec 2024 15:20:05 -0800 Subject: [PATCH] doc: switch from "leaky" to "token" bucket The two metaphors are mirrors of each other, and either works, but since we use the "token" bucket metaphor internally in Boulder, it's less confusing to use the same metaphor externally. --- content/en/docs/rate-limits.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/rate-limits.md b/content/en/docs/rate-limits.md index d28dd1561..1632b34fc 100644 --- a/content/en/docs/rate-limits.md +++ b/content/en/docs/rate-limits.md @@ -2,7 +2,7 @@ title: Rate Limits slug: rate-limits date: 2018-01-04 -lastmod: 2024-12-05 +lastmod: 2024-12-10 show_lastmod: true --- @@ -20,8 +20,8 @@ large website please review our [Integration Guide](/docs/integration-guide). # How Our Rate Limits Work -Limits are calculated, per request, using a [leaky -bucket](https://en.wikipedia.org/wiki/Leaky_bucket#As_a_meter) algorithm. This +Limits are calculated, per request, using a [token +bucket](https://en.wikipedia.org/wiki/Token_bucket) algorithm. This approach provides flexibility in how you use your allotted requests. You can either make requests in bursts—up to the full limit—or space out your requests to avoid the risk of being limited.