From 47b600af7a54e1d92ddcd83e36f8e10dc8530caf Mon Sep 17 00:00:00 2001 From: Istio Automation Date: Tue, 21 Jul 2020 06:20:27 -0700 Subject: [PATCH] bugfix (#7761) Co-authored-by: King Ye --- content/en/docs/tasks/policy-enforcement/rate-limiting/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/policy-enforcement/rate-limiting/index.md b/content/en/docs/tasks/policy-enforcement/rate-limiting/index.md index c8ac730e5e..561ce72570 100644 --- a/content/en/docs/tasks/policy-enforcement/rate-limiting/index.md +++ b/content/en/docs/tasks/policy-enforcement/rate-limiting/index.md @@ -85,7 +85,7 @@ so the configuration to enable rate limiting on both adapters is the same. {{< /warning >}} The `memquota` handler defines 4 different rate limit schemes. The default, - if no overrides match, is `500` requests per one second (`1s`). Two + if no overrides match, is `500` requests per one second (`1s`). Three overrides are also defined: * The first is `1` request (the `maxAmount` field) every `5s` (the